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
Match query-aware redirect rules against repeated decoded query fields: decoded value match · case 01
Match query-aware redirect rules against repeated decoded query fields: the decoded value match branch emits an incorrect decision.
Match query-aware redirect rules against repeated decoded query fields: decoded value match · case 02
Match query-aware redirect rules against repeated decoded query fields: the decoded value match branch emits an incorrect decision.
Match query-aware redirect rules against repeated decoded query fields: decoded value match · case 03
Match query-aware redirect rules against repeated decoded query fields: the decoded value match branch emits an incorrect decision.
Match query-aware redirect rules against repeated decoded query fields: decoded value match · case 04
Match query-aware redirect rules against repeated decoded query fields: the decoded value match branch emits an incorrect decision.
Match query-aware redirect rules against repeated decoded query fields: decoded value match · case 05
Match query-aware redirect rules against repeated decoded query fields: the decoded value match branch emits an incorrect decision.
Match query-aware redirect rules against repeated decoded query fields: missing is not empty · case 01
Match query-aware redirect rules against repeated decoded query fields: the missing is not empty branch emits an incorrect decision.
Match query-aware redirect rules against repeated decoded query fields: missing is not empty · case 02
Match query-aware redirect rules against repeated decoded query fields: the missing is not empty branch emits an incorrect decision.
Match query-aware redirect rules against repeated decoded query fields: missing is not empty · case 03
Match query-aware redirect rules against repeated decoded query fields: the missing is not empty branch emits an incorrect decision.
Match query-aware redirect rules against repeated decoded query fields: missing is not empty · case 04
Match query-aware redirect rules against repeated decoded query fields: the missing is not empty branch emits an incorrect decision.
Match query-aware redirect rules against repeated decoded query fields: missing is not empty · case 05
Match query-aware redirect rules against repeated decoded query fields: the missing is not empty branch emits an incorrect decision.
Match query-aware redirect rules against repeated decoded query fields: all match requires presence · case 01
Match query-aware redirect rules against repeated decoded query fields: the all match requires presence branch emits an incorrect decision.
Match query-aware redirect rules against repeated decoded query fields: all match requires presence · case 02
Match query-aware redirect rules against repeated decoded query fields: the all match requires presence branch emits an incorrect decision.
Match query-aware redirect rules against repeated decoded query fields: all match requires presence · case 03
Match query-aware redirect rules against repeated decoded query fields: the all match requires presence branch emits an incorrect decision.
Match query-aware redirect rules against repeated decoded query fields: all match requires presence · case 04
Match query-aware redirect rules against repeated decoded query fields: the all match requires presence branch emits an incorrect decision.
Match query-aware redirect rules against repeated decoded query fields: all match requires presence · case 05
Match query-aware redirect rules against repeated decoded query fields: the all match requires presence branch emits an incorrect decision.
Match query-aware redirect rules against repeated decoded query fields: negation after aggregation · case 01
Match query-aware redirect rules against repeated decoded query fields: the negation after aggregation branch emits an incorrect decision.
Match query-aware redirect rules against repeated decoded query fields: negation after aggregation · case 02
Match query-aware redirect rules against repeated decoded query fields: the negation after aggregation branch emits an incorrect decision.
Match query-aware redirect rules against repeated decoded query fields: negation after aggregation · case 03
Match query-aware redirect rules against repeated decoded query fields: the negation after aggregation branch emits an incorrect decision.
Match query-aware redirect rules against repeated decoded query fields: negation after aggregation · case 04
Match query-aware redirect rules against repeated decoded query fields: the negation after aggregation branch emits an incorrect decision.
Match query-aware redirect rules against repeated decoded query fields: negation after aggregation · case 05
Match query-aware redirect rules against repeated decoded query fields: the negation after aggregation branch emits an incorrect decision.
Match query-aware redirect rules against repeated decoded query fields: exact value not substring · case 01
Match query-aware redirect rules against repeated decoded query fields: the exact value not substring branch emits an incorrect decision.
Match query-aware redirect rules against repeated decoded query fields: exact value not substring · case 02
Match query-aware redirect rules against repeated decoded query fields: the exact value not substring branch emits an incorrect decision.
Match query-aware redirect rules against repeated decoded query fields: exact value not substring · case 03
Match query-aware redirect rules against repeated decoded query fields: the exact value not substring branch emits an incorrect decision.
Match query-aware redirect rules against repeated decoded query fields: exact value not substring · case 04
Match query-aware redirect rules against repeated decoded query fields: the exact value not substring branch emits an incorrect decision.
Match query-aware redirect rules against repeated decoded query fields: exact value not substring · case 05
Match query-aware redirect rules against repeated decoded query fields: the exact value not substring branch emits an incorrect decision.
Match query-aware redirect rules against repeated decoded query fields: duplicate query occurrence count · case 01
Match query-aware redirect rules against repeated decoded query fields: the duplicate query occurrence count branch emits an incorrect decision.
Match query-aware redirect rules against repeated decoded query fields: duplicate query occurrence count · case 02
Match query-aware redirect rules against repeated decoded query fields: the duplicate query occurrence count branch emits an incorrect decision.
Match query-aware redirect rules against repeated decoded query fields: duplicate query occurrence count · case 03
Match query-aware redirect rules against repeated decoded query fields: the duplicate query occurrence count branch emits an incorrect decision.
Match query-aware redirect rules against repeated decoded query fields: duplicate query occurrence count · case 04
Match query-aware redirect rules against repeated decoded query fields: the duplicate query occurrence count branch emits an incorrect decision.
Match query-aware redirect rules against repeated decoded query fields: duplicate query occurrence count · case 05
Match query-aware redirect rules against repeated decoded query fields: the duplicate query occurrence count branch emits an incorrect decision.
Match query-aware redirect rules against repeated decoded query fields: key value conjunction · case 01
Match query-aware redirect rules against repeated decoded query fields: the key value conjunction branch emits an incorrect decision.
Match query-aware redirect rules against repeated decoded query fields: key value conjunction · case 02
Match query-aware redirect rules against repeated decoded query fields: the key value conjunction branch emits an incorrect decision.
Match query-aware redirect rules against repeated decoded query fields: key value conjunction · case 03
Match query-aware redirect rules against repeated decoded query fields: the key value conjunction branch emits an incorrect decision.
Match query-aware redirect rules against repeated decoded query fields: key value conjunction · case 04
Match query-aware redirect rules against repeated decoded query fields: the key value conjunction branch emits an incorrect decision.
Match query-aware redirect rules against repeated decoded query fields: key value conjunction · case 05
Match query-aware redirect rules against repeated decoded query fields: the key value conjunction branch emits an incorrect decision.
Match query-aware redirect rules against repeated decoded query fields: all versus any option · case 01
Match query-aware redirect rules against repeated decoded query fields: the all versus any option branch emits an incorrect decision.
Match query-aware redirect rules against repeated decoded query fields: all versus any option · case 02
Match query-aware redirect rules against repeated decoded query fields: the all versus any option branch emits an incorrect decision.
Match query-aware redirect rules against repeated decoded query fields: all versus any option · case 03
Match query-aware redirect rules against repeated decoded query fields: the all versus any option branch emits an incorrect decision.
Match query-aware redirect rules against repeated decoded query fields: all versus any option · case 04
Match query-aware redirect rules against repeated decoded query fields: the all versus any option branch emits an incorrect decision.
Match query-aware redirect rules against repeated decoded query fields: all versus any option · case 05
Match query-aware redirect rules against repeated decoded query fields: the all versus any option branch emits an incorrect decision.
Account for a redirect chain using a monotonic deadline and separate response timing: remaining monotonic · case 01
Account for a redirect chain using a monotonic deadline and separate response timing: the remaining monotonic branch emits an incorrect decision.
Account for a redirect chain using a monotonic deadline and separate response timing: remaining monotonic · case 02
Account for a redirect chain using a monotonic deadline and separate response timing: the remaining monotonic branch emits an incorrect decision.
Account for a redirect chain using a monotonic deadline and separate response timing: remaining monotonic · case 03
Account for a redirect chain using a monotonic deadline and separate response timing: the remaining monotonic branch emits an incorrect decision.
Account for a redirect chain using a monotonic deadline and separate response timing: remaining monotonic · case 04
Account for a redirect chain using a monotonic deadline and separate response timing: the remaining monotonic branch emits an incorrect decision.
Account for a redirect chain using a monotonic deadline and separate response timing: remaining monotonic · case 05
Account for a redirect chain using a monotonic deadline and separate response timing: the remaining monotonic branch emits an incorrect decision.
Account for a redirect chain using a monotonic deadline and separate response timing: headers latency · case 01
Account for a redirect chain using a monotonic deadline and separate response timing: the headers latency branch emits an incorrect decision.
Account for a redirect chain using a monotonic deadline and separate response timing: headers latency · case 02
Account for a redirect chain using a monotonic deadline and separate response timing: the headers latency branch emits an incorrect decision.
Account for a redirect chain using a monotonic deadline and separate response timing: headers latency · case 03
Account for a redirect chain using a monotonic deadline and separate response timing: the headers latency branch emits an incorrect decision.
Account for a redirect chain using a monotonic deadline and separate response timing: headers latency · case 04
Account for a redirect chain using a monotonic deadline and separate response timing: the headers latency branch emits an incorrect decision.
Account for a redirect chain using a monotonic deadline and separate response timing: headers latency · case 05
Account for a redirect chain using a monotonic deadline and separate response timing: the headers latency branch emits an incorrect decision.
Account for a redirect chain using a monotonic deadline and separate response timing: drain latency · case 01
Account for a redirect chain using a monotonic deadline and separate response timing: the drain latency branch emits an incorrect decision.
Account for a redirect chain using a monotonic deadline and separate response timing: drain latency · case 02
Account for a redirect chain using a monotonic deadline and separate response timing: the drain latency branch emits an incorrect decision.
Account for a redirect chain using a monotonic deadline and separate response timing: drain latency · case 03
Account for a redirect chain using a monotonic deadline and separate response timing: the drain latency branch emits an incorrect decision.
Account for a redirect chain using a monotonic deadline and separate response timing: drain latency · case 04
Account for a redirect chain using a monotonic deadline and separate response timing: the drain latency branch emits an incorrect decision.
Account for a redirect chain using a monotonic deadline and separate response timing: drain latency · case 05
Account for a redirect chain using a monotonic deadline and separate response timing: the drain latency branch emits an incorrect decision.
Account for a redirect chain using a monotonic deadline and separate response timing: chain latency · case 01
Account for a redirect chain using a monotonic deadline and separate response timing: the chain latency branch emits an incorrect decision.
Account for a redirect chain using a monotonic deadline and separate response timing: chain latency · case 02
Account for a redirect chain using a monotonic deadline and separate response timing: the chain latency branch emits an incorrect decision.
Account for a redirect chain using a monotonic deadline and separate response timing: chain latency · case 03
Account for a redirect chain using a monotonic deadline and separate response timing: the chain latency branch emits an incorrect decision.
Account for a redirect chain using a monotonic deadline and separate response timing: chain latency · case 04
Account for a redirect chain using a monotonic deadline and separate response timing: the chain latency branch emits an incorrect decision.
Account for a redirect chain using a monotonic deadline and separate response timing: chain latency · case 05
Account for a redirect chain using a monotonic deadline and separate response timing: the chain latency branch emits an incorrect decision.
Account for a redirect chain using a monotonic deadline and separate response timing: deadline expiration equality · case 01
Account for a redirect chain using a monotonic deadline and separate response timing: the deadline expiration equality branch emits an incorrect decision.
Account for a redirect chain using a monotonic deadline and separate response timing: deadline expiration equality · case 02
Account for a redirect chain using a monotonic deadline and separate response timing: the deadline expiration equality branch emits an incorrect decision.
Account for a redirect chain using a monotonic deadline and separate response timing: deadline expiration equality · case 03
Account for a redirect chain using a monotonic deadline and separate response timing: the deadline expiration equality branch emits an incorrect decision.
Account for a redirect chain using a monotonic deadline and separate response timing: deadline expiration equality · case 04
Account for a redirect chain using a monotonic deadline and separate response timing: the deadline expiration equality branch emits an incorrect decision.
Account for a redirect chain using a monotonic deadline and separate response timing: deadline expiration equality · case 05
Account for a redirect chain using a monotonic deadline and separate response timing: the deadline expiration equality branch emits an incorrect decision.
Account for a redirect chain using a monotonic deadline and separate response timing: wall clock log only · case 01
Account for a redirect chain using a monotonic deadline and separate response timing: the wall clock log only branch emits an incorrect decision.
Account for a redirect chain using a monotonic deadline and separate response timing: wall clock log only · case 02
Account for a redirect chain using a monotonic deadline and separate response timing: the wall clock log only branch emits an incorrect decision.
Account for a redirect chain using a monotonic deadline and separate response timing: wall clock log only · case 03
Account for a redirect chain using a monotonic deadline and separate response timing: the wall clock log only branch emits an incorrect decision.
Account for a redirect chain using a monotonic deadline and separate response timing: wall clock log only · case 04
Account for a redirect chain using a monotonic deadline and separate response timing: the wall clock log only branch emits an incorrect decision.
Account for a redirect chain using a monotonic deadline and separate response timing: wall clock log only · case 05
Account for a redirect chain using a monotonic deadline and separate response timing: the wall clock log only branch emits an incorrect decision.
Account for a redirect chain using a monotonic deadline and separate response timing: next hop deadline unchanged · case 01
Account for a redirect chain using a monotonic deadline and separate response timing: the next hop deadline unchanged branch emits an incorrect decision.
Account for a redirect chain using a monotonic deadline and separate response timing: next hop deadline unchanged · case 02
Account for a redirect chain using a monotonic deadline and separate response timing: the next hop deadline unchanged branch emits an incorrect decision.
Account for a redirect chain using a monotonic deadline and separate response timing: next hop deadline unchanged · case 03
Account for a redirect chain using a monotonic deadline and separate response timing: the next hop deadline unchanged branch emits an incorrect decision.
Account for a redirect chain using a monotonic deadline and separate response timing: next hop deadline unchanged · case 04
Account for a redirect chain using a monotonic deadline and separate response timing: the next hop deadline unchanged branch emits an incorrect decision.
Account for a redirect chain using a monotonic deadline and separate response timing: next hop deadline unchanged · case 05
Account for a redirect chain using a monotonic deadline and separate response timing: the next hop deadline unchanged branch emits an incorrect decision.
Account for a redirect chain using a monotonic deadline and separate response timing: redirect transition overhead · case 01
Account for a redirect chain using a monotonic deadline and separate response timing: the redirect transition overhead branch emits an incorrect decision.
Account for a redirect chain using a monotonic deadline and separate response timing: redirect transition overhead · case 02
Account for a redirect chain using a monotonic deadline and separate response timing: the redirect transition overhead branch emits an incorrect decision.
Account for a redirect chain using a monotonic deadline and separate response timing: redirect transition overhead · case 03
Account for a redirect chain using a monotonic deadline and separate response timing: the redirect transition overhead branch emits an incorrect decision.
Account for a redirect chain using a monotonic deadline and separate response timing: redirect transition overhead · case 04
Account for a redirect chain using a monotonic deadline and separate response timing: the redirect transition overhead branch emits an incorrect decision.
Account for a redirect chain using a monotonic deadline and separate response timing: redirect transition overhead · case 05
Account for a redirect chain using a monotonic deadline and separate response timing: the redirect transition overhead branch emits an incorrect decision.
Account for a redirect chain using a monotonic deadline and separate response timing: zero latency is observed · case 01
Account for a redirect chain using a monotonic deadline and separate response timing: the zero latency is observed branch emits an incorrect decision.
Account for a redirect chain using a monotonic deadline and separate response timing: zero latency is observed · case 02
Account for a redirect chain using a monotonic deadline and separate response timing: the zero latency is observed branch emits an incorrect decision.
Account for a redirect chain using a monotonic deadline and separate response timing: zero latency is observed · case 03
Account for a redirect chain using a monotonic deadline and separate response timing: the zero latency is observed branch emits an incorrect decision.
Account for a redirect chain using a monotonic deadline and separate response timing: zero latency is observed · case 04
Account for a redirect chain using a monotonic deadline and separate response timing: the zero latency is observed branch emits an incorrect decision.
Account for a redirect chain using a monotonic deadline and separate response timing: zero latency is observed · case 05
Account for a redirect chain using a monotonic deadline and separate response timing: the zero latency is observed branch emits an incorrect decision.
Account for a redirect chain using a monotonic deadline and separate response timing: response time does not use wall · case 01
Account for a redirect chain using a monotonic deadline and separate response timing: the response time does not use wall branch emits an incorrect decision.
Account for a redirect chain using a monotonic deadline and separate response timing: response time does not use wall · case 02
Account for a redirect chain using a monotonic deadline and separate response timing: the response time does not use wall branch emits an incorrect decision.
Account for a redirect chain using a monotonic deadline and separate response timing: response time does not use wall · case 03
Account for a redirect chain using a monotonic deadline and separate response timing: the response time does not use wall branch emits an incorrect decision.
Account for a redirect chain using a monotonic deadline and separate response timing: response time does not use wall · case 04
Account for a redirect chain using a monotonic deadline and separate response timing: the response time does not use wall branch emits an incorrect decision.
Account for a redirect chain using a monotonic deadline and separate response timing: response time does not use wall · case 05
Account for a redirect chain using a monotonic deadline and separate response timing: the response time does not use wall branch emits an incorrect decision.
Invalidate redirect mappings by source and affected target with partition isolation: source exact match · case 01
Invalidate redirect mappings by source and affected target with partition isolation: the source exact match branch emits an incorrect decision.
Invalidate redirect mappings by source and affected target with partition isolation: source exact match · case 02
Invalidate redirect mappings by source and affected target with partition isolation: the source exact match branch emits an incorrect decision.
Invalidate redirect mappings by source and affected target with partition isolation: source exact match · case 03
Invalidate redirect mappings by source and affected target with partition isolation: the source exact match branch emits an incorrect decision.
Invalidate redirect mappings by source and affected target with partition isolation: source exact match · case 04
Invalidate redirect mappings by source and affected target with partition isolation: the source exact match branch emits an incorrect decision.
Invalidate redirect mappings by source and affected target with partition isolation: source exact match · case 05
Invalidate redirect mappings by source and affected target with partition isolation: the source exact match branch emits an incorrect decision.
Invalidate redirect mappings by source and affected target with partition isolation: source partition conjunction · case 01
Invalidate redirect mappings by source and affected target with partition isolation: the source partition conjunction branch emits an incorrect decision.
Invalidate redirect mappings by source and affected target with partition isolation: source partition conjunction · case 02
Invalidate redirect mappings by source and affected target with partition isolation: the source partition conjunction branch emits an incorrect decision.
Invalidate redirect mappings by source and affected target with partition isolation: source partition conjunction · case 03
Invalidate redirect mappings by source and affected target with partition isolation: the source partition conjunction branch emits an incorrect decision.
Invalidate redirect mappings by source and affected target with partition isolation: source partition conjunction · case 04
Invalidate redirect mappings by source and affected target with partition isolation: the source partition conjunction branch emits an incorrect decision.
Invalidate redirect mappings by source and affected target with partition isolation: source partition conjunction · case 05
Invalidate redirect mappings by source and affected target with partition isolation: the source partition conjunction branch emits an incorrect decision.
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 ↗