test(cloudflare): Port the http-server integration suites to span streaming - #24195
Draft
JPeer264 wants to merge 1 commit into
Draft
test(cloudflare): Port the http-server integration suites to span streaming#24195JPeer264 wants to merge 1 commit into
JPeer264 wants to merge 1 commit into
Conversation
…eaming Removes the `traceLifecycle: 'static'` pin from the five `suites/integrations/http-server*` suites. Nothing else changes. These suites cover request body capture, so they assert on the event the worker sends and never on a transaction. None of them sets `tracesSampleRate`, so the pin only ever selected a trace lifecycle for a client that emits no spans either way. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
size-limit report 📦
|
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.
Removes the
traceLifecycle: 'static'pin from the fivesuites/integrations/http-server*suites.Nothing else changes. These suites cover request body capture, so they assert on the event the worker sends and never on a transaction. None of them sets
tracesSampleRateeither, so the pin only ever selected a trace lifecycle for a client that emits no spans in the first place.Part of #24148
🤖 Generated with Claude Code