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
Per-defendant removal deadlines with a one-year diversity bar: barred test · case 01
A defendant served eleven months in is reported as barred although removal is still possible until the anniversary.
Per-defendant removal deadlines with a one-year diversity bar: barred test · case 02
A defendant served eleven months in is reported as barred although removal is still possible until the anniversary.
Per-defendant removal deadlines with a one-year diversity bar: barred test · case 03
A defendant served eleven months in is reported as barred although removal is still possible until the anniversary.
Per-defendant removal deadlines with a one-year diversity bar: barred test · case 04
A defendant served eleven months in is reported as barred although removal is still possible until the anniversary.
Per-defendant removal deadlines with a one-year diversity bar: barred test · case 05
A defendant served eleven months in is reported as barred although removal is still possible until the anniversary.
Dependent briefing deadlines computed from a rolled predecessor: opp roll · case 01
An opposition deadline falling on Saturday is reported as Saturday and the reply is computed from it.
Dependent briefing deadlines computed from a rolled predecessor: opp roll · case 02
An opposition deadline falling on Saturday is reported as Saturday and the reply is computed from it.
Dependent briefing deadlines computed from a rolled predecessor: opp roll · case 03
An opposition deadline falling on Saturday is reported as Saturday and the reply is computed from it.
Dependent briefing deadlines computed from a rolled predecessor: opp roll · case 04
An opposition deadline falling on Saturday is reported as Saturday and the reply is computed from it.
Dependent briefing deadlines computed from a rolled predecessor: opp roll · case 05
An opposition deadline falling on Saturday is reported as Saturday and the reply is computed from it.
Dependent briefing deadlines computed from a rolled predecessor: reply base · case 01
A late-served opposition pushes the reply deadline back.
Dependent briefing deadlines computed from a rolled predecessor: reply base · case 02
A late-served opposition pushes the reply deadline back.
Dependent briefing deadlines computed from a rolled predecessor: reply base · case 03
A late-served opposition pushes the reply deadline back.
Dependent briefing deadlines computed from a rolled predecessor: reply base · case 04
A late-served opposition pushes the reply deadline back.
Dependent briefing deadlines computed from a rolled predecessor: reply base · case 05
A late-served opposition pushes the reply deadline back.
Dependent briefing deadlines computed from a rolled predecessor: hearing gap · case 01
A hearing exactly seven days after the reply due date is flagged as non-compliant.
Dependent briefing deadlines computed from a rolled predecessor: hearing gap · case 02
A hearing exactly seven days after the reply due date is flagged as non-compliant.
Dependent briefing deadlines computed from a rolled predecessor: hearing gap · case 03
A hearing exactly seven days after the reply due date is flagged as non-compliant.
Dependent briefing deadlines computed from a rolled predecessor: hearing gap · case 04
A hearing exactly seven days after the reply due date is flagged as non-compliant.
Dependent briefing deadlines computed from a rolled predecessor: hearing gap · case 05
A hearing exactly seven days after the reply due date is flagged as non-compliant.
Extending a last day when the clerk office is inaccessible: closure merge · case 01
A later partial-closure entry overwrites an earlier full-day outage for the same day.
Extending a last day when the clerk office is inaccessible: closure merge · case 02
A later partial-closure entry overwrites an earlier full-day outage for the same day.
Extending a last day when the clerk office is inaccessible: closure merge · case 03
A later partial-closure entry overwrites an earlier full-day outage for the same day.
Extending a last day when the clerk office is inaccessible: closure merge · case 04
A later partial-closure entry overwrites an earlier full-day outage for the same day.
Extending a last day when the clerk office is inaccessible: closure merge · case 05
A later partial-closure entry overwrites an earlier full-day outage for the same day.
Extending a last day when the clerk office is inaccessible: partial scope · case 01
An afternoon clerk office closure extends an electronic filing deadline.
Extending a last day when the clerk office is inaccessible: partial scope · case 02
An afternoon clerk office closure extends an electronic filing deadline.
Extending a last day when the clerk office is inaccessible: partial scope · case 03
An afternoon clerk office closure extends an electronic filing deadline.
Extending a last day when the clerk office is inaccessible: partial scope · case 04
An afternoon clerk office closure extends an electronic filing deadline.
Extending a last day when the clerk office is inaccessible: partial scope · case 05
An afternoon clerk office closure extends an electronic filing deadline.
Extending a last day when the clerk office is inaccessible: close boundary · case 01
A closure recorded at the normal closing time is treated as making the day inaccessible.
Extending a last day when the clerk office is inaccessible: close boundary · case 02
A closure recorded at the normal closing time is treated as making the day inaccessible.
Extending a last day when the clerk office is inaccessible: close boundary · case 03
A closure recorded at the normal closing time is treated as making the day inaccessible.
Extending a last day when the clerk office is inaccessible: close boundary · case 04
A closure recorded at the normal closing time is treated as making the day inaccessible.
Extending a last day when the clerk office is inaccessible: close boundary · case 05
A closure recorded at the normal closing time is treated as making the day inaccessible.
Extending a last day when the clerk office is inaccessible: next accessible · case 01
When the office stays closed a second day, the deadline lands on that inaccessible day.
Extending a last day when the clerk office is inaccessible: next accessible · case 02
When the office stays closed a second day, the deadline lands on that inaccessible day.
Extending a last day when the clerk office is inaccessible: next accessible · case 03
When the office stays closed a second day, the deadline lands on that inaccessible day.
Extending a last day when the clerk office is inaccessible: next accessible · case 04
When the office stays closed a second day, the deadline lands on that inaccessible day.
Extending a last day when the clerk office is inaccessible: next accessible · case 05
When the office stays closed a second day, the deadline lands on that inaccessible day.
SRT timestamp parsing: fraction padding · case 01
A cue written as 00:00:01,5 starts at 1.005 s instead of 1.5 s.
SRT timestamp parsing: fraction padding · case 02
A cue written as 00:00:01,5 starts at 1.005 s instead of 1.5 s.
SRT timestamp parsing: fraction padding · case 03
A cue written as 00:00:01,5 starts at 1.005 s instead of 1.5 s.
SRT timestamp parsing: fraction padding · case 04
A cue written as 00:00:01,5 starts at 1.005 s instead of 1.5 s.
SRT timestamp parsing: fraction padding · case 05
A cue written as 00:00:01,5 starts at 1.005 s instead of 1.5 s.
SRT timestamp parsing: dot separator acceptance · case 01
Timestamps exported with a period before the milliseconds are rejected as invalid.
SRT timestamp parsing: dot separator acceptance · case 02
Timestamps exported with a period before the milliseconds are rejected as invalid.
SRT timestamp parsing: dot separator acceptance · case 03
Timestamps exported with a period before the milliseconds are rejected as invalid.
SRT timestamp parsing: dot separator acceptance · case 04
Timestamps exported with a period before the milliseconds are rejected as invalid.
SRT timestamp parsing: dot separator acceptance · case 05
Timestamps exported with a period before the milliseconds are rejected as invalid.
SRT timestamp parsing: minute and second range · case 01
A malformed timestamp such as 00:60:00,000 is accepted and silently becomes one hour.
SRT timestamp parsing: minute and second range · case 02
A malformed timestamp such as 00:60:00,000 is accepted and silently becomes one hour.
SRT timestamp parsing: minute and second range · case 03
A malformed timestamp such as 00:60:00,000 is accepted and silently becomes one hour.
SRT timestamp parsing: minute and second range · case 04
A malformed timestamp such as 00:60:00,000 is accepted and silently becomes one hour.
SRT timestamp parsing: minute and second range · case 05
A malformed timestamp such as 00:60:00,000 is accepted and silently becomes one hour.
SRT timestamp parsing: fraction digit limit · case 01
Valid short fractions such as ,5 are rejected while the file loads with missing cues.
SRT timestamp parsing: fraction digit limit · case 02
Valid short fractions such as ,5 are rejected while the file loads with missing cues.
SRT timestamp parsing: fraction digit limit · case 03
Valid short fractions such as ,5 are rejected while the file loads with missing cues.
SRT timestamp parsing: fraction digit limit · case 04
Valid short fractions such as ,5 are rejected while the file loads with missing cues.
SRT timestamp parsing: fraction digit limit · case 05
Valid short fractions such as ,5 are rejected while the file loads with missing cues.
SRT timestamp parsing: surrounding whitespace · case 01
Every cue from a CRLF subtitle file fails to parse because its end timestamp carries a carriage return.
SRT timestamp parsing: surrounding whitespace · case 02
Every cue from a CRLF subtitle file fails to parse because its end timestamp carries a carriage return.
SRT timestamp parsing: surrounding whitespace · case 03
Every cue from a CRLF subtitle file fails to parse because its end timestamp carries a carriage return.
SRT timestamp parsing: surrounding whitespace · case 04
Every cue from a CRLF subtitle file fails to parse because its end timestamp carries a carriage return.
SRT timestamp parsing: surrounding whitespace · case 05
Every cue from a CRLF subtitle file fails to parse because its end timestamp carries a carriage return.
SRT and WebVTT timestamp formatting: negative clamp · case 01
A cue shifted slightly before zero is written at a positive time mirrored around the origin.
SRT and WebVTT timestamp formatting: negative clamp · case 02
A cue shifted slightly before zero is written at a positive time mirrored around the origin.
SRT and WebVTT timestamp formatting: negative clamp · case 03
A cue shifted slightly before zero is written at a positive time mirrored around the origin.
SRT and WebVTT timestamp formatting: negative clamp · case 04
A cue shifted slightly before zero is written at a positive time mirrored around the origin.
SRT and WebVTT timestamp formatting: negative clamp · case 05
A cue shifted slightly before zero is written at a positive time mirrored around the origin.
SRT and WebVTT timestamp formatting: minute field extraction · case 01
Timestamps past the first hour print minute fields such as 61 or 125.
SRT and WebVTT timestamp formatting: minute field extraction · case 02
Timestamps past the first hour print minute fields such as 61 or 125.
SRT and WebVTT timestamp formatting: minute field extraction · case 03
Timestamps past the first hour print minute fields such as 61 or 125.
SRT and WebVTT timestamp formatting: minute field extraction · case 04
Timestamps past the first hour print minute fields such as 61 or 125.
SRT and WebVTT timestamp formatting: minute field extraction · case 05
Timestamps past the first hour print minute fields such as 61 or 125.
SRT and WebVTT timestamp formatting: srt millisecond padding · case 01
An SRT cue at 1.050 s is written as 00:00:01,50, which readers interpret as 500 ms.
SRT and WebVTT timestamp formatting: srt millisecond padding · case 02
An SRT cue at 1.050 s is written as 00:00:01,50, which readers interpret as 500 ms.
SRT and WebVTT timestamp formatting: srt millisecond padding · case 03
An SRT cue at 1.050 s is written as 00:00:01,50, which readers interpret as 500 ms.
SRT and WebVTT timestamp formatting: srt millisecond padding · case 04
An SRT cue at 1.050 s is written as 00:00:01,50, which readers interpret as 500 ms.
SRT and WebVTT timestamp formatting: srt millisecond padding · case 05
An SRT cue at 1.050 s is written as 00:00:01,50, which readers interpret as 500 ms.
SRT and WebVTT timestamp formatting: vtt hour omission · case 01
WebVTT cues between one and sixty minutes are written with a redundant 00: hour prefix.
SRT and WebVTT timestamp formatting: vtt hour omission · case 02
WebVTT cues between one and sixty minutes are written with a redundant 00: hour prefix.
SRT and WebVTT timestamp formatting: vtt hour omission · case 03
WebVTT cues between one and sixty minutes are written with a redundant 00: hour prefix.
SRT and WebVTT timestamp formatting: vtt hour omission · case 04
WebVTT cues between one and sixty minutes are written with a redundant 00: hour prefix.
SRT and WebVTT timestamp formatting: vtt hour omission · case 05
WebVTT cues between one and sixty minutes are written with a redundant 00: hour prefix.
SRT and WebVTT timestamp formatting: vtt short separator · case 01
Short WebVTT timestamps contain a comma and are rejected by players.
SRT and WebVTT timestamp formatting: vtt short separator · case 02
Short WebVTT timestamps contain a comma and are rejected by players.
SRT and WebVTT timestamp formatting: vtt short separator · case 03
Short WebVTT timestamps contain a comma and are rejected by players.
SRT and WebVTT timestamp formatting: vtt short separator · case 04
Short WebVTT timestamps contain a comma and are rejected by players.
SRT and WebVTT timestamp formatting: vtt short separator · case 05
Short WebVTT timestamps contain a comma and are rejected by players.
Partial subtitle resync from a point: resync scope boundary · case 01
The cue that begins exactly at the chosen resync point keeps its old timing while all later cues move.
Partial subtitle resync from a point: resync scope boundary · case 02
The cue that begins exactly at the chosen resync point keeps its old timing while all later cues move.
Partial subtitle resync from a point: resync scope boundary · case 03
The cue that begins exactly at the chosen resync point keeps its old timing while all later cues move.
Partial subtitle resync from a point: resync scope boundary · case 04
The cue that begins exactly at the chosen resync point keeps its old timing while all later cues move.
Partial subtitle resync from a point: resync scope boundary · case 05
The cue that begins exactly at the chosen resync point keeps its old timing while all later cues move.
Partial subtitle resync from a point: dropped cue test · case 01
A cue that ends exactly at time zero after shifting survives as a zero-length cue.
Partial subtitle resync from a point: dropped cue test · case 02
A cue that ends exactly at time zero after shifting survives as a zero-length cue.
Partial subtitle resync from a point: dropped cue test · case 03
A cue that ends exactly at time zero after shifting survives as a zero-length cue.
Partial subtitle resync from a point: dropped cue test · case 04
A cue that ends exactly at time zero after shifting survives as a zero-length cue.
Partial subtitle resync from a point: dropped cue test · case 05
A cue that ends exactly at time zero after shifting survives as a zero-length cue.
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 ↗