Fix a bug

Something behaves differently than it should. Forge calls this a Bug, and it treats the cause you suspect as one hypothesis among several rather than as a finding.

Ask for itCopy Anchor Link

Forge fix this: uploading a second file while the first is still
going cancels the first one. Happens in Chrome, not in Safari.
Repro: drag two files in quickly on /files.

Give it the symptom, the environment and a way in. Do not give it the fix you have in mind unless you want it treated as the answer.

What it does before it edits anythingCopy Anchor Link

1. Reproduces through the lowest realistic seam it can reach.
2. Writes down observations separately from hypotheses, so a guess is not promoted by sitting next to a fact.
3. Ranks the falsifiable explanations by fit and cost, then runs the cheapest observation that tells them apart.
4. Fixes the shared cause and inspects the siblings that share it.
5. Keeps your original reproduction as the acceptance proof.

If it cannot establish the behavior, the environment or the access it needs, it tells you exactly what is missing instead of guessing.

What comes backCopy Anchor Link

Expected:  the first upload continues
Actual:    the first upload aborts at ~40%
Cause:     both uploads share one AbortController on the store
Repair:    one controller per upload, keyed by file id
Proof:     original repro passes; 3 sibling callers checked

A repair that changes what the software is supposed to do is not a repair, so if your bug turns out to contradict accepted behavior, that comes back to you as a decision rather than being resolved quietly.

HotfixesCopy Anchor Link

Urgency changes the sequencing and the depth. It does not change who is accountable and it does not change what is true, so it cannot waive independent review, the original-reproduction check, or honest proof limits.

Forge fix this as a hotfix, stop at Build, I will ship it myself.