Repository navigation
fix(cache): stop concurrent download progress timer on failure - #2531
Open
YodHeVauHe wants to merge 2 commits into
Open
YodHeVauHe wants to merge 2 commits into
YodHeVauHe wants to merge 2 commits into
Conversation
Co-authored-by: ZaSourceCode <YodHeVauHe@users.noreply.github.com>
downloadCacheHttpClientConcurrent started a DownloadProgress timer and never cleared it when the download rejected, so the event loop stayed alive until the job timed out. Stop the timer in finally, matching downloadCacheStorageSDK. Co-authored-by: ZaSourceCode <YodHeVauHe@users.noreply.github.com>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes #2509.
downloadCacheHttpClientConcurrentstarted aDownloadProgresstimer and never calledstopDisplayTimer()when the download failed, so the timer kept the process alive until the job timed out. The failure path now stops the timer infinally, the same waydownloadCacheStorageSDKalready did.npm test -- packages/cache/__tests__/downloadUtils.test.ts --runInBandpassed: 1 suite, 4 tests.npm test -- packages/cache --runInBandpassed: 15 suites (1 skipped), 151 tests.