opentelemetry-erlang-contrib
opentelemetry-erlang-contrib copied to clipboard
Update dependency opentelemetry_process_propagator to ~> 0.3
This PR contains the following updates:
| Package | Update | Change |
|---|---|---|
| opentelemetry_process_propagator | minor | ~> 0.2 -> ~> 0.3 |
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
- [ ] If you want to rebase/retry this PR, check this box
This PR has been generated by Mend Renovate. View repository job log here.
⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
- any of the package files in this branch needs updating, or
- the branch becomes conflicted, or
- you click the rebase/retry checkbox if found above, or
- you rename this PR's title to start with "rebase!" to trigger it manually
The artifact failure details are included below:
File name: instrumentation/opentelemetry_dataloader/mix.lock
Command failed: mix deps.update opentelemetry_process_propagator
** (Mix) Hex dependency resolution failed
Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.
Dataloader's version has to be pinned due to this pinned dependency in dataloader itself.
@tsloughter any idea why all these tests started failing tonight with this (UndefinedFunctionError) function :otel_tracer_provider_sup.start/2 is undefined or private error? These were all passing the other day and the only thing that got bumped here in the lock files was the api patch version.
Maybe upgrade the test SDK being used?