You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened?\n\nWhen a partial download exists at the internal .tmp path, downloadFile sends a Range request starting at the existing size. In non-interactive mode it then copies the ranged response without seeking to the end of the already-open file, so the response starts at offset 0 and overwrites the partial bytes instead of appending them.\n\n### Version\n\nmain at d5d0b56\n\n### Relevant log output\n\nA hermetic HTTP-server reproduction is sufficient: seed a partial file, have the server return the remaining bytes for the requested Range, then call the download helper with no progress bar. The result contains the remainder at the beginning rather than the complete payload. Seeking before both copy paths preserves the intended resumed-download behavior.
What happened?\n\nWhen a partial download exists at the internal .tmp path, downloadFile sends a Range request starting at the existing size. In non-interactive mode it then copies the ranged response without seeking to the end of the already-open file, so the response starts at offset 0 and overwrites the partial bytes instead of appending them.\n\n### Version\n\nmain at d5d0b56\n\n### Relevant log output\n\nA hermetic HTTP-server reproduction is sufficient: seed a partial file, have the server return the remaining bytes for the requested Range, then call the download helper with no progress bar. The result contains the remainder at the beginning rather than the complete payload. Seeking before both copy paths preserves the intended resumed-download behavior.