Understand the failure.
Verify the repair.
Small, reproducible software failures. The broken implementation, the fix that didn’t work, and the one that passed—preserved together.
Explore the cases ↓How results are verified ↗WHAT THE ARCHIVE CONTAINS
100840 executable cases. 20168 are open.
Every case records the implementation that fails, the fix that did not work, and the repair that passed its checks—with recorded outputs and source hashes. This release adds 100840 cases across 20168 failure mechanisms and 254 domains.
The open tier gives you the failure and the unsuccessful fix for one case in every mechanism. The remaining 80672 cases, 5 variants per mechanism, are member-only: the verified repair, its recorded checks, and the full fixture suite are held in the member archive. Read the methodology ↗
A RECORD OF WHAT WENT WRONG
Browse the archive / 100840
Escalating failure penalty box: ban still active at its end instant · case 01
A client retrying exactly when told the ban ends is still refused.
Escalating failure penalty box: ban still active at its end instant · case 02
A client retrying exactly when told the ban ends is still refused.
Escalating failure penalty box: ban still active at its end instant · case 03
A client retrying exactly when told the ban ends is still refused.
Escalating failure penalty box: ban still active at its end instant · case 04
A client retrying exactly when told the ban ends is still refused.
Escalating failure penalty box: ban still active at its end instant · case 05
A client retrying exactly when told the ban ends is still refused.
Escalating failure penalty box: first ban already doubled · case 01
The first offence is banned for twice the configured base duration.
Escalating failure penalty box: first ban already doubled · case 02
The first offence is banned for twice the configured base duration.
Escalating failure penalty box: first ban already doubled · case 03
The first offence is banned for twice the configured base duration.
Escalating failure penalty box: first ban already doubled · case 04
The first offence is banned for twice the configured base duration.
Escalating failure penalty box: first ban already doubled · case 05
The first offence is banned for twice the configured base duration.
Escalating failure penalty box: failure log survives the ban · case 01
The first failure after a ban immediately triggers another, longer ban.
Escalating failure penalty box: failure log survives the ban · case 02
The first failure after a ban immediately triggers another, longer ban.
Escalating failure penalty box: failure log survives the ban · case 03
The first failure after a ban immediately triggers another, longer ban.
Escalating failure penalty box: failure log survives the ban · case 04
The first failure after a ban immediately triggers another, longer ban.
Escalating failure penalty box: failure log survives the ban · case 05
The first failure after a ban immediately triggers another, longer ban.
Escalating failure penalty box: failure exactly one window old still counted · case 01
Two failures exactly one window apart trigger a ban.
Escalating failure penalty box: failure exactly one window old still counted · case 02
Two failures exactly one window apart trigger a ban.
Escalating failure penalty box: failure exactly one window old still counted · case 03
Two failures exactly one window apart trigger a ban.
Escalating failure penalty box: failure exactly one window old still counted · case 04
Two failures exactly one window apart trigger a ban.
Escalating failure penalty box: failure exactly one window old still counted · case 05
Two failures exactly one window apart trigger a ban.
Escalating failure penalty box: failures during a ban are recorded · case 01
Attempts made while banned count toward the next ban.
Escalating failure penalty box: failures during a ban are recorded · case 02
Attempts made while banned count toward the next ban.
Escalating failure penalty box: failures during a ban are recorded · case 03
Attempts made while banned count toward the next ban.
Escalating failure penalty box: failures during a ban are recorded · case 04
Attempts made while banned count toward the next ban.
Escalating failure penalty box: failures during a ban are recorded · case 05
Attempts made while banned count toward the next ban.
Daily quota reset at local midnight: offset applied with the wrong sign · case 01
Quotas reset at the mirror-image hour: customers east of UTC reset in the afternoon.
Daily quota reset at local midnight: offset applied with the wrong sign · case 02
Quotas reset at the mirror-image hour: customers east of UTC reset in the afternoon.
Daily quota reset at local midnight: offset applied with the wrong sign · case 03
Quotas reset at the mirror-image hour: customers east of UTC reset in the afternoon.
Daily quota reset at local midnight: offset applied with the wrong sign · case 04
Quotas reset at the mirror-image hour: customers east of UTC reset in the afternoon.
Daily quota reset at local midnight: offset applied with the wrong sign · case 05
Quotas reset at the mirror-image hour: customers east of UTC reset in the afternoon.
Daily quota reset at local midnight: reset time reported as UTC midnight · case 01
Clients are told the quota resets at a local-midnight number interpreted as a UTC epoch.
Daily quota reset at local midnight: reset time reported as UTC midnight · case 02
Clients are told the quota resets at a local-midnight number interpreted as a UTC epoch.
Daily quota reset at local midnight: reset time reported as UTC midnight · case 03
Clients are told the quota resets at a local-midnight number interpreted as a UTC epoch.
Daily quota reset at local midnight: reset time reported as UTC midnight · case 04
Clients are told the quota resets at a local-midnight number interpreted as a UTC epoch.
Daily quota reset at local midnight: reset time reported as UTC midnight · case 05
Clients are told the quota resets at a local-midnight number interpreted as a UTC epoch.
Daily quota reset at local midnight: denied request burns the remaining quota · case 01
A request slightly too large for the remaining quota wipes out the rest of the day.
Daily quota reset at local midnight: denied request burns the remaining quota · case 02
A request slightly too large for the remaining quota wipes out the rest of the day.
Daily quota reset at local midnight: denied request burns the remaining quota · case 03
A request slightly too large for the remaining quota wipes out the rest of the day.
Daily quota reset at local midnight: denied request burns the remaining quota · case 04
A request slightly too large for the remaining quota wipes out the rest of the day.
Daily quota reset at local midnight: denied request burns the remaining quota · case 05
A request slightly too large for the remaining quota wipes out the rest of the day.
Daily quota reset at local midnight: usage resets at UTC midnight · case 01
Usage resets at UTC midnight while the advertised reset time is local midnight.
Daily quota reset at local midnight: usage resets at UTC midnight · case 02
Usage resets at UTC midnight while the advertised reset time is local midnight.
Daily quota reset at local midnight: usage resets at UTC midnight · case 03
Usage resets at UTC midnight while the advertised reset time is local midnight.
Daily quota reset at local midnight: usage resets at UTC midnight · case 04
Usage resets at UTC midnight while the advertised reset time is local midnight.
Daily quota reset at local midnight: usage resets at UTC midnight · case 05
Usage resets at UTC midnight while the advertised reset time is local midnight.
Reservation limiter with stored permits: request waits for its own permits · case 01
A large first request is delayed instead of the following caller, defeating the reservation design.
Reservation limiter with stored permits: request waits for its own permits · case 02
A large first request is delayed instead of the following caller, defeating the reservation design.
Reservation limiter with stored permits: request waits for its own permits · case 03
A large first request is delayed instead of the following caller, defeating the reservation design.
Reservation limiter with stored permits: request waits for its own permits · case 04
A large first request is delayed instead of the following caller, defeating the reservation design.
Reservation limiter with stored permits: request waits for its own permits · case 05
A large first request is delayed instead of the following caller, defeating the reservation design.
Reservation limiter with stored permits: stored permits unbounded · case 01
After a long idle period the limiter releases an arbitrarily large burst.
Reservation limiter with stored permits: stored permits unbounded · case 02
After a long idle period the limiter releases an arbitrarily large burst.
Reservation limiter with stored permits: stored permits unbounded · case 03
After a long idle period the limiter releases an arbitrarily large burst.
Reservation limiter with stored permits: stored permits unbounded · case 04
After a long idle period the limiter releases an arbitrarily large burst.
Reservation limiter with stored permits: stored permits unbounded · case 05
After a long idle period the limiter releases an arbitrarily large burst.
Reservation limiter with stored permits: stored permits never consumed · case 01
A burst allowance is reused by every request, so the limiter never throttles after idleness.
Reservation limiter with stored permits: stored permits never consumed · case 02
A burst allowance is reused by every request, so the limiter never throttles after idleness.
Reservation limiter with stored permits: stored permits never consumed · case 03
A burst allowance is reused by every request, so the limiter never throttles after idleness.
Reservation limiter with stored permits: stored permits never consumed · case 04
A burst allowance is reused by every request, so the limiter never throttles after idleness.
Reservation limiter with stored permits: stored permits never consumed · case 05
A burst allowance is reused by every request, so the limiter never throttles after idleness.
Reservation limiter with stored permits: idle resync leaves next_free in the past · case 01
Idle time is credited again at the next request and fresh permits are scheduled in the past.
Reservation limiter with stored permits: idle resync leaves next_free in the past · case 02
Idle time is credited again at the next request and fresh permits are scheduled in the past.
Reservation limiter with stored permits: idle resync leaves next_free in the past · case 03
Idle time is credited again at the next request and fresh permits are scheduled in the past.
Reservation limiter with stored permits: idle resync leaves next_free in the past · case 04
Idle time is credited again at the next request and fresh permits are scheduled in the past.
Reservation limiter with stored permits: idle resync leaves next_free in the past · case 05
Idle time is credited again at the next request and fresh permits are scheduled in the past.
Reservation limiter with stored permits: wait truncated · case 01
Callers sleep slightly too little and run ahead of the configured rate.
Reservation limiter with stored permits: wait truncated · case 02
Callers sleep slightly too little and run ahead of the configured rate.
Reservation limiter with stored permits: wait truncated · case 03
Callers sleep slightly too little and run ahead of the configured rate.
Reservation limiter with stored permits: wait truncated · case 04
Callers sleep slightly too little and run ahead of the configured rate.
Reservation limiter with stored permits: wait truncated · case 05
Callers sleep slightly too little and run ahead of the configured rate.
Priority limiter with reserved high-priority capacity: low traffic ignores total usage · case 01
When high traffic is heavy, low requests are still admitted and the window exceeds capacity.
Priority limiter with reserved high-priority capacity: low traffic ignores total usage · case 02
When high traffic is heavy, low requests are still admitted and the window exceeds capacity.
Priority limiter with reserved high-priority capacity: low traffic ignores total usage · case 03
When high traffic is heavy, low requests are still admitted and the window exceeds capacity.
Priority limiter with reserved high-priority capacity: low traffic ignores total usage · case 04
When high traffic is heavy, low requests are still admitted and the window exceeds capacity.
Priority limiter with reserved high-priority capacity: low traffic ignores total usage · case 05
When high traffic is heavy, low requests are still admitted and the window exceeds capacity.
Priority limiter with reserved high-priority capacity: high admissions counted as low · case 01
High-priority traffic consumes the low share, so bulk clients are throttled by critical traffic.
Priority limiter with reserved high-priority capacity: high admissions counted as low · case 02
High-priority traffic consumes the low share, so bulk clients are throttled by critical traffic.
Priority limiter with reserved high-priority capacity: high admissions counted as low · case 03
High-priority traffic consumes the low share, so bulk clients are throttled by critical traffic.
Priority limiter with reserved high-priority capacity: high admissions counted as low · case 04
High-priority traffic consumes the low share, so bulk clients are throttled by critical traffic.
Priority limiter with reserved high-priority capacity: high admissions counted as low · case 05
High-priority traffic consumes the low share, so bulk clients are throttled by critical traffic.
Priority limiter with reserved high-priority capacity: high counter never resets · case 01
After a few windows the high counter alone fills capacity and everything is denied.
Priority limiter with reserved high-priority capacity: high counter never resets · case 02
After a few windows the high counter alone fills capacity and everything is denied.
Priority limiter with reserved high-priority capacity: high counter never resets · case 03
After a few windows the high counter alone fills capacity and everything is denied.
Priority limiter with reserved high-priority capacity: high counter never resets · case 04
After a few windows the high counter alone fills capacity and everything is denied.
Priority limiter with reserved high-priority capacity: high counter never resets · case 05
After a few windows the high counter alone fills capacity and everything is denied.
Priority limiter with reserved high-priority capacity: unknown labels treated as high · case 01
Batch jobs tagged with a new label bypass the reserve and consume capacity meant for critical traffic.
Priority limiter with reserved high-priority capacity: unknown labels treated as high · case 02
Batch jobs tagged with a new label bypass the reserve and consume capacity meant for critical traffic.
Priority limiter with reserved high-priority capacity: unknown labels treated as high · case 03
Batch jobs tagged with a new label bypass the reserve and consume capacity meant for critical traffic.
Priority limiter with reserved high-priority capacity: unknown labels treated as high · case 04
Batch jobs tagged with a new label bypass the reserve and consume capacity meant for critical traffic.
Priority limiter with reserved high-priority capacity: unknown labels treated as high · case 05
Batch jobs tagged with a new label bypass the reserve and consume capacity meant for critical traffic.
Priority limiter with reserved high-priority capacity: window length off by a factor of ten · case 01
Counters reset every tenth of a second, so the per-second capacity is admitted ten times over.
Priority limiter with reserved high-priority capacity: window length off by a factor of ten · case 02
Counters reset every tenth of a second, so the per-second capacity is admitted ten times over.
Priority limiter with reserved high-priority capacity: window length off by a factor of ten · case 03
Counters reset every tenth of a second, so the per-second capacity is admitted ten times over.
Priority limiter with reserved high-priority capacity: window length off by a factor of ten · case 04
Counters reset every tenth of a second, so the per-second capacity is admitted ten times over.
Priority limiter with reserved high-priority capacity: window length off by a factor of ten · case 05
Counters reset every tenth of a second, so the per-second capacity is admitted ten times over.
Distributed limiter with leased quota chunks: chunk granted beyond the remaining quota · case 01
The fleet collectively admits more than the global quota.
Distributed limiter with leased quota chunks: chunk granted beyond the remaining quota · case 02
The fleet collectively admits more than the global quota.
Distributed limiter with leased quota chunks: chunk granted beyond the remaining quota · case 03
The fleet collectively admits more than the global quota.
Distributed limiter with leased quota chunks: chunk granted beyond the remaining quota · case 04
The fleet collectively admits more than the global quota.
Distributed limiter with leased quota chunks: chunk granted beyond the remaining quota · case 05
The fleet collectively admits more than the global quota.
INSPECTABLE BY DESIGN
Every result has a runnable source.
Runnable implementations with recorded outputs, source hashes, and explicit contracts. Related variants share a failure mechanism and belong together in evaluation splits.
Read the methodology ↗