fix(downloads): improved handling for large file downloads and user-initiated cancellation (#632)

* fix(downloads): increase retry attempts and backoff for large file downloads
* fix download retry config and abort handling
* use abort reason to detect user-initiated cancels
This commit is contained in:
0xGlitch 2026-04-02 16:14:23 -06:00 committed by Jake Turner
parent cb4fa003a4
commit d7e3d9246b
2 changed files with 14 additions and 6 deletions

View File

@ -54,6 +54,11 @@ export class RunDownloadJob {
totalBytes: 0,
}
// Track whether cancellation was explicitly requested by the user (via Redis signal
// or in-process AbortController). BullMQ lock mismatches can also abort the download
// stream, but those should be retried — only user-initiated cancels are unrecoverable.
let userCancelled = false
// Poll Redis for cancel signal every 2s — independent of progress events so cancellation
// works even when the stream is stalled and no onProgress ticks are firing.
let cancelPollInterval: ReturnType<typeof setInterval> | null = setInterval(async () => {
@ -61,7 +66,8 @@ export class RunDownloadJob {
const val = await cancelRedis.get(RunDownloadJob.cancelKey(job.id!))
if (val) {
await cancelRedis.del(RunDownloadJob.cancelKey(job.id!))
abortController.abort()
userCancelled = true
abortController.abort('user-cancel')
}
} catch {
// Redis errors are non-fatal; in-process AbortController covers same-process cancels
@ -176,8 +182,10 @@ export class RunDownloadJob {
filepath,
}
} catch (error: any) {
// If this was a cancellation abort, don't let BullMQ retry
if (error?.message?.includes('aborted') || error?.message?.includes('cancelled')) {
// Only prevent retries for user-initiated cancellations. BullMQ lock mismatches
// can also abort the stream, and those should be retried with backoff.
// Check both the flag (Redis poll) and abort reason (in-process cancel).
if (userCancelled || abortController.signal.reason === 'user-cancel') {
throw new UnrecoverableError(`Download cancelled: ${error.message}`)
}
throw error
@ -228,8 +236,8 @@ export class RunDownloadJob {
try {
const job = await queue.add(this.key, params, {
jobId,
attempts: 3,
backoff: { type: 'exponential', delay: 2000 },
attempts: 10,
backoff: { type: 'exponential', delay: 30000 },
removeOnComplete: true,
})

View File

@ -125,7 +125,7 @@ export class DownloadService {
await RunDownloadJob.signalCancel(jobId)
// Also try in-memory abort (works if worker is in same process)
RunDownloadJob.abortControllers.get(jobId)?.abort()
RunDownloadJob.abortControllers.get(jobId)?.abort('user-cancel')
RunDownloadJob.abortControllers.delete(jobId)
// Poll for terminal state (up to 4s at 250ms intervals) — cooperates with BullMQ's lifecycle