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
Error when uploading to GitHub release: "Error from GitHub: Validation Failed" #221
Comments
Also, I'm using Node 10 on the CI machine so that I can make prebuilds for that version, dunno if that is contributing to the issue. Strangely the issue went away on its own on TravisCI after a rebuild but it fails consistently on Appveyor. |
@vweevers Any thoughts? |
@daviwil We could start by tweaking |
@ralphtheninja isn't "Validation failed" an error returned by GitHub? Not much we can do. |
It is, but there might also be a |
@daviwil You could try AppVeyor again to see if we get any better messages. |
Thanks @ralphtheninja! Definitely clearer now:
Looks like there are some partially uploaded assets from a previous build: Just cleared those out and running another build to see if it resolves the issue. |
Failed again for the same reason... I'll try debugging it locally on my machine to see what's going on. |
I'm getting this for node serialport when I switched to node 10 builds to work around the prebuild/prebuildify#10 |
@daviwil Did you manage to get any more information by debugging locally? |
it appears to be uploading the files twice |
Might be a bug in https://github.com/ralphtheninja/ghreleases , but strange that we haven't noticed it before. I'll try to reproduce with |
@daviwil I went through your setup for I can explain in greater detail if you like. |
I'm wondering if there are multiple builds running on e.g. AppVeyor that try to build and upload the same binaries. |
Thanks for looking into this @ralphtheninja! I hadn't come across |
I can confirm that I get dupes uploaded in a single call to my upload npm script and that no other builds produce the same files. |
So all it takes to reproduce is a |
Node 10
…On Sat, Jun 30, 2018, 5:12 AM Lars-Magnus Skog ***@***.***> wrote:
I can confirm that I get dupes uploaded in a single call to my upload npm
script and that no other builds produce the same files. "prebuild-upload":
"prebuild --all --strip --verbose"
So all it takes to reproduce is a npm run prebuild-upload in
node-serialport? Which version of node? I'd like to reproduce this.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#221 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABlbnwrIK_P0ln_2yK5ggh_Q12FXS4rks5uB0EMgaJpZM4Uz3ZL>
.
|
It looks like I'm getting this on node 8. https://travis-ci.org/node-serialport/node-serialport/jobs/406510232
It does publish the binaries, but seems to fail after when maybe it tries again? |
This problem seems to be in Added some debug information and upload.js:filtered contains duplicate entries that causes some files to be uploaded twice.
|
I have found the root cause of the issue.
Only the runtime and the abi fields are used to build the filename and prebuild package name, which results in one file for |
Awesome find! I'll start by patching |
@ralphtheninja I have submitted a PR to fix this issue on the prebuild side also: #226 Thanks! It's up to you if you want to keep a GIGO policy or implement a filter for this, because I think it is quite an invalid input to ghreleases to call it with duplicate entries. |
Hey folks, I'm running prebuild on CI after not having used it in a while and I'm getting this error when prebuild tries to upload assets to a GitHub release:
I've recreated the GitHub token I'm using in CI to upload the releases so it shouldn't be an authentication issue. Any idea what might be causing this?
The text was updated successfully, but these errors were encountered: