Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error: Socket Hang up when electron-builder Release on github.

See original GitHub issue

Version: 22.6.0
Electron Version:8.1.1
Electron Type (current, beta, nightly):Current

Target: NSIS Windows

My electron-builder.json file for configurations

{
  "appId": "com.screenshot.app",
  "copyright": "Copyright © 2019-Tushar Kanjariya",
  "productName": "Screenshot App",
  "nsis": {
    "perMachine": true,
    "oneClick": false,
    "allowToChangeInstallationDirectory": false,
    "license": "LICENSE.txt",
    "allowElevation": true
  },
  "publish": {
    "provider": "github",
    "owner": "TusharKanjariya",
    "repo": "screenshot-app-electron",
    "token": "my_token"
  }
}

When I run the command npm run publish:github then the following error will occur after the final build and uploading

Plz, Help to solve my Issue.

Issue Analytics

State:
Created 3 years ago
Reactions:16
Comments:85 (11 by maintainers)

Top GitHub Comments

5reactions

ocavuecommented, Jun 8, 2022

GitHub’s official actions/upload-artifact seems to resolve this issue by adding retries:

https://github.com/actions/upload-artifact/issues/116#issuecomment-754141048

Should be good now. Retries with exponential back-off have been added to all HTTP calls so any socket disconnects, timeouts, 503s or ECONNRESET errors should gracefully now retry and the artifact upload should go through (previously only a subset of HTTP calls during upload were retried). Recent updates should significantly improve reliability.

5reactions

sheckcommented, Sep 19, 2021

I’m still seeing this on an electron project I work on. When we run parallel windows and Mac builds on GH actions that publishes to GH releases, it seems to fail about 60% of the time with this error.

We’ve since switched to serialized builds and haven’t encountered the issue anymore, but it would be nice to have parallel builds again.