-
Notifications
You must be signed in to change notification settings - Fork 0
fix(audit): pair every audit request entry with a response (WP35) #1601
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
32 commits
Select commit
Hold shift + click to select a range
7565b82
feat(audit): pair every request entry with a response
jeremi c66be30
fix(casework): pair every audited request with a response
jeremi e4a9cd8
test(casework): expect a withheld result to pair its request entry
jeremi f17ed10
fix(scheduling): answer every commitment request entry
jeremi ca0c54b
fix(render): pair each call's audit entries under a server-drawn id
jeremi b85ceaf
fix(breg): answer every audited request entry
jeremi fe92918
fix(hooks): record delivery outcomes only after they commit
jeremi 368ce72
docs: describe the audit request pairing guarantee
jeremi 94e761c
test(breg): expect a faulted mutation to answer its attempt
jeremi 747a32f
test(breg): expect faulted reads and tombstones to answer their attempt
jeremi 8c05a59
docs(breg): enforce BREG-V1-27
jeremi 68157f5
docs: anchor the audit pairing claims in the retention page
jeremi d7161db
fix(breg): answer maintenance request entries that end early
jeremi eab4baf
fix(audit): keep request pairing through cancellation
jeremi 474ac05
fix(hooks): resolve an unacknowledged commit before auditing it
jeremi 4c5ed4d
fix(hooks): answer an operator replay whose caller left
jeremi ba58367
fix(breg): resolve erasure and receipt outcomes before auditing them
jeremi c398681
fix(audit): claim a request for a response appended in its name
jeremi 91ece62
fix(breg): read back retention and reconcile outcomes after commit er…
jeremi f2c8221
fix(audit): queue a dropped request's file response outside a runtime
jeremi f94e9a7
fix(hooks): recognize retry and dead-letter commits after later progress
jeremi 6cad728
fix(audit): answer a request once when a claim races its drop or shut…
jeremi ebd09b5
fix(breg): hold an Evidence action's attempt until its terminal answe…
jeremi 62d28e2
fix(breg): record a committed erasure before retrying external deletions
jeremi d8da69b
fix(breg): answer an ingestion transition unfinished when its commit …
jeremi 487a4f8
fix(hooks): answer every delivery transition whose commit fate is unk…
jeremi 476e213
docs(breg): scope audit pairing to a running process in BREG-V1-27
jeremi fcf54eb
fix(casework): write an operation's whole response tail even when its…
jeremi 2c65e43
fix(casework): read back a commit whose acknowledgment was lost befor…
jeremi 4108d34
fix(casework): name the review request a review note's request entry …
jeremi d7010a4
fix(scheduling): read back a capacity commit whose acknowledgment was…
jeremi 3dd1be2
docs(site): state what the BReg and Render audit journals record when…
jeremi 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
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.
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 this erasure's commit rolls back after returning an ambiguous error, a concurrent
erase-expiredinvocation can delete the same rows beforeexpired_evidence_remainsruns;Some(false)then attributes the second invocation's deletion to the first and records the first request aserasedwith its speculative count. Fresh evidence beyond the prior read-back fix is that the recovery predicate is not transaction-specific; use the original transaction status or a request-specific durable marker instead.AGENTS.md reference: products/breg/AGENTS.md:L175-L182
Useful? React with 👍 / 👎.