Repository navigation
Conversation
Contributor
Contributor
🟢 Java Benchmark SLOs — All performance SLOs passed
PR vs. master results
Commit: Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion. |
mcculls
force-pushed
the
mcculls/context-capture-callers
branch
from
November 11, 2026 11:50
b0410db to
9c1c1c7
Compare
Kafka / producer-benchmarkParameters
See matching parameters
SummaryFound 0 performance improvements and 0 performance regressions! Performance is the same for 2 metrics, 1 unstable metrics. See unchanged results
|
Kafka / consumer-benchmarkParameters
See matching parameters
SummaryFound 0 performance improvements and 0 performance regressions! Performance is the same for 3 metrics, 0 unstable metrics. See unchanged results
|
mcculls
force-pushed
the
mcculls/context-capture-callers
branch
from
November 12, 2026 12:21
9c1c1c7 to
ad1d74c
Compare
Debugger benchmarksParameters
See matching parameters
SummaryFound 0 performance improvements and 3 performance regressions! Performance is the same for 7 metrics, 5 unstable metrics.
See unchanged results
Request duration reports for reportsgantt
title reports - request duration [CI 0.99] : candidate=None, baseline=None
dateFormat X
axisFormat %s
section baseline
noprobe (363.33 µs) : 340, 386
. : milestone, 363,
basic (347.973 µs) : 343, 353
. : milestone, 348,
loop (8.124 ms) : 8060, 8188
. : milestone, 8124,
section candidate
noprobe (371.217 µs) : 334, 409
. : milestone, 371,
basic (365.421 µs) : 358, 372
. : milestone, 365,
loop (8.12 ms) : 8056, 8184
. : milestone, 8120,
|
mcculls
force-pushed
the
mcculls/context-capture-callers
branch
from
November 12, 2026 12:57
ad1d74c to
a930c41
Compare
mcculls
force-pushed
the
mcculls/context-capture-callers
branch
2 times, most recently
from
November 14, 2026 20:18
9964b50 to
20d70b5
Compare
mcculls
force-pushed
the
mcculls/context-capture-callers
branch
2 times, most recently
from
November 15, 2026 21:59
c85b231 to
87b6961
Compare
gh-worker-dd-mergequeue-cf854d
Bot
force-pushed
the
mcculls/context-capture-callers
branch
from
November 16, 2026 16:59
87b6961 to
9721043
Compare
Capture suppression belongs to the active execution context rather than its tracer. Move instrumentation helpers and tests to the Context capture controls so they follow the selected context manager.
mcculls
force-pushed
the
mcculls/context-capture-callers
branch
from
November 16, 2026 23:56
9721043 to
fcaeeeb
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What Does This Do
Move remaining capture-control callers to
Context.isCaptureEnabled/Context.setCaptureEnabledand remove the static async-propagation wrappers fromAgentTracer. Public tracer instance methods remain available for compatibility.Motivation
Capture suppression belongs to the active execution context. Using the Context API lets callers follow the selected context manager without depending on the legacy tracer API. This is stacked on #13311.
Additional Notes
Reroute the legacy adapter's capture methods to the scope manager through dedicated tracer capture methods, bypassing the public async-propagation methods. Advice uses the bytecode bridge for compatibility with older class files.
Validation: scope-manager and AI Guard propagation tests; all three migrated OpenTracing test classes; compilation of migrated Scala and Kotlin callers; formatting of affected modules. Scope-manager tests also check legacy API compatibility and verify Context bypasses the legacy async methods.