Aglet

Investigate upload cancellation races and partial artifacts

Cancellation investigation needs a timeline because the action and the last transfer response can arrive in either order. Use a controlled file and vary the response timing, then compare client transitions with the server's artifact record. The brief should identify the first conflicting transition.

Build a useful investigation brief

  1. Build ordered timing cases

    Prepare cases where cancellation precedes a transfer response, follows it, or coincides with a final chunk. Record the file identity, request sequence, progress, and expected terminal state for each case. Keep the same fixture across timings.

  2. Trace state transitions

    For every case, list client state, server upload state, temporary artifact state, and visible controls after each event. Mark transitions that are legal, repeated, or impossible under the stated cancellation contract.

  3. Explain the surviving artifact

    Compare the final record with the cancellation response and any later status read. Identify whether the artifact is retained by design, left by a race, or detached from the visible file. Separate evidence from hypotheses about cleanup timing.

What to carry forward

The investigation is sufficient when response ordering and final artifact state explain one reproducible cancellation outcome. If cleanup or retention evidence is absent, report the observable mismatch and leave the responsible boundary open rather than assigning an unproven cause.

Technical background: MDN reference.

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