The site behind https://software.opensuse.org. It is the default web interface to download openSUSE distributions and to search for OBS packages. Packaged at https://build.opensuse.org/project/show/openSUSE:infrastructure:software.opensuse.org
Make :value in SingleExceptionInterface writable, so that it can be modified in before_send under event.exception.values[n].value#2072
Add sampled field to dynamic_sampling_context#2092
Consolidate HTTP span data conventions with OpenTelemetry with Sentry::Span::DataConventions#2093
Consolidate database span data conventions with OpenTelemetry for ActiveRecord and Redis #2100
Add new config.trace_propagation_targets option to set targets for which headers are propagated in outgoing HTTP requests #2079
# takes an array of strings or regexpsconfig.trace_propagation_targets=[/.*/]# default is to all targetsconfig.trace_propagation_targets=[/example.com/,'foobar.org/api/v2']
Tracing without Performance
Implement PropagationContext on Scope and add Sentry.get_trace_propagation_headers API #2084
The SDK now supports connecting arbitrary events (Errors / Transactions / Replays) across distributed services and not just Transactions.
To continue an incoming trace starting with this version of the SDK, use Sentry.continue_trace as follows.
Make :value in SingleExceptionInterface writable, so that it can be modified in before_send under event.exception.values[n].value#2072
Add sampled field to dynamic_sampling_context#2092
Consolidate HTTP span data conventions with OpenTelemetry with Sentry::Span::DataConventions#2093
Consolidate database span data conventions with OpenTelemetry for ActiveRecord and Redis #2100
Add new config.trace_propagation_targets option to set targets for which headers are propagated in outgoing HTTP requests #2079
# takes an array of strings or regexpsconfig.trace_propagation_targets=[/.*/]# default is to all targetsconfig.trace_propagation_targets=[/example.com/,'foobar.org/api/v2']
Tracing without Performance
Implement PropagationContext on Scope and add Sentry.get_trace_propagation_headers API #2084
The SDK now supports connecting arbitrary events (Errors / Transactions / Replays) across distributed services and not just Transactions.
To continue an incoming trace starting with this version of the SDK, use Sentry.continue_trace as follows.
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.
All Depfu comment commands
@depfu rebase
Rebases against your default branch and redoes this update
@depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@depfu cancel merge
Cancels automatic merging of this PR
@depfu close
Closes this PR and deletes the branch
@depfu reopen
Restores the branch and reopens this PR (if it's closed)
@depfu pause
Ignores all future updates for this dependency and closes this PR
@depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ sentry-rails (5.10.0 → 5.11.0) · Repo · Changelog
Release Notes
5.11.0
Does any of this look wrong? Please let us know.
✳️ minitest (5.19.0 → 5.20.0) · Repo · Changelog
Release Notes
5.20.0 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 3 commits:
prepped for release
+ Optionally allow autorun exit hook to remain active in forked child. (casperisfine)
Fixed skip messages for non-forking systems. (casperisfine)
✳️ sentry-ruby (5.10.0 → 5.11.0) · Repo · Changelog
Release Notes
5.11.0
Does any of this look wrong? Please let us know.
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands