Uh oh!
There was an error while loading. Please reload this page.
test(aws-serverless): Add callback-style and trace-propagation Lambda e2e coverage - #21757
Closed
nicohrubec wants to merge 1 commit into
Closed
test(aws-serverless): Add callback-style and trace-propagation Lambda e2e coverage#21757nicohrubec wants to merge 1 commit into
nicohrubec wants to merge 1 commit into
Conversation
… e2e coverage Adds e2e cases for callback-style handlers (success + error) and trace continuation from incoming headers, covering paths the existing async-only suite missed. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
size-limit report 📦
|
nicohrubec
commented
Jun 24, 2026
MemberAuthor
Combining into #21758 — the changes are small enough to ship as a single PR. |
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 freeto 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.
Adds e2e coverage for AWS Lambda handler paths the existing async-only suite missed, ahead of the AwsLambda instrumentation streamline (#stacked):
(event, context, callback)) — success transaction + error capture (mechanismauto.function.aws_serverless.otel).sentry-trace/baggageand asserting the Lambda transaction continues thetrace_id/parent_span_id.These pass against the current instrumentation, so they act as a behavior-preserving guard for the streamline PR stacked on top.
🤖 Generated with Claude Code