-
Notifications
You must be signed in to change notification settings - Fork 0
fix(notices): stable replay deliveries, admission ordering, abort-aware authorization #202
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
Merged
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,8 @@ | ||
| --- | ||
| "@agent-bundle/runtime": patch | ||
| --- | ||
|
|
||
| Keep next-event notice admission deterministic across invocation replays, | ||
| scope replayed deliveries to the matching principal, exclude notices created | ||
| after an event started, and interrupt delivery authorization when the request | ||
| is aborted. |
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
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
Oops, something went wrong.
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.
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 event reuses an invocation ID that previously admitted a notice but supplies a different principal, and there are no pending candidates for the new principal, the dispatch block is skipped and this scan returns the prior principal's attempted notice solely by invocation ID. Since invocation IDs are caller-provided and
deliveryFordoes not check the current principal, this exposes notice content across authorization boundaries; always replay the stored admission through the idempotent dispatch (including empty admissions) or otherwise verify that the current principal matches the original admission.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.
Fixed in 05b58ac (merged to main as d63dd3b): replayed deliveries are filtered through recipientMatchesPrincipal before receipt matching, so an invocation id reused by a different principal observes only its own (empty) set — the receipt contract records no principal, so the notice recipient is the strictest available binding. Regression test interleaves a foreign principal between the first run and the replay.