-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Explicitly read the artifact into memory before uploading to the remote cache api #898
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Explicitly read the artifact into memory before uploading to the remote cache api #898
Conversation
Since the artifact is already read anyways, this doens't add additional overhead.
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/vercel/turbo-site/5PpWuHkj1vBhHvKQHRx1n4dqGgC1 [Deployment for a50134d failed] |
@gaspar09 What do you think about setting the |
Yep. Going to add a test to make sure it actually gets added as expected. |
Let's change the global cache key here to be safe. @gaspar09 your turn to pick |
Read the tar artifact into memory so that we can compute the content-md5
This read was already happening implicitly via the
retryableHttp
module.