Aglet

Verify chunked uploads across ranges, remainders, and retries

Verification should cover files shorter than one chunk, exact multiples, final remainders, repeated parts, and an interrupted transfer. Confirm each accepted object equals the source byte-for-byte and that rejected metadata creates a deliberate retry path rather than partial or apparently complete delivery.

Check whether the outcome improved

  1. Run shape fixtures

    Test an empty file if supported, a one-byte file, one full chunk, two full chunks, and a remainder. Record expected range and payload lengths before sending, then compare receiver acceptance with those exact values.

  2. Exercise retries and order

    Repeat one chunk, interrupt before the final part, and deliver parts through the supported ordering. Verify duplicates are handled according to the contract, missing parts cannot appear complete, and the final assembly preserves source order.

  3. Compare delivered bytes

    Hash or byte-compare the assembled object with the patterned source and inspect its stored length. Check the user-visible outcome and downstream handoff, ensuring a complete label is withheld until the assembly evidence meets the contract.

What to carry forward

Accept chunking when every shape and retry case yields the expected ranges and source bytes, with safe handling for rejected or missing parts. Fail on any silent gap, overlap, order change, or completion state unsupported by assembly evidence.

Technical background: tus protocol documentation.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow