Devin PR broke ledger list API and created buckets on deleted resources
Quick Answer
Devin caused a low-severity (3.4/10) logic error failure: Devin PR broke ledger list API and created buckets on deleted resources. The root cause was scope misunderstanding. PR closed without merge.
Description
Devin submitted a PR to implement bucket deletion in Formance Ledger. The maintainer (gfyrag) found multiple issues: the ledger list endpoint was broken by the changes, the PR allowed creating new ledgers on deleted buckets (a logic error), test naming conventions were violated, and handler filename conventions were ignored. Despite passing CI, the PR required extensive human review to catch these architectural issues.
Instruction Given
Implement bucket deletion functionality for the Formance Ledger system
Expected Behavior
Implement soft-delete and hard-delete for buckets while maintaining existing API contracts and following project conventions
Actual Behavior
Broke the ledger list endpoint, allowed creating ledgers on deleted buckets, used inconsistent test/handler naming conventions. 65% code coverage with 142 lines missing coverage.
Impact / Damage
PR closed without merge. Maintainer had to provide 4+ review comments pointing out broken functionality and convention violations. Wasted reviewer time.
Frequently Asked Questions
What happened in incident STUPID-2026-0011? ▾
Devin submitted a PR to implement bucket deletion in Formance Ledger. The maintainer (gfyrag) found multiple issues: the ledger list endpoint was broken by the changes, the PR allowed creating new ledgers on deleted buckets (a logic error), test naming conventions were violated, and handler filename conventions were ignored. Despite passing CI, the PR required extensive human review to catch these architectural issues.
Which AI agent caused this failure? ▾
Devin was responsible for this logic error incident, documented as STUPID-2026-0011 in the StupidLLM AI agent incident database.
How severe was this AI agent failure? ▾
It is rated 3.4/10 (low) on StupidLLM's CVSS-style severity scale for AI agent failures, based on damage type, reversibility, and scope.
What was the root cause? ▾
The root cause was classified as scope misunderstanding. Implement soft-delete and hard-delete for buckets while maintaining existing API contracts and following project conventions
What was the impact or damage? ▾
PR closed without merge. Maintainer had to provide 4+ review comments pointing out broken functionality and convention violations. Wasted reviewer time.