fix(runtime): Keep resource events out of steering#1014
Draft
sentry-junior[bot] wants to merge 2 commits into
Draft
fix(runtime): Keep resource events out of steering#1014sentry-junior[bot] wants to merge 2 commits into
sentry-junior[bot] wants to merge 2 commits into
Conversation
Co-Authored-By: David Cramer <david@sentry.io>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
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.
Resource-event notifications that arrive during an active turn now remain queued for the next subscribed turn instead of entering the live steering drain. This keeps provider updates in the follow-up path while preserving steering for user-authored instructions.
Queue separation
The Slack mailbox drain excludes records whose durable source is
resource_event, leaving them pending for the worker’s next slice. A component regression test covers an event arriving after the active input is acknowledged.Typecheck passes. The targeted component suite is locally blocked because Postgres is unavailable at
127.0.0.1:54322; CI will run it.Requested by David Cramer via Junior.
--
View Junior Session