Mastodon Feed: Post

Mastodon Feed

jonny@neuromatch.social ("jonny (nonvenomous)") wrote:

This shit is so funny to me man, I could read these bug reports forever

This person reports how they tried to get fable to build a thing to process some data, but instead burned 12 days of usage on it generating thousands of commits and hundreds of GB of data doing absolutely nothing. It was supposed to build some validation thing that wraps the data processing pipeline, but it never built the pipeline itself, so it then went into a delirium of validating the validator and doing everything except the thing it was supposed to

https://github.com/anthropics/claude-code/issues/76987

The receipts on volume — and it's worse than the raw counts show Today is day twelve since my Fable access was restored on July 1. In that window, in this one repository, pulled just now from git: 1,816 commits 486 brand-new documents created, 1,813 documents touched 7,314 total files touched And here's the part that should stop you cold: those are the net figures — after I had to stop and clean up my disk because the mess got so bad. An agent had to archive 3,943 stale markdown files in a single commit, and the broader cleanup recovered roughly 93 GB of space (free space had been driven down to about 29 GB and came back to about 122 GB). The gross output was thousands of documents higher than the net counts show — so voluminous the project needed an automated sweeper and a manual disk cleanup just to bury the debris. Last 24 hours alone: 306 commits, 22 new docs. The night before: 251 commits, 99 new docs. This is not a tool starved for activity. It is a tool pouring enormous, metered effort into everything adjacent to the task — and, by my account, none of it into the 46 days I actually asked it to run through steps 1–7.