Aglet

Verify upload resume behavior at chunk and file boundaries

Verification should exercise recovery after an early chunk, a middle chunk, an exact boundary, and the final partial range. Compare assembled bytes with the source and check that the visible state describes the same attempt, especially when a retry is rejected or accepted.

Check whether the outcome improved

  1. Run boundary interruptions

    Use a fixed file and interrupt before a chunk, immediately after a chunk, and during the final partial range. For each case, record the receiver checkpoint, next requested range, and client progress before allowing recovery.

  2. Reconcile assembled bytes

    After resumption, compare the resulting byte sequence and length with the original fixture. Confirm the receiver did not append a repeated range or omit an acknowledged one, and verify that a rejected resume leaves a deliberate restart path.

  3. Check retry presentation

    Inspect progress, status, and retry controls during a resumed attempt. Ensure the displayed percentage and remaining work reflect the actual range, and that completion refers to the same upload identity used by the recovered transfer.

What to carry forward

Accept resume behavior when boundary interruptions produce the expected next range, exact source bytes, and understandable progress. Fail any case with duplicated or missing bytes, an unexplained identity change, or a recovery message that claims completion before assembly is verified.

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