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
A zero-copy range sender accounts for partial progress reported with syscall errors: kernel reports beyond the promised range abort before state advances · case 01
A zero-copy range sender accounts for partial progress reported with syscall errors: kernel reports beyond the promised range abort before state advances.
A zero-copy range sender accounts for partial progress reported with syscall errors: kernel reports beyond the promised range abort before state advances · case 02
A zero-copy range sender accounts for partial progress reported with syscall errors: kernel reports beyond the promised range abort before state advances.
A zero-copy range sender accounts for partial progress reported with syscall errors: kernel reports beyond the promised range abort before state advances · case 03
A zero-copy range sender accounts for partial progress reported with syscall errors: kernel reports beyond the promised range abort before state advances.
A zero-copy range sender accounts for partial progress reported with syscall errors: kernel reports beyond the promised range abort before state advances · case 04
A zero-copy range sender accounts for partial progress reported with syscall errors: kernel reports beyond the promised range abort before state advances.
A zero-copy range sender accounts for partial progress reported with syscall errors: kernel reports beyond the promised range abort before state advances · case 05
A zero-copy range sender accounts for partial progress reported with syscall errors: kernel reports beyond the promised range abort before state advances.
A zero-copy range sender accounts for partial progress reported with syscall errors: successful byte progress survives an interrupted syscall status · case 01
A zero-copy range sender accounts for partial progress reported with syscall errors: successful byte progress survives an interrupted syscall status.
A zero-copy range sender accounts for partial progress reported with syscall errors: successful byte progress survives an interrupted syscall status · case 02
A zero-copy range sender accounts for partial progress reported with syscall errors: successful byte progress survives an interrupted syscall status.
A zero-copy range sender accounts for partial progress reported with syscall errors: successful byte progress survives an interrupted syscall status · case 03
A zero-copy range sender accounts for partial progress reported with syscall errors: successful byte progress survives an interrupted syscall status.
A zero-copy range sender accounts for partial progress reported with syscall errors: successful byte progress survives an interrupted syscall status · case 04
A zero-copy range sender accounts for partial progress reported with syscall errors: successful byte progress survives an interrupted syscall status.
A zero-copy range sender accounts for partial progress reported with syscall errors: successful byte progress survives an interrupted syscall status · case 05
A zero-copy range sender accounts for partial progress reported with syscall errors: successful byte progress survives an interrupted syscall status.
A zero-copy range sender accounts for partial progress reported with syscall errors: would-block may accompany successfully transmitted range bytes · case 01
A zero-copy range sender accounts for partial progress reported with syscall errors: would-block may accompany successfully transmitted range bytes.
A zero-copy range sender accounts for partial progress reported with syscall errors: would-block may accompany successfully transmitted range bytes · case 02
A zero-copy range sender accounts for partial progress reported with syscall errors: would-block may accompany successfully transmitted range bytes.
A zero-copy range sender accounts for partial progress reported with syscall errors: would-block may accompany successfully transmitted range bytes · case 03
A zero-copy range sender accounts for partial progress reported with syscall errors: would-block may accompany successfully transmitted range bytes.
A zero-copy range sender accounts for partial progress reported with syscall errors: would-block may accompany successfully transmitted range bytes · case 04
A zero-copy range sender accounts for partial progress reported with syscall errors: would-block may accompany successfully transmitted range bytes.
A zero-copy range sender accounts for partial progress reported with syscall errors: would-block may accompany successfully transmitted range bytes · case 05
A zero-copy range sender accounts for partial progress reported with syscall errors: would-block may accompany successfully transmitted range bytes.
A zero-copy range sender accounts for partial progress reported with syscall errors: fatal errors remain terminal even after their last accepted bytes · case 01
A zero-copy range sender accounts for partial progress reported with syscall errors: fatal errors remain terminal even after their last accepted bytes.
A zero-copy range sender accounts for partial progress reported with syscall errors: fatal errors remain terminal even after their last accepted bytes · case 02
A zero-copy range sender accounts for partial progress reported with syscall errors: fatal errors remain terminal even after their last accepted bytes.
A zero-copy range sender accounts for partial progress reported with syscall errors: fatal errors remain terminal even after their last accepted bytes · case 03
A zero-copy range sender accounts for partial progress reported with syscall errors: fatal errors remain terminal even after their last accepted bytes.
A zero-copy range sender accounts for partial progress reported with syscall errors: fatal errors remain terminal even after their last accepted bytes · case 04
A zero-copy range sender accounts for partial progress reported with syscall errors: fatal errors remain terminal even after their last accepted bytes.
A zero-copy range sender accounts for partial progress reported with syscall errors: fatal errors remain terminal even after their last accepted bytes · case 05
A zero-copy range sender accounts for partial progress reported with syscall errors: fatal errors remain terminal even after their last accepted bytes.
A zero-copy range sender accounts for partial progress reported with syscall errors: all promised bytes complete even if the same syscall reports would-block · case 01
A zero-copy range sender accounts for partial progress reported with syscall errors: all promised bytes complete even if the same syscall reports would-block.
A zero-copy range sender accounts for partial progress reported with syscall errors: all promised bytes complete even if the same syscall reports would-block · case 02
A zero-copy range sender accounts for partial progress reported with syscall errors: all promised bytes complete even if the same syscall reports would-block.
A zero-copy range sender accounts for partial progress reported with syscall errors: all promised bytes complete even if the same syscall reports would-block · case 03
A zero-copy range sender accounts for partial progress reported with syscall errors: all promised bytes complete even if the same syscall reports would-block.
A zero-copy range sender accounts for partial progress reported with syscall errors: all promised bytes complete even if the same syscall reports would-block · case 04
A zero-copy range sender accounts for partial progress reported with syscall errors: all promised bytes complete even if the same syscall reports would-block.
A zero-copy range sender accounts for partial progress reported with syscall errors: all promised bytes complete even if the same syscall reports would-block · case 05
A zero-copy range sender accounts for partial progress reported with syscall errors: all promised bytes complete even if the same syscall reports would-block.
A zero-copy range sender accounts for partial progress reported with syscall errors: an interrupted zero-byte syscall is rescheduled without declaring EOF · case 01
A zero-copy range sender accounts for partial progress reported with syscall errors: an interrupted zero-byte syscall is rescheduled without declaring EOF.
A zero-copy range sender accounts for partial progress reported with syscall errors: an interrupted zero-byte syscall is rescheduled without declaring EOF · case 02
A zero-copy range sender accounts for partial progress reported with syscall errors: an interrupted zero-byte syscall is rescheduled without declaring EOF.
A zero-copy range sender accounts for partial progress reported with syscall errors: an interrupted zero-byte syscall is rescheduled without declaring EOF · case 03
A zero-copy range sender accounts for partial progress reported with syscall errors: an interrupted zero-byte syscall is rescheduled without declaring EOF.
A zero-copy range sender accounts for partial progress reported with syscall errors: an interrupted zero-byte syscall is rescheduled without declaring EOF · case 04
A zero-copy range sender accounts for partial progress reported with syscall errors: an interrupted zero-byte syscall is rescheduled without declaring EOF.
A zero-copy range sender accounts for partial progress reported with syscall errors: an interrupted zero-byte syscall is rescheduled without declaring EOF · case 05
A zero-copy range sender accounts for partial progress reported with syscall errors: an interrupted zero-byte syscall is rescheduled without declaring EOF.
A zero-copy range sender accounts for partial progress reported with syscall errors: a clean zero-byte return with remaining bytes is truncation · case 01
A zero-copy range sender accounts for partial progress reported with syscall errors: a clean zero-byte return with remaining bytes is truncation.
A zero-copy range sender accounts for partial progress reported with syscall errors: a clean zero-byte return with remaining bytes is truncation · case 02
A zero-copy range sender accounts for partial progress reported with syscall errors: a clean zero-byte return with remaining bytes is truncation.
A zero-copy range sender accounts for partial progress reported with syscall errors: a clean zero-byte return with remaining bytes is truncation · case 03
A zero-copy range sender accounts for partial progress reported with syscall errors: a clean zero-byte return with remaining bytes is truncation.
A zero-copy range sender accounts for partial progress reported with syscall errors: a clean zero-byte return with remaining bytes is truncation · case 04
A zero-copy range sender accounts for partial progress reported with syscall errors: a clean zero-byte return with remaining bytes is truncation.
A zero-copy range sender accounts for partial progress reported with syscall errors: a clean zero-byte return with remaining bytes is truncation · case 05
A zero-copy range sender accounts for partial progress reported with syscall errors: a clean zero-byte return with remaining bytes is truncation.
A zero-copy range sender accounts for partial progress reported with syscall errors: aborted and truncated range streams release the source handle · case 01
A zero-copy range sender accounts for partial progress reported with syscall errors: aborted and truncated range streams release the source handle.
A zero-copy range sender accounts for partial progress reported with syscall errors: aborted and truncated range streams release the source handle · case 02
A zero-copy range sender accounts for partial progress reported with syscall errors: aborted and truncated range streams release the source handle.
A zero-copy range sender accounts for partial progress reported with syscall errors: aborted and truncated range streams release the source handle · case 03
A zero-copy range sender accounts for partial progress reported with syscall errors: aborted and truncated range streams release the source handle.
A zero-copy range sender accounts for partial progress reported with syscall errors: aborted and truncated range streams release the source handle · case 04
A zero-copy range sender accounts for partial progress reported with syscall errors: aborted and truncated range streams release the source handle.
A zero-copy range sender accounts for partial progress reported with syscall errors: aborted and truncated range streams release the source handle · case 05
A zero-copy range sender accounts for partial progress reported with syscall errors: aborted and truncated range streams release the source handle.
A range-set guard limits amplification before serving resolved byte ranges: an empty resolved range list never becomes an empty partial response · case 01
A range-set guard limits amplification before serving resolved byte ranges: an empty resolved range list never becomes an empty partial response.
A range-set guard limits amplification before serving resolved byte ranges: an empty resolved range list never becomes an empty partial response · case 02
A range-set guard limits amplification before serving resolved byte ranges: an empty resolved range list never becomes an empty partial response.
A range-set guard limits amplification before serving resolved byte ranges: an empty resolved range list never becomes an empty partial response · case 03
A range-set guard limits amplification before serving resolved byte ranges: an empty resolved range list never becomes an empty partial response.
A range-set guard limits amplification before serving resolved byte ranges: an empty resolved range list never becomes an empty partial response · case 04
A range-set guard limits amplification before serving resolved byte ranges: an empty resolved range list never becomes an empty partial response.
A range-set guard limits amplification before serving resolved byte ranges: an empty resolved range list never becomes an empty partial response · case 05
A range-set guard limits amplification before serving resolved byte ranges: an empty resolved range list never becomes an empty partial response.
A range-set guard limits amplification before serving resolved byte ranges: repeated identical ranges each count toward the amplification budget · case 01
A range-set guard limits amplification before serving resolved byte ranges: repeated identical ranges each count toward the amplification budget.
A range-set guard limits amplification before serving resolved byte ranges: repeated identical ranges each count toward the amplification budget · case 02
A range-set guard limits amplification before serving resolved byte ranges: repeated identical ranges each count toward the amplification budget.
A range-set guard limits amplification before serving resolved byte ranges: repeated identical ranges each count toward the amplification budget · case 03
A range-set guard limits amplification before serving resolved byte ranges: repeated identical ranges each count toward the amplification budget.
A range-set guard limits amplification before serving resolved byte ranges: repeated identical ranges each count toward the amplification budget · case 04
A range-set guard limits amplification before serving resolved byte ranges: repeated identical ranges each count toward the amplification budget.
A range-set guard limits amplification before serving resolved byte ranges: repeated identical ranges each count toward the amplification budget · case 05
A range-set guard limits amplification before serving resolved byte ranges: repeated identical ranges each count toward the amplification budget.
A range-set guard limits amplification before serving resolved byte ranges: overlap detection sweeps ranges in start order rather than request order · case 01
A range-set guard limits amplification before serving resolved byte ranges: overlap detection sweeps ranges in start order rather than request order.
A range-set guard limits amplification before serving resolved byte ranges: overlap detection sweeps ranges in start order rather than request order · case 02
A range-set guard limits amplification before serving resolved byte ranges: overlap detection sweeps ranges in start order rather than request order.
A range-set guard limits amplification before serving resolved byte ranges: overlap detection sweeps ranges in start order rather than request order · case 03
A range-set guard limits amplification before serving resolved byte ranges: overlap detection sweeps ranges in start order rather than request order.
A range-set guard limits amplification before serving resolved byte ranges: overlap detection sweeps ranges in start order rather than request order · case 04
A range-set guard limits amplification before serving resolved byte ranges: overlap detection sweeps ranges in start order rather than request order.
A range-set guard limits amplification before serving resolved byte ranges: overlap detection sweeps ranges in start order rather than request order · case 05
A range-set guard limits amplification before serving resolved byte ranges: overlap detection sweeps ranges in start order rather than request order.
A range-set guard limits amplification before serving resolved byte ranges: touching ranges are not counted as overlapping while a shared byte is · case 01
A range-set guard limits amplification before serving resolved byte ranges: touching ranges are not counted as overlapping while a shared byte is.
A range-set guard limits amplification before serving resolved byte ranges: touching ranges are not counted as overlapping while a shared byte is · case 02
A range-set guard limits amplification before serving resolved byte ranges: touching ranges are not counted as overlapping while a shared byte is.
A range-set guard limits amplification before serving resolved byte ranges: touching ranges are not counted as overlapping while a shared byte is · case 03
A range-set guard limits amplification before serving resolved byte ranges: touching ranges are not counted as overlapping while a shared byte is.
A range-set guard limits amplification before serving resolved byte ranges: touching ranges are not counted as overlapping while a shared byte is · case 04
A range-set guard limits amplification before serving resolved byte ranges: touching ranges are not counted as overlapping while a shared byte is.
A range-set guard limits amplification before serving resolved byte ranges: touching ranges are not counted as overlapping while a shared byte is · case 05
A range-set guard limits amplification before serving resolved byte ranges: touching ranges are not counted as overlapping while a shared byte is.
A range-set guard limits amplification before serving resolved byte ranges: coalescing joins ranges that touch without a byte gap · case 01
A range-set guard limits amplification before serving resolved byte ranges: coalescing joins ranges that touch without a byte gap.
A range-set guard limits amplification before serving resolved byte ranges: coalescing joins ranges that touch without a byte gap · case 02
A range-set guard limits amplification before serving resolved byte ranges: coalescing joins ranges that touch without a byte gap.
A range-set guard limits amplification before serving resolved byte ranges: coalescing joins ranges that touch without a byte gap · case 03
A range-set guard limits amplification before serving resolved byte ranges: coalescing joins ranges that touch without a byte gap.
A range-set guard limits amplification before serving resolved byte ranges: coalescing joins ranges that touch without a byte gap · case 04
A range-set guard limits amplification before serving resolved byte ranges: coalescing joins ranges that touch without a byte gap.
A range-set guard limits amplification before serving resolved byte ranges: coalescing joins ranges that touch without a byte gap · case 05
A range-set guard limits amplification before serving resolved byte ranges: coalescing joins ranges that touch without a byte gap.
A range-set guard limits amplification before serving resolved byte ranges: a contained range cannot shrink the coalesced end · case 01
A range-set guard limits amplification before serving resolved byte ranges: a contained range cannot shrink the coalesced end.
A range-set guard limits amplification before serving resolved byte ranges: a contained range cannot shrink the coalesced end · case 02
A range-set guard limits amplification before serving resolved byte ranges: a contained range cannot shrink the coalesced end.
A range-set guard limits amplification before serving resolved byte ranges: a contained range cannot shrink the coalesced end · case 03
A range-set guard limits amplification before serving resolved byte ranges: a contained range cannot shrink the coalesced end.
A range-set guard limits amplification before serving resolved byte ranges: a contained range cannot shrink the coalesced end · case 04
A range-set guard limits amplification before serving resolved byte ranges: a contained range cannot shrink the coalesced end.
A range-set guard limits amplification before serving resolved byte ranges: a contained range cannot shrink the coalesced end · case 05
A range-set guard limits amplification before serving resolved byte ranges: a contained range cannot shrink the coalesced end.
A range-set guard limits amplification before serving resolved byte ranges: inversions compare each member with its immediate request predecessor · case 01
A range-set guard limits amplification before serving resolved byte ranges: inversions compare each member with its immediate request predecessor.
A range-set guard limits amplification before serving resolved byte ranges: inversions compare each member with its immediate request predecessor · case 02
A range-set guard limits amplification before serving resolved byte ranges: inversions compare each member with its immediate request predecessor.
A range-set guard limits amplification before serving resolved byte ranges: inversions compare each member with its immediate request predecessor · case 03
A range-set guard limits amplification before serving resolved byte ranges: inversions compare each member with its immediate request predecessor.
A range-set guard limits amplification before serving resolved byte ranges: inversions compare each member with its immediate request predecessor · case 04
A range-set guard limits amplification before serving resolved byte ranges: inversions compare each member with its immediate request predecessor.
A range-set guard limits amplification before serving resolved byte ranges: inversions compare each member with its immediate request predecessor · case 05
A range-set guard limits amplification before serving resolved byte ranges: inversions compare each member with its immediate request predecessor.
A range-set guard limits amplification before serving resolved byte ranges: any tolerated overlap still forces coalesced output · case 01
A range-set guard limits amplification before serving resolved byte ranges: any tolerated overlap still forces coalesced output.
A range-set guard limits amplification before serving resolved byte ranges: any tolerated overlap still forces coalesced output · case 02
A range-set guard limits amplification before serving resolved byte ranges: any tolerated overlap still forces coalesced output.
A range-set guard limits amplification before serving resolved byte ranges: any tolerated overlap still forces coalesced output · case 03
A range-set guard limits amplification before serving resolved byte ranges: any tolerated overlap still forces coalesced output.
A range-set guard limits amplification before serving resolved byte ranges: any tolerated overlap still forces coalesced output · case 04
A range-set guard limits amplification before serving resolved byte ranges: any tolerated overlap still forces coalesced output.
A range-set guard limits amplification before serving resolved byte ranges: any tolerated overlap still forces coalesced output · case 05
A range-set guard limits amplification before serving resolved byte ranges: any tolerated overlap still forces coalesced output.
A parallel downloader splits a representation into worker ranges and rebalances idle workers: remainder bytes go one each to the leading workers · case 01
A parallel downloader splits a representation into worker ranges and rebalances idle workers: remainder bytes go one each to the leading workers.
A parallel downloader splits a representation into worker ranges and rebalances idle workers: remainder bytes go one each to the leading workers · case 02
A parallel downloader splits a representation into worker ranges and rebalances idle workers: remainder bytes go one each to the leading workers.
A parallel downloader splits a representation into worker ranges and rebalances idle workers: remainder bytes go one each to the leading workers · case 03
A parallel downloader splits a representation into worker ranges and rebalances idle workers: remainder bytes go one each to the leading workers.
A parallel downloader splits a representation into worker ranges and rebalances idle workers: remainder bytes go one each to the leading workers · case 04
A parallel downloader splits a representation into worker ranges and rebalances idle workers: remainder bytes go one each to the leading workers.
A parallel downloader splits a representation into worker ranges and rebalances idle workers: remainder bytes go one each to the leading workers · case 05
A parallel downloader splits a representation into worker ranges and rebalances idle workers: remainder bytes go one each to the leading workers.
A parallel downloader splits a representation into worker ranges and rebalances idle workers: each segment begins after the previous segment actual size · case 01
A parallel downloader splits a representation into worker ranges and rebalances idle workers: each segment begins after the previous segment actual size.
A parallel downloader splits a representation into worker ranges and rebalances idle workers: each segment begins after the previous segment actual size · case 02
A parallel downloader splits a representation into worker ranges and rebalances idle workers: each segment begins after the previous segment actual size.
A parallel downloader splits a representation into worker ranges and rebalances idle workers: each segment begins after the previous segment actual size · case 03
A parallel downloader splits a representation into worker ranges and rebalances idle workers: each segment begins after the previous segment actual size.
A parallel downloader splits a representation into worker ranges and rebalances idle workers: each segment begins after the previous segment actual size · case 04
A parallel downloader splits a representation into worker ranges and rebalances idle workers: each segment begins after the previous segment actual size.
A parallel downloader splits a representation into worker ranges and rebalances idle workers: each segment begins after the previous segment actual size · case 05
A parallel downloader splits a representation into worker ranges and rebalances idle workers: each segment begins after the previous segment actual size.
A parallel downloader splits a representation into worker ranges and rebalances idle workers: accepted bytes cannot advance a worker past its assigned end · case 01
A parallel downloader splits a representation into worker ranges and rebalances idle workers: accepted bytes cannot advance a worker past its assigned end.
A parallel downloader splits a representation into worker ranges and rebalances idle workers: accepted bytes cannot advance a worker past its assigned end · case 02
A parallel downloader splits a representation into worker ranges and rebalances idle workers: accepted bytes cannot advance a worker past its assigned end.
A parallel downloader splits a representation into worker ranges and rebalances idle workers: accepted bytes cannot advance a worker past its assigned end · case 03
A parallel downloader splits a representation into worker ranges and rebalances idle workers: accepted bytes cannot advance a worker past its assigned end.
A parallel downloader splits a representation into worker ranges and rebalances idle workers: accepted bytes cannot advance a worker past its assigned end · case 04
A parallel downloader splits a representation into worker ranges and rebalances idle workers: accepted bytes cannot advance a worker past its assigned end.
A parallel downloader splits a representation into worker ranges and rebalances idle workers: accepted bytes cannot advance a worker past its assigned end · case 05
A parallel downloader splits a representation into worker ranges and rebalances idle workers: accepted bytes cannot advance a worker past its assigned end.
A parallel downloader splits a representation into worker ranges and rebalances idle workers: negative worker indices are rejected rather than addressing the last worker · case 01
A parallel downloader splits a representation into worker ranges and rebalances idle workers: negative worker indices are rejected rather than addressing the last worker.
A parallel downloader splits a representation into worker ranges and rebalances idle workers: negative worker indices are rejected rather than addressing the last worker · case 02
A parallel downloader splits a representation into worker ranges and rebalances idle workers: negative worker indices are rejected rather than addressing the last worker.
A parallel downloader splits a representation into worker ranges and rebalances idle workers: negative worker indices are rejected rather than addressing the last worker · case 03
A parallel downloader splits a representation into worker ranges and rebalances idle workers: negative worker indices are rejected rather than addressing the last worker.
A parallel downloader splits a representation into worker ranges and rebalances idle workers: negative worker indices are rejected rather than addressing the last worker · case 04
A parallel downloader splits a representation into worker ranges and rebalances idle workers: negative worker indices are rejected rather than addressing the last worker.
A parallel downloader splits a representation into worker ranges and rebalances idle workers: negative worker indices are rejected rather than addressing the last worker · case 05
A parallel downloader splits a representation into worker ranges and rebalances idle workers: negative worker indices are rejected rather than addressing the last worker.
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 ↗