Code:already_exists when uploading to release page

[maidul98]

I keep getting

error=scm releases: failed to publish artifacts: failed to upload 

 422 Validation Failed [{Resource:ReleaseAsset Field:name Code:already_exists Message:}]

I have seen others also have this same issue but looks like no solution exists. Is there a way to over write the files and prevent this issue from failing the release?

[caarlos0]

you should probably delete the old release there, or just its assets, and re-run goreleaser.

make sure there are no cases of goreleaser running 2 times in parallel or something in that sense.

all available options are documented here: https://goreleaser.com/customization/release/

[maidul98]

I deleted the release so there were no releases before i started. How would I delete the assets? I assumed they would be deleted when i delete the release as well. However, even with no release page i tried again and ran into the same issue.

I'm not too sure but it looks like it is trying to upload twice from the logs

• scm releases
      • creating or updating release                 repo=Infisical/infisical-merge tag=v0.0.99
      • uploading to release                         file=dist/infisical-merge_0.0.99_windows_arm64.tar.gz name=infisical-merge_0.0.99_windows_arm64.tar.gz
      • uploading to release                         file=dist/infisical-merge_0.0.99_linux_armv6.tar.gz name=infisical-merge_0.0.99_linux_armv6.tar.gz
      • uploading to release                         file=dist/infisical-merge_0.0.99_linux_armv7.tar.gz name=infisical-merge_0.0.99_linux_armv7.tar.gz
      • uploading to release                         file=dist/infisical-merge_0.0.99_windows_armv6.tar.gz name=infisical-merge_0.0.99_windows_armv6.tar.gz
      • uploading to release                         file=dist/infisical-merge_0.0.99_windows_armv5.tar.gz name=infisical-merge_0.0.99_windows_armv5.tar.gz
      • uploading to release                         file=dist/infisical-merge_0.0.99_windows_armv7.tar.gz name=infisical-merge_0.0.99_windows_armv7.tar.gz
      • uploading to release                         file=dist/infisical-merge_0.0.99_windows_amd64.tar.gz name=infisical-merge_0.0.99_windows_amd64.tar.gz
      • uploading to release                         file=dist/infisical-merge_0.0.99_darwin_amd64.tar.gz name=infisical-merge_0.0.99_darwin_amd64.tar.gz
      • uploading to release                         file=dist/infisical-merge_0.0.99_linux_armv5.tar.gz name=infisical-merge_0.0.99_linux_armv5.tar.gz
      • uploading to release                         file=dist/infisical-merge_0.0.99_darwin_arm64.tar.gz name=infisical-merge_0.0.99_darwin_arm64.tar.gz
      • uploading to release                         file=dist/infisical-merge_0.0.99_linux_arm64.tar.gz name=infisical-merge_0.0.99_linux_arm64.tar.gz
      • uploading to release                         file=dist/infisical-merge_0.0.99_linux_amd64.tar.gz name=infisical-merge_0.0.99_linux_amd64.tar.gz
      • uploading to release                         file=dist/infisical-merge_0.0.99_linux_arm.rpm name=infisical-merge_0.0.99_linux_arm.rpm
      • uploading to release                         file=dist/infisical-merge_0.0.99_linux_arm.rpm name=infisical-merge_0.0.99_linux_arm.rpm
      • uploading to release                         file=dist/infisical-merge_0.0.99_linux_amd64.rpm name=infisical-merge_0.0.99_linux_amd64.rpm
      • failed to upload artifact, will retry        artifact=infisical-merge_0.0.99_linux_arm.rpm error=POST https://uploads.github.com/repos/Infisical/infisical-merge/releases/83431789/assets?name=infisical-merge_0.0.99_linux_arm.rpm: 404 Not Found [] try=1
      • uploading to release                         file=dist/infisical-merge_0.0.99_linux_arm.rpm name=infisical-merge_0.0.99_linux_arm.rpm
      • uploading to release                         file=dist/infisical-merge_0.0.99_linux_arm.rpm name=infisical-merge_0.0.99_linux_arm.rpm
      • failed to upload artifact, will retry        artifact=infisical-merge_0.0.99_linux_arm.rpm error=Post "https://uploads.github.com/repos/Infisical/infisical-merge/releases/83431789/assets?name=infisical-merge_0.0.99_linux_arm.rpm": http2: Transport: cannot retry err [stream error: stream ID 31; REFUSED_STREAM; received from peer] after Request.Body was written; define Request.GetBody to avoid this error try=2
      • uploading to release                         file=dist/infisical-merge_0.0.99_linux_arm.rpm name=infisical-merge_0.0.99_linux_arm.rpm
      • failed to upload artifact, will retry        artifact=infisical-merge_0.0.99_linux_arm.rpm error=Post "https://uploads.github.com/repos/Infisical/infisical-merge/releases/83431789/assets?name=infisical-merge_0.0.99_linux_arm.rpm": http2: Transport: cannot retry err [stream error: stream ID 35; REFUSED_STREAM; received from peer] after Request.Body was written; define Request.GetBody to avoid this error try=3
      • uploading to release                         file=dist/infisical-merge_0.0.99_linux_arm.rpm name=infisical-merge_0.0.99_linux_arm.rpm
      • failed to upload artifact, will retry        artifact=infisical-merge_0.0.99_linux_arm.rpm error=POST https://uploads.github.com/repos/Infisical/infisical-merge/releases/83431789/assets?name=infisical-merge_0.0.99_linux_arm.rpm: 422 Validation Failed [{Resource:ReleaseAsset Field:name Code:already_exists Message:}] try=1

It looks like it tried to upload infisical-merge_0.0.99_linux_amd64.rpm again after it uplaoded it. When i look in the release page infisical-merge_0.0.99_linux_amd64.rpm was indeed uploaded.

I'm not sure why it would be doing this two times as i have defult settings for most things

Work flow file: https://github.com/Infisical/infisical-merge/blob/main/.github/workflows/release_build.yml
Go releaser file: https://github.com/Infisical/infisical-merge/blob/main/.goreleaser.yaml

Any ideas? Thank you!

[caarlos0]

you probably need to report that to github... its an issue that happen on their side sometimes, the upload fails, but it actually "succeeds", and further uploads then fail

[maidul98]

I found the issue. It was because I set a custom file name format for nFPM section which didn't include the goos. So for different goos it created the same file.

[caarlos0]

ahh that might be it too yes!