🤖 tests: sendModeDropdown 'send after step' waits only 1 s for the stream to start
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 84/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- testing
Research direction
Open tests/ui/chat/sendModeDropdown.test.ts and inspect the waitFor for canInterrupt around line 207; compare it with the sibling wait around line 240. Add an explicit load-tolerant timeout to the first wait, then run the focused test and confirm it passes.
Written by the indexing model from the issue text.
Description
tests/ui/chat/sendModeDropdown.test.ts › "send after step waits for every tool call emitted in the current step" failed in CI with "Expected the source turn to be streaming before queueing".
- Seen once: PR #5801 head 76c52aa2bb, run 37537817431, job 112523650492 ("Test / Integration (1/3)"). The message appears twice in that job because jest prints its failure summary twice.
- The same test passed in CI on the next head (a0ca2001af), and the whole file passed 10 of 10 local runs on that head.
- A scan of the last 40 failed
PRworkflow runs found the message only in that job.
Likely cause (not proven): the waitFor for canInterrupt at sendModeDropdown.test.ts:207 sets no timeout, so it uses the testing-library default of 1000 ms. A sibling test waits for the same condition with { timeout: 30_000 } (around line 240). On a loaded runner the stream can take more than 1 s to start.
Fix idea: give that wait an explicit load-tolerant timeout, as the sibling test does.
The PR #5801 readiness check found that its changes cannot reach this path: the failing wait runs before any composer edit code, and the only send before it is a normal send.
Generated with xum • Model: anthropic:claude-opus-5-5 • Thinking: high • Cost: $33.65
- Dominant language
- TypeScript
- Stars
- 2k
- Forks
- 140
- Avg merge
- 5h 59m
- Merged PRs (30d)
- 935
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from coder/xum
-
backlog
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
backlog
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
backlog
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
backlog
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
backlog
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 84/100
answerLoops/answerLoops#345 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
siyuan-note/siyuan#20313 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
LanternOps/breeze#8254 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
gofish-graphics/gofish-graphics#1084 ·
Maintainers usually reply within 1 day