-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Getting UnsupportedHeader code while trying to upload artifact #1910
Comments
I am also facing this issue. We do not set any headers while calling uploadArtifact method. It started failing after v2.2.0 release. Any breaking changes were released? |
👋🏼 @akshaykhante @divyanshu2601 could you please repro the issue and give me the |
@yacaovsnc It is ‘09c3bb65-ffab-4a46-b63a-47a18dcb451e’ |
@akshaykhante thanks. I also need the blob you are trying to upload to narrow down the query - I need the Azure Blob server name as well. Could you please show us the entire http call the script is trying to make? |
@yacaovsnc sharing entire blob would not be possible. The size of blob is 25.2 mb. Below is the part of script where i am calling uploadArtifact
where filesToUpload is a list of one or more files. |
Describe the bug
Getting UnsupportedHeader code while trying to upload artifact
To Reproduce
Steps to reproduce the behavior:
We noticed UnsupportedHeader error coming in x-ms-error-code in version 2.1.8 @action/artifact
We upgraded @actions/artifact to 2.2.0 in our package.json
We have made call to uploadArtifact(artifactName, files, root directory, {retentionDays} of DefaultArtifactClient of @actions/artifact from our js file.
We observed below behaviour:
upload-artifact.js makes call to uploadZipToBlobStorage under blob-upload.js where it makes a call to uploadStream method present in storage-blob and error occurs at uploadStream method where error says : RestError: One of the HTTP headers specified in the request is not supported.
When we look at the request header it is as below :
Expected behavior
Requested Artifact Should get uploaded to workflow .
Screenshots
Attached request header in point 5 above.
Response header looks like below :
Additional context
My first guess would be if x-ms-version 2025-01-05 is able to support the header being passed from @action/artifact ?
The text was updated successfully, but these errors were encountered: