Repair Resumable Upload Offset Bugs

The problem

Resumable upload implementations often suffer from inconsistent offset tracking, race conditions during concurrent chunk writes, and leaking temporary files. Developers struggle to synchronize session identity, state ownership, and integrity checks across complex storage layers.

What it does

• Identifies and patches authoritative committed offset mismatches across repository components.
• Enforces strict chunk range validation to prevent data corruption during retries.
• Implements deterministic session generation and lease management for concurrent writers.
• Standardizes temporary file cleanup and session expiry logic without weakening security policies.
• Generates regression tests using local byte-range fixtures and loopback endpoints.

Frameworks & tools

Works with repository-level code using Read, Edit, and Bash tools. Applicable to any stack implementing chunked or resumable upload protocols.

Why this beats prompting it yourself

General prompts often miss the subtle race conditions and trust boundaries inherent in multi-part uploads. This skill follows a rigorous method to map state transitions and bind callbacks to the specific generations that created them, ensuring fixes don't just "look right" but handle edge cases like identical chunk retries and terminal failures correctly.

Use cases

• Fixing "offset mismatch" errors in S3-compatible or custom storage backends.
• Resolving data integrity issues caused by out-of-order chunk processing.
• Automating the cleanup of orphaned upload sessions and partial files.
• Adding redacted observability to upload pipelines without logging customer data.

Known limitations

Cannot interact with production services or live cloud environments. It focuses on local repository repairs and deterministic testing fixtures.