Skip to content

[bug] Unable to download artifact(s): Unable to download and extract artifact: Request timeout #249

Closed

Description

@mathbunnyru

What happened?

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

The link is here:
https://github.com/jupyter/docker-stacks/actions/runs/7214568077

What did you expect to happen?

Successful run

How can we reproduce it?

Possibly fork jupyter/docker-stacks and run the docker.yml workflow

Anything else we need to know?

I tried to restart the build a few times - seems to work sometimes.
The runner which downloads the artifact is a GitHub-hosted runner.

What version of the action are you using?

v4

What are your runner environments?

linux

Are you on GitHub Enterprise Server? If so, what version?

No response

Activity

  1. mathbunnyru commented on Dec 14, 2023

    @mathbunnyru
    Author

    This only happened when I switched to v4 a few hours ago.

  2. acgxv commented on Dec 15, 2023

    @acgxv

    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.

  3. IvanGithub-Professional commented on Dec 15, 2023

    @IvanGithub-Professional

    @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

  4. mathbunnyru commented on Dec 15, 2023

    @mathbunnyru
    Author

    @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.

  5. submarines-and commented on Dec 15, 2023

    @submarines-and

    Happens to us intermittently as well. Both actions are v4

    Error: Unable to download artifact(s): Unable to download and extract artifact: Request timeout:

  6. Santas commented on Dec 15, 2023

    @Santas

    After upgrading to v4 we saw similar issue

    Error: Unable to download artifact(s): Unable to download and extract artifact: Unexpected HTTP response from blob storage: 503 The server is busy.
    
  7. added a commit that references this issue on Dec 15, 2023
  8. RickyDaMa commented on Dec 15, 2023

    @RickyDaMa

    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

  9. jamezp commented on Dec 15, 2023

    @jamezp

    Just another "I'm seeing this too" https://github.com/resteasy/resteasy-microprofile/actions/runs/7224411814. The artifact is definitely there.

  10. cmeister2 commented on Dec 15, 2023

    @cmeister2

    Ditto, after upgrading curl/curl-fuzzer from v3 to v4.

  11. JasonGross commented on Dec 16, 2023

    @JasonGross

    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?

  12. added a commit that references this issue on Dec 16, 2023
  13. added a commit that references this issue on Dec 16, 2023
  14. 43 remaining items

  15. mhemmings commented on Jan 10, 2024

    @mhemmings

    @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?

  16. jeroen commented on Feb 20, 2024

    @jeroen

    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

  17. Garett-MacGowan commented on Apr 5, 2024

    @Garett-MacGowan

    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

    I noticed that your failure is not related to a timeout.

    Can someone confirm whether the timeout issue is fixed?

  18. dannyskoog commented on Apr 5, 2024

    @dannyskoog

    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

    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

  19. rwader-swi commented on Nov 13, 2024

    @rwader-swi

    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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions