electron-builder
electron-builder copied to clipboard
electron-userland
Error: Socket Hang up when electron-builder Release on github.
-
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.
Is this consistently reproducable? This seems like it could be related: https://github.com/request/request/issues/2047
Have you tried upgrading your node version?
@b-zurg My Current Node version is v13.13.0. I have tried this solution but can't able to solve the issue.
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
![stale[bot] avatar](https://avatars.githubusercontent.com/in/1724?v=4 "Published by a pub.dev verified publisher"){kind=small}
Question - how long does the upload take? This sort of error is something I've encountered elsewhere on long uploads
I am having the same today, never had this issue before: https://travis-ci.com/github/hovancik/stretchly/jobs/362382915
⨯ Cannot cleanup:
Error #1 --------------------------------------------------------------------------------
Error: socket hang up
at connResetException (internal/errors.js:570:14)
at TLSSocket.socketOnEnd (_http_client.js:440:23)
at TLSSocket.emit (events.js:228:7)
at endReadableNT (_stream_readable.js:1185:12)
at processTicksAndRejections (internal/process/task_queues.js:81:21)
Error #2 --------------------------------------------------------------------------------
Error: socket hang up
at connResetException (internal/errors.js:570:14)
at TLSSocket.socketOnEnd (_http_client.js:440:23)
at TLSSocket.emit (events.js:228:7)
at endReadableNT (_stream_readable.js:1185:12)
at processTicksAndRejections (internal/process/task_queues.js:81:21)
Error #3 --------------------------------------------------------------------------------
Error: socket hang up
at connResetException (internal/errors.js:570:14)
at TLSSocket.socketOnEnd (_http_client.js:440:23)
at TLSSocket.emit (events.js:228:7)
at endReadableNT (_stream_readable.js:1185:12)
at processTicksAndRejections (internal/process/task_queues.js:81:21)
Error #4 --------------------------------------------------------------------------------
Error: socket hang up
at connResetException (internal/errors.js:570:14)
at TLSSocket.socketOnEnd (_http_client.js:440:23)
at TLSSocket.emit (events.js:228:7)
at endReadableNT (_stream_readable.js:1185:12)
at processTicksAndRejections (internal/process/task_queues.js:81:21)
Error #5 --------------------------------------------------------------------------------
Error: socket hang up
at connResetException (internal/errors.js:570:14)
at TLSSocket.socketOnEnd (_http_client.js:440:23)
at TLSSocket.emit (events.js:228:7)
at endReadableNT (_stream_readable.js:1185:12)
at processTicksAndRejections (internal/process/task_queues.js:81:21) stackTrace=
Error: Cannot cleanup:
Error #1 --------------------------------------------------------------------------------
Error: socket hang up
at connResetException (internal/errors.js:570:14)
at TLSSocket.socketOnEnd (_http_client.js:440:23)
at TLSSocket.emit (events.js:228:7)
at endReadableNT (_stream_readable.js:1185:12)
at processTicksAndRejections (internal/process/task_queues.js:81:21)
Error #2 --------------------------------------------------------------------------------
Error: socket hang up
at connResetException (internal/errors.js:570:14)
at TLSSocket.socketOnEnd (_http_client.js:440:23)
at TLSSocket.emit (events.js:228:7)
at endReadableNT (_stream_readable.js:1185:12)
at processTicksAndRejections (internal/process/task_queues.js:81:21)
Error #3 --------------------------------------------------------------------------------
Error: socket hang up
at connResetException (internal/errors.js:570:14)
at TLSSocket.socketOnEnd (_http_client.js:440:23)
at TLSSocket.emit (events.js:228:7)
at endReadableNT (_stream_readable.js:1185:12)
at processTicksAndRejections (internal/process/task_queues.js:81:21)
Error #4 --------------------------------------------------------------------------------
Error: socket hang up
at connResetException (internal/errors.js:570:14)
at TLSSocket.socketOnEnd (_http_client.js:440:23)
at TLSSocket.emit (events.js:228:7)
at endReadableNT (_stream_readable.js:1185:12)
at processTicksAndRejections (internal/process/task_queues.js:81:21)
Error #5 --------------------------------------------------------------------------------
Error: socket hang up
at connResetException (internal/errors.js:570:14)
at TLSSocket.socketOnEnd (_http_client.js:440:23)
at TLSSocket.emit (events.js:228:7)
at endReadableNT (_stream_readable.js:1185:12)
at processTicksAndRejections (internal/process/task_queues.js:81:21)
at throwError (/home/travis/build/hovancik/stretchly/node_modules/builder-util/src/asyncTaskManager.ts:90:11)
at checkErrors (/home/travis/build/hovancik/stretchly/node_modules/builder-util/src/asyncTaskManager.ts:53:9)
at AsyncTaskManager.awaitTasks (/home/travis/build/hovancik/stretchly/node_modules/builder-util/src/asyncTaskManager.ts:58:5)
at PublishManager.awaitTasks (/home/travis/build/hovancik/stretchly/node_modules/app-builder-lib/src/publish/PublishManager.ts:210:28)
at /home/travis/build/hovancik/stretchly/node_modules/app-builder-lib/src/index.ts:94:32
at executeFinally (/home/travis/build/hovancik/stretchly/node_modules/builder-util/src/promise.ts:25:9)
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
Hello 🖖🏻
I am also facing this issue since some weeks ago. I now always to re-run the Github Actions until it works.
https://github.com/Graviton-Code-Editor/Graviton-App/runs/1140459243?check_suite_focus=true
Notes:
- It fails randomly
- Only fails in Windows and Ubuntu
Publishing is almost unusable. It is falling for me at a ratio of around one successful upload to five failed ones.
I have experienced socket hang ups in different contexts when there is a long running upload. It depends on the specific connection being made and if the connection is not kept alive the upload target thinks it's a dead connection and kills it.
That's what it seems like is happening here. The comments indicate that it does go through sometimes. I would bet that those times the upload happened just a bit faster.
I'm also going to guess that is it's under 2 minutes it's fine as the default connection time out for node JS is 2 minutes.
Could anyone verify these guesses?
If I'm reading this right, there is no option to set a preferred timeout and it may fail four times before rejecting the upload.
I've noticed something else: it doesn't fail at the times my draft release is empty, i.e., when there is no need to overwrite files. Looking at all the examples you folks posted here, they all are trying to overwrite files. Is it possible that a change in GitHub API is the root cause?
I've noticed something else: it doesn't fail at the times my draft release is empty, i.e., when there is no need to overwrite files. Looking at all the examples you folks posted here, they all are trying to overwrite files. Is it possible that a change in GitHub API is the root cause?
You are absolutely right, it has only been randomly failing when I had a draft matching the same version. Now I have increased the version, it does no longer match the draft's version so it now doesn't randomly fail anymore
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
yeap. still.
Can also confirm that this is still an issue, and yes, only occurs if the version tag already exists (i.e. it is overwriting a file).
Having the same issue: publishing a ~60-80mb package fails on Windows and Linux fairly often, and I have to restart the action. I seem to remember seeing it fail on macOS too, but I restarted the GitHub action, and no longer have the logs to verify. I can verify however what has been observed before: it only fails if there's assets to overwrite. Haven't seen it fail when publishing new assets.
Adding log file failed upload to github from Azure Pipelines
==============================================================================
Task : Bash
Description : Run a Bash script on macOS, Linux, or Windows
Version : 3.179.0
Author : Microsoft Corporation
Help : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/bash
==============================================================================
Generating script.
Script contents:
yarn dist
========================== Starting Command Output ===========================
/bin/bash --noprofile --norc /Users/runner/work/_temp/4d3341b5-17ab-4376-b393-6d6bde38ab4f.sh
yarn run v1.22.5
$ electron-builder
• electron-builder version=22.9.1 os=18.7.0
• artifacts will be published if draft release exists reason=CI detected
• loaded configuration file=package.json ("build" field)
• rebuilding native dependencies dependencies=@tensorflow/[email protected], [email protected] platform=darwin arch=x64
• rebuilding native dependency name=sqlite3 version=5.0.0
• rebuilding native dependency name=@tensorflow/tfjs-node version=1.5.1
• packaging platform=darwin arch=x64 electron=8.5.2 appOutDir=artifacts/mac
• downloading url=https://github.com/electron/electron/releases/download/v8.5.2/electron-v8.5.2-darwin-x64.zip size=66 MB parts=6
• downloaded url=https://github.com/electron/electron/releases/download/v8.5.2/electron-v8.5.2-darwin-x64.zip duration=1.161s
• signing file=artifacts/mac/XXX
identityHash=XXX provisioningProfile=none
Notorization skipped in the CI
• building target=macOS zip arch=x64 file=artifacts/xxx.zip
• building target=DMG arch=x64 file=artifacts/xxx.dmg
• building embedded block map file=artifacts/xxx.zip
• publishing publisher=Github (owner: iERP-ai, project: studio, version: 0.9.4-dev)
• uploading file=xxx.zip provider=GitHub
• building block map blockMapFile=artifacts/xxx.dmg.blockmap
• uploading file=xxx.dmg.blockmap provider=GitHub
• uploading file=xxx.dmg provider=GitHub
⨯ write EPIPE stackTrace=
Error: write EPIPE
at WriteWrap.onWriteComplete [as oncomplete] (internal/stream_base_commons.js:92:16)
at handleWriteReq (internal/stream_base_commons.js:51:26)
at writeGeneric (internal/stream_base_commons.js:143:15)
at TLSSocket.Socket._writeGeneric (net.js:784:11)
at TLSSocket.Socket._write (net.js:796:8)
at doWrite (_stream_writable.js:403:12)
at doWrite (_stream_writable.js:403:12)
at clearBuffer (_stream_writable.js:542:7)
at TLSSocket.Writable.uncork (_stream_writable.js:338:7)
at ClientRequest.OutgoingMessage.uncork (_http_outgoing.js:244:17)
at connectionCorkNT (_http_outgoing.js:698:8)
at processTicksAndRejections (internal/process/task_queues.js:84:21)
• overwrite published file file=xxx.dmg.blockmap reason=already exists on GitHub
• overwrite published file file=xxx.dmg reason=already exists on GitHub
error Command failed with exit code 1.
Also facing this. I have tried to run GitHub Actions about 7 times now to get this build to upload :/
This is essentially making it unusable.
Can also confirm that this is still an issue, and yes, only occurs if the version tag already exists (i.e. it is overwriting a file).
Could the script perhaps try and delete the file first, then upload?
Can also confirm that this is still an issue, and yes, only occurs if the version tag already exists (i.e. it is overwriting a file).
Could the script perhaps try and delete the file first, then upload?
https://github.com/electron-userland/electron-builder/blob/0ba839b72b6a13178ad5bc4b03a47f9aca980650/packages/electron-publish/src/gitHubPublisher.ts#L186-L188
I'm afraid if it is already doing it. I'm not even sure if this is the right place to look at because i have not contributed to this repo at all, but If I have some time later i might dig into this. I might be wrong, but i'm suspecting it might be some changes in Github API that breaks the if statement or something https://github.com/electron-userland/electron-builder/blob/0ba839b72b6a13178ad5bc4b03a47f9aca980650/packages/electron-publish/src/gitHubPublisher.ts#L186
Can also confirm that this is still an issue, and yes, only occurs if the version tag already exists (i.e. it is overwriting a file).
Could the script perhaps try and delete the file first, then upload?
https://github.com/electron-userland/electron-builder/blob/0ba839b72b6a13178ad5bc4b03a47f9aca980650/packages/electron-publish/src/gitHubPublisher.ts#L186-L188
I'm afraid if it is already doing it. I'm not even sure if this is the right place to look at because i have not contributed to this repo at all, but If I have some time later i might dig into this. I might be wrong, but i'm suspecting it might be some changes in Github API that breaks the if statement or something https://github.com/electron-userland/electron-builder/blob/0ba839b72b6a13178ad5bc4b03a47f9aca980650/packages/electron-publish/src/gitHubPublisher.ts#L186
I think you are right. I can take a look too, just trying to work out how to run this project from a fork right now.
Can also confirm that this is still an issue, and yes, only occurs if the version tag already exists (i.e. it is overwriting a file).
Could the script perhaps try and delete the file first, then upload?
https://github.com/electron-userland/electron-builder/blob/0ba839b72b6a13178ad5bc4b03a47f9aca980650/packages/electron-publish/src/gitHubPublisher.ts#L186-L188
I'm afraid if it is already doing it. I'm not even sure if this is the right place to look at because i have not contributed to this repo at all, but If I have some time later i might dig into this. I might be wrong, but i'm suspecting it might be some changes in Github API that breaks the if statement or something https://github.com/electron-userland/electron-builder/blob/0ba839b72b6a13178ad5bc4b03a47f9aca980650/packages/electron-publish/src/gitHubPublisher.ts#L186
Na, it's getting into that loop.
• overwrite published file file=Balance-Bar-Setup-0.5.0.exe.blockmap reason=already exists on GitHub
⨯ socket hang up stackTrace=
Error: socket hang up
at connResetException (internal/errors.js:607:14)
at TLSSocket.socketOnEnd (_http_client.js:493:23)
at TLSSocket.emit (events.js:327:22)
at endReadableNT (internal/streams/readable.js:1327:12)
at processTicksAndRejections (internal/process/task_queues.js:80:21)
Well yeah. perhaps related: https://github.com/request/request/issues/2047
Regardless of whether we use request i think it just might be a general issue across node.js applications. Based on the thread, we may also want to try fiddling around with request headers.