-
Notifications
You must be signed in to change notification settings - Fork 7
fix(review): gate idempotency on a recorded verdict, not run status #344
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
Open
neversettle17-101
wants to merge
8
commits into
main
Choose a base branch
from
ao/agent-orchestrator-6/fix-stale-running-review-342
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+151
−21
Open
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
f2a5a8d
fix(review): retry review when a stale Running pass's reviewer died
neversettle17-101 177eb76
fix(review): gate idempotency on a recorded verdict, not run liveness
neversettle17-101 ad0e0a4
Test
neversettle17-101 a0849ec
Revert "Test"
neversettle17-101 ec0b9b2
Test - 2
neversettle17-101 dd5bc64
Update review.go
neversettle17-101 32da2bf
fix(review): restore domain.VerdictNone in idempotency check
neversettle17-101 25b74da
feat(review): gate re-review block on Status==Complete; lock state ma…
neversettle17-101 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
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.
Non-blocking, just flagging the behavior change: previously a repeat
Triggeragainst a genuinely live, in-progress review (Running, pane alive, not yet submitted) was a pure no-op that returned the existing run. Now it always supersedes — the in-progress run is markedFailed("superseded by a new review trigger") and a fresh run is created, re-Notifying the live pane. Since the only caller is the user-initiatedPOST /reviews/triggerbutton, this reads as "re-run the review," which is reasonable, and the test comments call it out. Worth confirming nothing auto-polls this endpoint, since on a poll loop it would keep killing an in-flight review before it can submit. From what I can see it's button-only, so this is fine.