Incident Dossier

Deadline Truncated Silently

A long-running fan-out job was returning inconsistent reports: most jobs ran cleanly but a fraction delivered partial results that downstream consumers treated as complete. The audit log showed the upstream operation had taken longer than the configured budget for those jobs, yet no timeout error was raised — the partial result had been returned without any signal that it was incomplete.

Initial failing signalDeadline check is missing after the operation resolvesExpected behavior: operation past deadline rejects with DeadlineExceeded · actual behavior: operation past deadline silently returns the partial result

Progress

1Reproduce the bugRun checks

2Edit the fixOpen

3Pass checksOpen

4Submit fixOpen

Reproduction Steps

Run npm test.
Inspect runWithDeadline and ask what happens to the deadline value after the operation resolves.
Notice that the deadline is computed but never compared to the clock again.
Re-check the injected clock after the operation and reject with DeadlineExceeded when the deadline has passed.

Focus Mode

Start

src/deadline.js

Likely area

src/deadline.js

Challenge Coach

Hints reveal broad direction first, then narrow toward the suspect path without showing hidden tests or exact solution code.

TopicReliability

DifficultyHard

Est. time28 min

Workspacepreparing

Explorer

Loading files

Evidence Map

Failing signal loaded from challenge API
Workspace files loaded from workspace API
Results rendered only after API run/submit

Autosaved

workspace

Outputread-onlyready$ prepare workspace

Preparing workspace