Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot merge resource due to conflicting Schema URL in OTEL v1.1.0 / OTEL-contrib v1.1.0 #1384

Closed
pkwarren opened this issue Nov 2, 2021 · 0 comments · Fixed by #1385
Closed
Assignees
Labels
bug Something isn't working
Milestone

Comments

@pkwarren
Copy link

pkwarren commented Nov 2, 2021

If we attempt to upgrade to the latest OTEL and OTEL contrib, we're hitting the error cannot merge resource due to conflicting Schema URL attempting to create a resource detector on startup. This appears to be due to the fact that the OTEL libraries have updated to semconv v1.7.0 while several of the OTEL-contrib packages are still on semconv v1.4.0.

@Aneurysm9 Aneurysm9 self-assigned this Nov 2, 2021
@Aneurysm9 Aneurysm9 added the bug Something isn't working label Nov 2, 2021
plantfansam referenced this issue in plantfansam/opentelemetry-go-contrib Mar 18, 2022
* Call otel.Handle with non-nil errors

That's what normally happens in other call sites. Those two didn't
check it, but passed the "error" to Handle. The default, delegating
implementation of ErrorHandler was printing the error unconditionally,
which resulted in pointless lines like `2020/12/07 19:51:28 <nil>` in
demos, for example.

* Add tests

Co-authored-by: Tyler Yahn <[email protected]>
@pellared pellared added this to the untracked milestone Nov 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants