Keep the lesson for the next incident
Cluster the range failures
Group findings by inclusive endpoints, final remainders, declared size, part order, duplicate retries, and empty or one-chunk files. Record the smallest source fixture that made each failure visible and the downstream state it produced.
Write the byte contract
Document how a chunk's start, end, length, number, identity, and assembly order relate. Include expected records for a full chunk and a short final chunk, plus the rule for repeated or missing parts.
Make boundary tests habitual
Require the patterned fixture when changing chunk size, range formatting, retry handling, persistence, or completion checks. Name the owner for the contract and record which evidence proves an assembled object is ready for processing.
What to carry forward
The learning record is complete when range arithmetic and assembly order are explicit, boundary fixtures are preserved, and completion depends on source-byte evidence. If a protocol intentionally accepts a different convention, document that convention at the receiver boundary and keep the fixture aligned.
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