Clipper, Desktop: Prevent race condition when download limit is reached #10124
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The change here is to check if the
request.destroy()
method has already been called before resolving thefetchBlob
function.This change is necessary to address a potential race condition.
When the
LimitedDownloadController
callsrequest.destroy()
, it triggers the asynchronouscleanUpOnError
function which unlinks the downloaded file and reject. But if before the function is rejected thefile.on('finish', ...)
is executed the function might appear to resolve successfully, returning apath
property to a file that has beenunlinked
by thecleanUpOnError
function.By checking if
request.destroyed
is true, we can ensure the file hasn't been unlinked before resolving it.I think my explanation might be a little confusing, but if needed I can give more information.