Repository navigation
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.
fix(id): reset DogStatsD buffers on identity refresh #10339
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Uh oh!
There was an error while loading. Please reload this page.
fix(id): reset DogStatsD buffers on identity refresh #10339
Changes from all commits
b8e2848File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When an identity refresh occurs after
request()starts but before its DNS/connect/write completes, this generation check runs only in the response callback, after the old buffer may already have been transmitted. Consequently, each resumed MicroVM clone can still submit the pre-snapshot HTTP payload; the guard merely suppresses its telemetry and UDP fallback. Track and abort active HTTP requests duringupdateTags(), and cover this sibling of the UDP/DNS case.AGENTS.md reference: AGENTS.md:L79-L79
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When a MicroVM snapshot is taken after
socket.send()is queued but before it completes, this generation check runs only from the completion callback, after libuv has already accepted the old buffer; each resumed clone can therefore still transmit the stale datagram. The new pending-callback test confirms only that stale completions are ignored, not that the packets are canceled. Track and invalidate the outstanding UDP transport at refresh, and cover the sibling case by asserting that a receiver gets no pre-refresh packet.AGENTS.md reference: AGENTS.md:L78-L79
Useful? React with 👍 / 👎.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.