Repository navigation
test(e2e): Use an external host address for the Lambda DSN on loopback hostnames - #25282
Merged
Merged
Conversation
JPeer264
added this pull request to stack #25283
October 12, 2026 12:19
JPeer264
marked this pull request as ready for review
October 12, 2026 12:29
JPeer264
force-pushed
the
jp/aws-e2e-loopback-host
branch
from
October 12, 2026 12:33
9e3784b to
9583652
Compare
andreiborza
approved these changes
Oct 12, 2026
msonnb
approved these changes
Oct 13, 2026
JPeer264
removed this pull request from stack #25283
October 13, 2026 15:29
JPeer264
added this pull request to stack #25335
October 13, 2026 15:29
…k hostnames The AWS serverless E2E apps point the Lambda's DSN at the host IP that the runner's hostname resolves to. On Namespace runners the hostname resolves to 127.0.0.1, which inside the Lambda container is the container itself, so no event reached the event proxy and every test timed out. When the hostname resolves to a loopback address, use the first external IPv4 address that is not a Docker bridge. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
JPeer264
force-pushed
the
jp/aws-e2e-loopback-host
branch
from
October 13, 2026 15:36
9583652 to
1d8c6bd
Compare
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
4 participants
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.
Even if we would stay on GHA runners for now, it is still good to keep this one in as this could also happen locally.
The AWS serverless E2E apps point the DSN of the Lambda at the address that the hostname of the runner resolves to. When that address is a loopback address, they now use the first external IPv4 address that is not a Docker bridge.
Why
On Namespace runners the hostname resolves to
127.0.0.1. Inside the Lambda container, that is the container itself, so no event reached the event proxy, and each test timed out after 180 s. On GitHub runners the hostname resolves to the address of the VM, so nothing changes there.Failed on CI: https://github.com/getsentry/sentry-javascript/actions/runs/38033058956/job/114158845637