search

actions / upload-artifact

MIT License
3.01k stars 683 forks source link

[bug] Since actions/upload-artifact@v4 new public artifacts are no longer accessible #486

Closed robert-scheck closed 6 months ago

robert-scheck commented 6 months ago

What happened?

Unfortunately, https://github.com/pdftk-java/pdftk-java-container/pull/9 (actions/upload-artifact@v4) uploads new inaccessible public artifacts. These public artifacts are neither accessible using the GitHub web interface when being logged in nor inside of the action itself using actions/download-artifact@v4 (via https://github.com/pdftk-java/pdftk-java-container/pull/10):

Error: 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.

What did you expect to happen?

Working again like in v3 ;-)

How can we reproduce it?

See URLs above

Anything else we need to know?

Oh, and I do have the trashcan icon (that can be used to delete the artifact). So…I don't have enough permissions to access/download my artifact, but enough permissions to delete it?

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

konradpabjan commented 6 months ago

Here is the failed run https://github.com/pdftk-java/pdftk-java-container/actions/runs/7269244986

The workflow file that does the upload is this:

Image

This looks similar to https://github.com/actions/upload-artifact/issues/473, I was able to reproduce this by uploading an artifact with the # character in the name.

On download during a run with download-artifact@v4 the following annotation appears:

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.

If trying to download from the web UI then this happens:

Image

leettaylor commented 6 months ago

Don't think it's exclusive to having a # in the name as I have it happen with a file simply named public-dir.zip

jtamsut commented 6 months ago

Hey @leettaylor. This is due to the # in your artifact name. If you remove that you should be able to upload successfully. We are aware of this issue and are working on a fix.

Going to close this as its a duplicate of #473.