Skip to content

Test for the exclusion of documentation modifications in library sele… - #5122

Closed
nccatoni wants to merge 7 commits into
mainfrom
nccatoni/test-#5121
Closed

Test for the exclusion of documentation modifications in library sele…#5122
nccatoni wants to merge 7 commits into
mainfrom
nccatoni/test-#5121

Conversation

@nccatoni

Copy link
Copy Markdown
Collaborator

…ction. (#5121)

Motivation

Test for push request #5121

Base automatically changed from exclude-docs-from-library-detection to main August 25, 2025 14:31
@nccatoni nccatoni closed this Aug 25, 2025
@nccatoni
nccatoni deleted the nccatoni/test-#5121 branch August 25, 2025 15:32
darccio added a commit that referenced this pull request Aug 4, 2026
The previous commit covers CSS with the v1 protocol, but that pairing
worked even while the two were coupled, so it cannot detect the coupling.
The discriminating case is the mirror: v1 pinned while CSS is off.

Released dd-trace-go gates v1 on CSS capability and silently downgrades
to /v0.4/traces the moment stats computation is disabled. CSS is
negotiated entirely out of band -- a Datadog-Client-Computed-Stats header
and a separate /v0.6/stats endpoint, both handled identically by the
Agent on either protocol -- so disabling it has no bearing on the trace
wire format. DataDog/dd-trace-go#5122 removes the gate.

Add APM_TRACING_EFFICIENT_PAYLOAD_STATS_DISABLED, which is
APM_TRACING_EFFICIENT_PAYLOAD plus DD_TRACE_STATS_COMPUTATION_ENABLED
=false, and Test_V1PayloadWithStatsDisabled asserting every trace still
goes to /v1.0/traces in v1 format. The test first asserts no /v0.6/stats
payloads exist, so it fails loudly rather than passing vacuously if CSS
were somehow active.

Declared missing_feature for golang until #5122 ships, and for nodejs and
ruby to match every other class in this file (neither has working v1).
Java is deliberately left inheriting the file-level >=1.62.0: it supports
v1 when the protocol is pinned and has no CSS coupling, so it is the
language that proves the test is meaningful rather than vacuous.

Co-Authored-By: Claude <noreply@anthropic.com>
darccio added a commit that referenced this pull request Aug 7, 2026
The previous commit covers CSS with the v1 protocol, but that pairing
worked even while the two were coupled, so it cannot detect the coupling.
The discriminating case is the mirror: v1 pinned while CSS is off.

Released dd-trace-go gates v1 on CSS capability and silently downgrades
to /v0.4/traces the moment stats computation is disabled. CSS is
negotiated entirely out of band -- a Datadog-Client-Computed-Stats header
and a separate /v0.6/stats endpoint, both handled identically by the
Agent on either protocol -- so disabling it has no bearing on the trace
wire format. DataDog/dd-trace-go#5122 removes the gate.

Add APM_TRACING_EFFICIENT_PAYLOAD_STATS_DISABLED, which is
APM_TRACING_EFFICIENT_PAYLOAD plus DD_TRACE_STATS_COMPUTATION_ENABLED
=false, and Test_V1PayloadWithStatsDisabled asserting every trace still
goes to /v1.0/traces in v1 format. The test first asserts no /v0.6/stats
payloads exist, so it fails loudly rather than passing vacuously if CSS
were somehow active.

Declared missing_feature for golang until #5122 ships, and for nodejs and
ruby to match every other class in this file (neither has working v1).
Java is deliberately left inheriting the file-level >=1.62.0: it supports
v1 when the protocol is pinned and has no CSS coupling, so it is the
language that proves the test is meaningful rather than vacuous.

Co-Authored-By: Claude <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant