Repository navigation
test(issues): Wait for issue counts instead of toast dismissal - #126793
Merged
Merged
Conversation
Loading and success toasts can disappear or replace each other before the issue list updates. Wait for the expected issue count after bulk actions. Co-Authored-By: Codex <noreply@openai.com>
scttcper
marked this pull request as ready for review
October 7, 2026 21:33
kcons
approved these changes
Oct 7, 2026
3 tasks done
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.
Wait for the expected issue count after bulk actions instead of dismissing loading/success toasts that can race with the list update.
CI example: resolving an issue hits a stale toast element, then passes on retry. Delaying the response locally also reproduces an early return before the row disappears.