@actions/cache: using concurrent download whenever server supported
#1835
Conversation
This file contains 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
…via `Accept-Ranges` header)
Jura45
approved these changes
Oct 27, 2024
|
@dungdm93 could you file an issue detailing your use case? Outside of GitHub Enterprise Server, we don't support other storage providers besides Azure Blob Storage. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 concurrent download cache is currently limited to Azure Blob Storage, requiring users to enable it by setting
DownloadOptions.concurrentBlobDownloads.However, since
S3,GCS, and various file servers also allow partial downloads, it would be beneficial for the cache client to automatically detect server support and utilize concurrent downloads when available.