Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

🤖 tests: reportDecisionHold "(row running)" times out waiting for held input in CI

Open
#7,321 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
bun, typescript
Domain
testing

Research direction

Start with src/node/services/taskService.reportDecisionHold.test.ts, especially the until helper at line 137 and the failing case near line 1007; compare its setup with the passing “row reported” case. Reproduce the timeout under CI-like conditions and trace why held input is not observed after the decision settles and queue drains. Done when the cause is identified and the case is reliable without masking genuine failures.

Written by the indexing model from the issue text.

Description

Summary

One case of src/node/services/taskService.reportDecisionHold.test.ts timed out in CI and dropped a PR from the merge queue. The test is "report-decision hold for queued follow-ups (real host) > a report read while the stream end is deferred refuses the held follow-up as indeterminate (row running)". It waited 5 s for the held input and failed at 5247 ms. It does not fail locally.

Case

  • 2026-10-23 08:50 UTC, merge group of #7313 (head 99c0798faa on main 9c1eb8932d), Test / Unit (3/6), job 120326505217.
  • The error is timed out waiting for held input, from the until helper at line 137, called at line 1007. The steps before it passed: "decision settled" and "queue drained".
  • The ENOTDIR stack traces just before it in the log come from the previous test. That test writes a file at the parent session dir on purpose (line 909).
  • The other case of the same test ("row reported") passed in the same run in 259 ms.

Local runs

The file ran 30 times on each head, 4 copies at a time, with Bun 1.4.3:

Head Failed runs
#7313 head e7bc62803d 0 of 30
origin/main 9c1eb8932d 0 of 30

Each run takes about 4 s. The case takes 99 to 120 ms locally on both heads. The loop-test tripwire of #7313, which includes this file, found 0 trips. So I do not count it as a defect of #7313. I did not find the cause.

Related

  • #4458, #4558, #5010 and #5065 (all closed) were earlier flakes of the same file.
  • Refs #7255. Builders of that refactor rerun this test alone when it fails, and compare it with origin/main.

Generated with xum • Model: anthropic:claude-opus-5-5 • Thinking: max • Cost: $139.60

Dominant language
TypeScript
Stars
2.1k
Forks
140
Avg merge
5h 8m
Merged PRs (30d)
952

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from coder/xum

All issues in coder/xum

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.