Add W3C Trace Context propagation#284
Merged
Merged
Conversation
The observability tracer and agent_trace spans carried no IDs, so a span on one side of an HTTP call could not be correlated with the work it triggered downstream. Add the W3C Trace Context standard: generate, parse, and propagate traceparent / tracestate headers with an injectable RNG for deterministic IDs under test. Wired through facade, executor (AC_trace_inject / AC_trace_extract), MCP, and the Script Builder with a headless test batch and EN/Zh docs.
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 61 |
| Duplication | 0 |
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
|
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
1 participant
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
Adds the W3C Trace Context standard so spans, logs, and downstream services share one trace/span lineage across HTTP boundaries. The existing
observabilitytracer andagent_tracespans carried no IDs and could not be correlated across a call.SpanContext(immutable trace_id/span_id/trace_flags/tracestate).new_root_context/child_context;parse_traceparent/format_traceparent(version-00, rejects bad version / malformed / all-zero IDs withTraceContextError);parse_tracestate/format_tracestate.inject_context/extract_contextover a headers dict (case-insensitive extract).Layers
utils/trace_context/(pure stdlibos/re, zero PySide6).je_auto_control+__all__.AC_trace_inject,AC_trace_extract.ac_trace_inject,ac_trace_extract(read-only).test/unit_test/headless/test_trace_context_batch.py(14 tests, no Qt/network).v76_features_doc.rst(EN + Zh) + toctrees + 3 README What's-new sections.Verification
pytest test/unit_test/headless/test_trace_context_batch.py→ 14 passed.ruff check je_auto_control/clean; pylint 10.00/10; bandit clean; radon CC clean.