-
Notifications
You must be signed in to change notification settings - Fork 26
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
java.net.SocketException: Broken pipe (Write failed) #23
Comments
I'm getting the same exception as @stewartbryson. It doesn't seem to be related to the artifact size (I've uploaded 64 Mib successfully), but it always happens on the second artifact in |
Sorry you are experiencing this as well... but I am glad to hear I'm not crazy. It's so strange... I only have one repo build where this is happening and I can't figure out at all what is the difference. |
@stewartbryson Are you uploading more than one artifact? I haven't looked at the code yet to see if that could make any difference, but that seems to be what causes it for me. |
I've uploaded a new version 2.2.9, let me know if that fixes the issue for you. |
@BreadMoirai That fixed it for me. Thanks! |
Sorry for my late response @BreadMoirai. This indeed fixed it for me as well. Thanks so much for this. |
I get the following error with version
2.2.8
. The release is created and the artifact is uploaded, and in general, it "works"... but there is some kind of handshake problem going on. It also happens with version 2.2.7. I tried with 2.2.6, but I get a different error with that version, and it's probably unrelated and not worth describing.Additionally, I'm only getting this with 1 repository out of about 10: the others are successful. The build processes are identical. The only thing that's different is it's an uber JAR, so larger than normal: 59M.
The text was updated successfully, but these errors were encountered: