-
-
Notifications
You must be signed in to change notification settings - Fork 112
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
upload failed with socket hang up #44
Comments
Pretty sure this is just a network outage. Can't really do much there except for retrying. |
ok, so you suggest trying it later again? |
Might still be that the worker's network is broken in some way. |
Hello @svenstaro, I am also facing the same issue and getting the following error. However, I may have a hint to solve this issue. Workflow Run Log: https://github.com/pranjal-joshi/Screeni-py/runs/2508182883?check_suite_focus=true I am using the same action to build packages for Windows, Linux and Mac. Here your action is working fine for Windows(.exe) and Linux(.bin) files because it is a single file. However, for Mac, the compiled output Can you please make sure whether this GH action is can handle the directory uploading to the release? Because I never had hands-on experience with Mac so feel free to correct me if required. |
@Borda I am having a similar issue mentioned in the above comment. |
Hi, we ended up switching to another solution |
To make that work I just use PAT around. Not sure if relates but you can try that guys.
|
Write permissions are required for the upload to succeed (either use token, permissions or change the settings > actions > general): |
Since we now have retrying as of 2.5.0, I think we can consider the initial problem fixed. |
Still experiencing this on 2.5.0 |
Hello,
we have been using this action for a few weeks and all were fine till now when I observed the following issue:
Any idea/suggestion on what went wrong?
the trace is here - https://github.com/PyTorchLightning/pytorch-lightning/runs/1822403300?check_suite_focus=true
The text was updated successfully, but these errors were encountered: