* filer: cancel a chunk download that no reader waits for
* filer: stop waiting for reader cache budget once cancelled
* filer: keep a cancelled download's re-lookups off its context
The refresh and retry lookups took the download's context. FilerClient
coalesces concurrent lookups of a volume, so a cancelled download leading
one failed the other readers waiting on it. Fetches still stop on cancel.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* filer: test that cancelling a download leaves its re-lookup running
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* filer: cancel unheld downloads when the reader cache is destroyed
ReaderCache.destroy waited for every downloader, so closing a reader
waited for a stalled prefetch nobody read. Downloads with no reader or
stream on them are now cancelled first; ones still in use keep running.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* filer: test that destroying the reader cache cancels an unread prefetch
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* filer: cancel a destroyed download once its last holder leaves
destroy skipped downloads a reader or stream still held, and once they
were out of the map nothing cancelled them, so destroy waited for a fetch
nobody used. removeConsumedLocked now cancels any consumable download,
whether or not it is still in the map.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* filer: test a destroyed download cancelled after its last stream leaves
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* filer: release the stream only after destroy dropped the download
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* filer: test a cancelled stream leaving a waiting reader's download running
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Chris Lu <chrislusf@users.noreply.github.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>