This is the record of an abcd-managed repository

abcdBetav0.16.2 · 2026-11-06

Development record

A context-bound git read can fail on a loaded machine after git has already answered: isolatedGitContext (internal/gitutil/repo.go) sets WaitDelay to 50 ms whenever the context can end, and exec starts that timer when git exits on its own, so the copy of git's output can miss it and Wait reports exec.ErrWaitDelay over a successful git. The status reader runs under a deadline, so on 2026-10-27 TestADoubtfulAnnouncementIsFlaggedAndEveryOtherBranchStillRead (internal/core/claim/status_test.go:300) failed a records-only preflight with 'reading the status branches: exec: WaitDelay expired before I/O complete', and in use the prompt hook would print 'status unavailable' for the same reason. The fix for iss-2610100846469473 removed the delay only for callers with no deadline.

issueresolvedminoriss-2610272041031418

A context-bound git read can fail on a loaded machine after git has already answered: isolatedGitContext (internal/gitutil/repo.go) sets WaitDelay to 50 ms whenever the context can end, and exec starts that timer when git exits on its own, so the copy of git's output can miss it and Wait reports exec.ErrWaitDelay over a successful git. The status reader runs under a deadline, so on 2026-10-27 TestADoubtfulAnnouncementIsFlaggedAndEveryOtherBranchStillRead (internal/core/claim/status_test.go:300) failed a records-only preflight with 'reading the status branches: exec: WaitDelay expired before I/O complete', and in use the prompt hook would print 'status unavailable' for the same reason. The fix for iss-2610100846469473 removed the delay only for callers with no deadline.

Frontmatter

idiss-2610272041031418
typeissue
lifecycleresolved
severityminor

mentions1