Repository navigation
Conversation
size-limit report 📦Compared: 2bceb36 (PR test merge using develop at dd50123) Against: f547f64 (develop) · base run #65164
|
Optional E2E testsSome optional checks were not successful. They do not block the merge. 6 not successful, 50 successful. See the run.
Successful checks
|
a357b59 to
e260c45
Compare
e260c45 to
35c5803
Compare
35c5803 to
a2969c3
Compare
cbbbe3b to
335dfa3
Compare
335dfa3 to
126db26
Compare
126db26 to
7198f33
Compare
3595b95 to
3ba0759
Compare
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 2 potential issues.
There are 5 total unresolved issues (including 3 from previous reviews).
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 3ba0759. Configure here.
3ba0759 to
4513424
Compare
702d6cd to
5d89e02
Compare
5d89e02 to
9edc632
Compare
9edc632 to
5fb2345
Compare
|
One or more gzipped bundles increased by more than 500 bytes. If this increase is intentional, add the Accept Bundlesize Increase label to this PR to rerun and accept the check. |
Lambda runs no HTTP server, so `serveTunnelIntegration` redirects `_HANDLER` to a shim that answers tunnel events before the user's handler, when `init` runs from a preload. `wrapHandler` in `@sentry/aws-serverless` answers them too. The handler resolution moves to `@sentry/node`, and its loader stays out of the main entry.
… runtime Covers the aws-serverless and @sentry/node handler shims for async, callback and streaming handlers, the API Gateway, ALB and base64 event shapes, and a failed forward.
5fb2345 to
8e88880
Compare

Adds an AWS handler shim that handles tunnel events before they hit the user handler.
Note for reviewers: if you are lacking context on this PR, check #25997