You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[bug] Unable to download artifact(s): Unable to download and extract artifact: Request timeout #249
My GitHub workflow tried to download an artifact and got the following error:
Unable to download artifact(s): Unable to download and extract artifact: Request timeout: /actions-results/48835bcc-3d9d-48c1-9b25-e61724c412e6/workflow-job-run-133fda40-ba8c-5571-226b-e94c9a723dbe/artifacts/scipy-notebook-x86_64.zip?se=2023-12-14T22%3A41%3A57Z&sig=kIu7CPVgJ9myrpzJC9NS%2FLVc8z8fcQtdDXC0sDa5DVc%3D&sp=r&spr=https&sr=b&st=2023-12-14T22%3A31%3A57Z&sv=2021-12-02
This only happened when I switched to v4 a few hours ago.
Reacted by Brian Kroth, Nicolas DUBIEN, Tonye Jack, Enrico Minack, Nicolas Duchon, Marcel, Brendan, Mark Hemmings, Ian VanSchooten, Anton Gilgur and 5 more
Alright, it's not a bug on my end. Perhaps others are experiencing the same issue.
The problem is due to some actions not updating their dependencies. I use the new version of upload, and consequently, using an older version of download will result in failure.
Reacted by Jason Gross, Tonye Jack, Marcel, 🇺🇦 Sviatoslav Sydorenko (Святослав Сидоренко) and Rewa Wader
@mathbunnyru I had a very similar Issue created earlier about an artifact not being found. This is a little different because you are receiving a "Request Timeout" but maybe my solution will fix yours. The issue is not being consistent with your Upload & Download versions. I was uploading with version 3 and downloading with version 4. Mine was not considered a bug because it is documented as expected.
My soultion was this
Solution: Be consistent with the versions with your Upload & Download such as action/upload-artifact@v4 and actions/download-artifact@v4
Reacted by Chris Swan
Reacted by Jason Gross, Marcel, JeroenOnline, Chris Ulpinnis, Armin, 🇺🇦 Sviatoslav Sydorenko (Святослав Сидоренко), Jay Jijie Chen and Rewa Wader
@mathbunnyru I had a very similar Issue created earlier about an artifact not being found. This is a little different because you are receiving a "Request Timeout" but maybe my solution will fix yours. The issue is not being consistent with your Upload & Download versions. I was uploading with version 3 and downloading with version 4. Mine was not considered a bug because it is documented as expected.
My soultion was this
Solution: Be consistent with the versions with your Upload & Download such as action/upload-artifact@v4 and actions/download-artifact@v4
Thank you. Unfortunately, I already use v4 in all uploads and downloads.
Reacted by Marcel, JeroenOnline, 🇺🇦 Sviatoslav Sydorenko (Святослав Сидоренко), Anton Gilgur, Agriya Khetarpal, R Mars and Rewa Wader
Similar issue here, v3 works, v4 gives this error when trying to download a definitely-there and definitely-that-name artifact:
Unable to download artifact(s): Unable to download and extract artifact: Unexpected HTTP response from blob storage: 409 Public access is not permitted on this storage account.
Private repo that I can't share, sorry
Reacted by wpbonelli, Nicolas DUBIEN, Marcel, JeroenOnline, Alex Yang, Anton Gilgur and Agriya Khetarpal
@vmjoseph I'm not sure this should be marked as closed, given the "fix" is a bit of a patch/temporary solution masking an underlying issue?
Reacted by Caleb Jasik, Willem Jan Glerum, Peter Sandtner, Nicolas Duchon, Sigurd Fosseng, Florian Lehner, Enrico Minack, Ayaz Salikhov, Andrew Seigner, Malcolm Smith and 20 more
Reacted by 🇺🇦 Sviatoslav Sydorenko (Святослав Сидоренко), Caleb Jasik, James Frost, Agriya Khetarpal, Klaus Viisainen, Adrian Hatch, liuxingbaoyu, Burak Ok, R Mars, Leithen and 1 more
I noticed that your failure is not related to a timeout.
Can someone confirm whether the timeout issue is fixed?
Since the fix was released ~3 months ago I haven't faced the timeout issue again, using v4. Also, the lack of activity in here implies that it was indeed fixed across the board IMHO
ironically v3 is working faster than v4 in my case. Also v3 is less flaky. Regarding the deprecation warning of v3, is it just going to be deprecated or it will be completely out of use?
Activity
mathbunnyru commentedon Dec 14, 2023
This only happened when I switched to v4 a few hours ago.
acgxv commentedon Dec 15, 2023
Same here.
Alright, it's not a bug on my end. Perhaps others are experiencing the same issue.
The problem is due to some actions not updating their dependencies. I use the new version of upload, and consequently, using an older version of download will result in failure.
IvanGithub-Professional commentedon Dec 15, 2023
@mathbunnyru I had a very similar Issue created earlier about an artifact not being found. This is a little different because you are receiving a "Request Timeout" but maybe my solution will fix yours. The issue is not being consistent with your Upload & Download versions. I was uploading with version 3 and downloading with version 4. Mine was not considered a bug because it is documented as expected.
My soultion was this
Solution: Be consistent with the versions with your Upload & Download such as
action/upload-artifact@v4andactions/download-artifact@v4mathbunnyru commentedon Dec 15, 2023
Thank you. Unfortunately, I already use v4 in all uploads and downloads.
submarines-and commentedon Dec 15, 2023
Happens to us intermittently as well. Both actions are v4
Error: Unable to download artifact(s): Unable to download and extract artifact: Request timeout:Santas commentedon Dec 15, 2023
After upgrading to v4 we saw similar issue
ci: Use v3 for upload-artifact.
RickyDaMa commentedon Dec 15, 2023
Similar issue here, v3 works, v4 gives this error when trying to download a definitely-there and definitely-that-name artifact:
Private repo that I can't share, sorry
jamezp commentedon Dec 15, 2023
Just another "I'm seeing this too" https://github.com/resteasy/resteasy-microprofile/actions/runs/7224411814. The artifact is definitely there.
build-ufos-py,import: switch to {upload,download}-artifact@v3
cmeister2 commentedon Dec 15, 2023
Ditto, after upgrading curl/curl-fuzzer from v3 to v4.
JasonGross commentedon Dec 16, 2023
Another example: https://github.com/mit-plv/fiat-crypto/actions/runs/7226837418/job/19695450596?pr=1786#step:6:20 both upload and download are v4. Is the new backend very unstable or something?
downgraded artifact actions to v3
Revert "update artifact actions (#1067)"
43 remaining items
mhemmings commentedon Jan 10, 2024
@vmjoseph I'm not sure this should be marked as closed, given the "fix" is a bit of a patch/temporary solution masking an underlying issue?
⬆️ Upgrade actions/{download,upload}-artifact action to v4 (#4583)
action: bump upload-artifact/download-artifact v4
action: bump upload-artifact/download-artifact v4
action: bump upload-artifact/download-artifact v4
chore(deps): update actions/download-artifact action to v4.1.1 (#158)
build(deps): bump actions/{download,upload}-artifact from 3 to 4
build(deps): bump actions/{download,upload}-artifact from 3 to 4
fix(deps): update all non-major dependencies (#2187)
chore(deps): update actions/download-artifact action to v4.1.2 (#11)
jeroen commentedon Feb 20, 2024
This is still flaky, after bumping to v4 getting lots of failures again: https://github.com/r-universe/tiledb-inc/actions/runs/7978856468/job/21785898976
chore(deps): update github-actions (major) (#719)
Garett-MacGowan commentedon Apr 5, 2024
I noticed that your failure is not related to a timeout.
Can someone confirm whether the timeout issue is fixed?
dannyskoog commentedon Apr 5, 2024
Since the fix was released ~3 months ago I haven't faced the timeout issue again, using v4. Also, the lack of activity in here implies that it was indeed fixed across the board IMHO
rwader-swi commentedon Nov 13, 2024
ironically v3 is working faster than v4 in my case. Also v3 is less flaky. Regarding the deprecation warning of v3, is it just going to be deprecated or it will be completely out of use?