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
Websocket continuation requires an open fragmented message · case 01
Websocket continuation requires an open fragmented message.
Websocket continuation requires an open fragmented message · case 02
Websocket continuation requires an open fragmented message.
Websocket continuation requires an open fragmented message · case 03
Websocket continuation requires an open fragmented message.
Websocket continuation requires an open fragmented message · case 04
Websocket continuation requires an open fragmented message.
Websocket continuation requires an open fragmented message · case 05
Websocket continuation requires an open fragmented message.
Websocket control frames do not close fragmented message state · case 01
Websocket control frames do not close fragmented message state.
Websocket control frames do not close fragmented message state · case 02
Websocket control frames do not close fragmented message state.
Websocket control frames do not close fragmented message state · case 03
Websocket control frames do not close fragmented message state.
Websocket control frames do not close fragmented message state · case 04
Websocket control frames do not close fragmented message state.
Websocket control frames do not close fragmented message state · case 05
Websocket control frames do not close fragmented message state.
Websocket mask index continues across buffer chunks · case 01
Websocket mask index continues across buffer chunks.
Websocket mask index continues across buffer chunks · case 02
Websocket mask index continues across buffer chunks.
Websocket mask index continues across buffer chunks · case 03
Websocket mask index continues across buffer chunks.
Websocket mask index continues across buffer chunks · case 04
Websocket mask index continues across buffer chunks.
Websocket mask index continues across buffer chunks · case 05
Websocket mask index continues across buffer chunks.
Websocket close payload cannot contain a single byte · case 01
Websocket close payload cannot contain a single byte.
Websocket close payload cannot contain a single byte · case 02
Websocket close payload cannot contain a single byte.
Websocket close payload cannot contain a single byte · case 03
Websocket close payload cannot contain a single byte.
Websocket close payload cannot contain a single byte · case 04
Websocket close payload cannot contain a single byte.
Websocket close payload cannot contain a single byte · case 05
Websocket close payload cannot contain a single byte.
Websocket reserved close codes are not transmitted · case 01
Websocket reserved close codes are not transmitted.
Websocket reserved close codes are not transmitted · case 02
Websocket reserved close codes are not transmitted.
Websocket reserved close codes are not transmitted · case 03
Websocket reserved close codes are not transmitted.
Websocket reserved close codes are not transmitted · case 04
Websocket reserved close codes are not transmitted.
Websocket reserved close codes are not transmitted · case 05
Websocket reserved close codes are not transmitted.
Websocket pong echoes the entire ping payload · case 01
Websocket pong echoes the entire ping payload.
Websocket pong echoes the entire ping payload · case 02
Websocket pong echoes the entire ping payload.
Websocket pong echoes the entire ping payload · case 03
Websocket pong echoes the entire ping payload.
Websocket pong echoes the entire ping payload · case 04
Websocket pong echoes the entire ping payload.
Websocket pong echoes the entire ping payload · case 05
Websocket pong echoes the entire ping payload.
Websocket close handshake completes after both close directions · case 01
Websocket close handshake completes after both close directions.
Websocket close handshake completes after both close directions · case 02
Websocket close handshake completes after both close directions.
Websocket close handshake completes after both close directions · case 03
Websocket close handshake completes after both close directions.
Websocket close handshake completes after both close directions · case 04
Websocket close handshake completes after both close directions.
Websocket close handshake completes after both close directions · case 05
Websocket close handshake completes after both close directions.
Websocket application data is disallowed after close starts · case 01
Websocket application data is disallowed after close starts.
Websocket application data is disallowed after close starts · case 02
Websocket application data is disallowed after close starts.
Websocket application data is disallowed after close starts · case 03
Websocket application data is disallowed after close starts.
Websocket application data is disallowed after close starts · case 04
Websocket application data is disallowed after close starts.
Websocket application data is disallowed after close starts · case 05
Websocket application data is disallowed after close starts.
Sse empty id clears the reconnection event identifier · case 01
Sse empty id clears the reconnection event identifier.
Sse empty id clears the reconnection event identifier · case 02
Sse empty id clears the reconnection event identifier.
Sse empty id clears the reconnection event identifier · case 03
Sse empty id clears the reconnection event identifier.
Sse empty id clears the reconnection event identifier · case 04
Sse empty id clears the reconnection event identifier.
Sse empty id clears the reconnection event identifier · case 05
Sse empty id clears the reconnection event identifier.
Sse retry field accepts only nonempty ascii digits · case 01
Sse retry field accepts only nonempty ascii digits.
Sse retry field accepts only nonempty ascii digits · case 02
Sse retry field accepts only nonempty ascii digits.
Sse retry field accepts only nonempty ascii digits · case 03
Sse retry field accepts only nonempty ascii digits.
Sse retry field accepts only nonempty ascii digits · case 04
Sse retry field accepts only nonempty ascii digits.
Sse retry field accepts only nonempty ascii digits · case 05
Sse retry field accepts only nonempty ascii digits.
Sse data lines join with newlines not concatenation · case 01
Sse data lines join with newlines not concatenation.
Sse data lines join with newlines not concatenation · case 02
Sse data lines join with newlines not concatenation.
Sse data lines join with newlines not concatenation · case 03
Sse data lines join with newlines not concatenation.
Sse data lines join with newlines not concatenation · case 04
Sse data lines join with newlines not concatenation.
Sse data lines join with newlines not concatenation · case 05
Sse data lines join with newlines not concatenation.
Sse dispatch requires at least one data field · case 01
Sse dispatch requires at least one data field.
Sse dispatch requires at least one data field · case 02
Sse dispatch requires at least one data field.
Sse dispatch requires at least one data field · case 03
Sse dispatch requires at least one data field.
Sse dispatch requires at least one data field · case 04
Sse dispatch requires at least one data field.
Sse dispatch requires at least one data field · case 05
Sse dispatch requires at least one data field.
Sse comments do not change data buffer · case 01
Sse comments do not change data buffer.
Sse comments do not change data buffer · case 02
Sse comments do not change data buffer.
Sse comments do not change data buffer · case 03
Sse comments do not change data buffer.
Sse comments do not change data buffer · case 04
Sse comments do not change data buffer.
Sse comments do not change data buffer · case 05
Sse comments do not change data buffer.
Cors origin wildcard is incompatible with credentialed response · case 01
Cors origin wildcard is incompatible with credentialed response.
Cors origin wildcard is incompatible with credentialed response · case 02
Cors origin wildcard is incompatible with credentialed response.
Cors origin wildcard is incompatible with credentialed response · case 03
Cors origin wildcard is incompatible with credentialed response.
Cors origin wildcard is incompatible with credentialed response · case 04
Cors origin wildcard is incompatible with credentialed response.
Cors origin wildcard is incompatible with credentialed response · case 05
Cors origin wildcard is incompatible with credentialed response.
Cors preflight method matching is case sensitive · case 01
Cors preflight method matching is case sensitive.
Cors preflight method matching is case sensitive · case 02
Cors preflight method matching is case sensitive.
Cors preflight method matching is case sensitive · case 03
Cors preflight method matching is case sensitive.
Cors preflight method matching is case sensitive · case 04
Cors preflight method matching is case sensitive.
Cors preflight method matching is case sensitive · case 05
Cors preflight method matching is case sensitive.
Cors preflight header names are case insensitive · case 01
Cors preflight header names are case insensitive.
Cors preflight header names are case insensitive · case 02
Cors preflight header names are case insensitive.
Cors preflight header names are case insensitive · case 03
Cors preflight header names are case insensitive.
Cors preflight header names are case insensitive · case 04
Cors preflight header names are case insensitive.
Cors preflight header names are case insensitive · case 05
Cors preflight header names are case insensitive.
Cors origin comparison includes scheme host and port · case 01
Cors origin comparison includes scheme host and port.
Cors origin comparison includes scheme host and port · case 02
Cors origin comparison includes scheme host and port.
Cors origin comparison includes scheme host and port · case 03
Cors origin comparison includes scheme host and port.
Cors origin comparison includes scheme host and port · case 04
Cors origin comparison includes scheme host and port.
Cors origin comparison includes scheme host and port · case 05
Cors origin comparison includes scheme host and port.
Cors preflight cache key includes origin and method · case 01
Cors preflight cache key includes origin and method.
Cors preflight cache key includes origin and method · case 02
Cors preflight cache key includes origin and method.
Cors preflight cache key includes origin and method · case 03
Cors preflight cache key includes origin and method.
Cors preflight cache key includes origin and method · case 04
Cors preflight cache key includes origin and method.
Cors preflight cache key includes origin and method · case 05
Cors preflight cache key includes origin and method.
Cors exposed header wildcard is literal with credentials · case 01
Cors exposed header wildcard is literal with credentials.
Cors exposed header wildcard is literal with credentials · case 02
Cors exposed header wildcard is literal with credentials.
Cors exposed header wildcard is literal with credentials · case 03
Cors exposed header wildcard is literal with credentials.
Cors exposed header wildcard is literal with credentials · case 04
Cors exposed header wildcard is literal with credentials.
Cors exposed header wildcard is literal with credentials · case 05
Cors exposed header wildcard is literal with credentials.
Cors preflight max age is capped by browser policy · case 01
Cors preflight max age is capped by browser policy.
Cors preflight max age is capped by browser policy · case 02
Cors preflight max age is capped by browser policy.
Cors preflight max age is capped by browser policy · case 03
Cors preflight max age is capped by browser policy.
Cors preflight max age is capped by browser policy · case 04
Cors preflight max age is capped by browser policy.
Cors preflight max age is capped by browser policy · case 05
Cors preflight max age is capped by browser policy.
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 ↗