Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
  • Qualcosa non va?
#7,321 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
bun, typescript
Ambito
testing

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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

Lingua principale
TypeScript
Stelle
2.1k
Fork
140
Merge medio
3h 23m
PR unite (30g)
953

Preparare l'ambiente

  • Include un Dockerfile o un file Docker Compose
  • Nessun modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di coder/xum

Tutte le issue di coder/xum

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.