Repository navigation
fix(web): a pending approval is announced once, not once per queued message #25866
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
juliusmarminge
wants to merge
4
commits into
main
Choose a base branch
from
fix/issue-24882
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.
+38
−10
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
6d7d6dc
test(web): reproduce repeated approval notifications for queued runs …
juliusmarminge 107c2c9
fix(web): a pending approval notifies once while runs queue behind it
juliusmarminge 8e83c58
fix(web): overlapping requests no longer re-announce the older one
juliusmarminge 9ef95eb
Merge remote-tracking branch 'origin/main' into fix/issue-24882
juliusmarminge 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.
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.
Script executed:
Repository: pingdotgg/t3code
Length of output: 9440
Script executed:
Repository: pingdotgg/t3code
Length of output: 23116
Script executed:
Repository: pingdotgg/t3code
Length of output: 37155
Script executed:
Repository: pingdotgg/t3code
Length of output: 6476
Script executed:
Repository: pingdotgg/t3code
Length of output: 3399
Announce each distinct pending request once during the waiting period.
When request B appears while request A remains pending, both observations use the same
"approval"or"input"attention value. The gate does not notify for B. The request ID is available onrawThread.pendingRuntimeRequest, so track announced request IDs during the waiting period. Clear that set when the thread stops waiting. Do not announce A again when it becomes visible after B.This is a narrow overlapping-request case, so classify it as a minor correctness issue rather than a major regression. The added test and source comment explicitly accept the status-only tradeoff for queued and overlapping requests. The previous run-plus-status key notified for B only when B coincided with a changed latest run, while also re-announcing A for queued runs.