npm install network errors with build.snapcraft.io proxy configuration
Metadata
Current evaluation
Electron-packager downloads failed behind the legacy build.snapcraft.io proxy; that hosted-build service is no longer part of current remote builds.
Suggested action: close stale
Reason: The report targets build.snapcraft.io, and the matching issue record identifies that hosted-build proxy request as obsolete because current remote builds use Launchpad and no longer include the affected service. The repository has no current build.snapcraft.io references, and merged PR canonical/snapcraft#5785 addresses Launchpad honoring proxy variables, so the original 2020 failure no longer has an actionable current target.
Evaluated by: mr-cal-bot
Impact:
25
Quick Win:
14
Complexity:
30
Confidence:
93
Actionability:
80
Issue body
Note: I originally discovered this issue last year and it got fixed upstream with electron-packager (https://forum.snapcraft.io/t/getaddrinfo-enotfound-github-com-builds-failing-on-snapcraft-io-due-to-network-problems/14164/6) but the problem seems to have returned.
My snapcraft.yaml (https://github.com/krellian/kiosk/blob/master/snap/snapcraft.yaml) runs `npm install` in override-build, which includes installing the electron-packager npm package. That installation process tries to fetch resources from github.com:443 and fails due to the network proxy configuration being used on build.snapcraft.io
RequestError: getaddrinfo ENOTFOUND github.com github.com:443
Full build log here: https://build.snapcraft.io/user/krellian/kiosk/1034152
I was able to work around this issue by adding the following to my snapcraft.yaml but it would be great if this could be fixed. I suspect it's probably an upstream bug again, but perhaps there's something that could be changed about the build server configuration to reduce these types of errors?
if [ -n "$http_proxy" ]; then
export ELECTRON_GET_USE_PROXY=1
export GLOBAL_AGENT_HTTP_PROXY="${http_proxy}"
export GLOBAL_AGENT_HTTPS_PROXY="${http_proxy}"
fi
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
25
Quick Win:
14
Complexity:
30
Confidence:
93
Actionability:
80
|
close stale | Electron-packager downloads failed behind the legacy build.snapcraft.io proxy; that hosted-build service is no longer part of current remote builds. | |
| stealth/space-bunny-alpha |
Impact:
45
Quick Win:
9
Complexity:
67
Confidence:
82
Actionability:
61
|
keep open | Electron Packager downloads GitHub assets without honoring the build-service proxy during npm install. A workaround exists, and maintainers agreed proxy bridging belongs in Snapcraft rather than Launchpad. | |
| stealth/space-bunny-alpha |
Impact:
35
Quick Win:
6
Complexity:
58
Confidence:
79
Actionability:
42
|
close stale | Obsolete build.snapcraft.io proxy request: npm/Electron downloads bypassed the hosted-build proxy; current remote builds use Launchpad and no longer include the affected service. | |
| qwen/qwen3.6-35b-a3b |
Impact:
30
Quick Win:
9
Complexity:
40
Confidence:
60
Actionability:
50
|
needs triage | npm install fails on build.snapcraft.io due to proxy configuration issues with electron-packager fetching from github.com; reporter provides workaround using environment variables | |
| qwen/qwen3.8-27b |
Impact:
15
Quick Win:
9
Staleness:
95
Complexity:
40
Confidence:
75
Support Request:
35
|
close stale | npm install fails with getaddrinfo ENOTFOUND github.com due to build.snapcraft.io proxy config; reporter has a workaround via proxy env vars. ~6 years old, zero comments, and the affected build service has since been decommissioned. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
30
Confidence:
70
Support Request:
20
|
needs triage | External contributor reports npm install failing on build.snapcraft.io due to proxy configuration. The issue lacks labels, has zero maintainer comments, and has been inactive for nearly six years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
20
Confidence:
85
Support Request:
20
|
close stale | npm install fails on build.snapcraft.io due to proxy configuration blocking GitHub access. Unlabeled, no maintainer comments, and inactive for over 5 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
30
Confidence:
85
Support Request:
45
|
close stale | Reports npm install failures on build.snapcraft.io due to proxy configuration for electron-packager. Provides a workaround. No maintainer response or labels after over six years of inactivity. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Related To:
canonical/snapcraft#5785
(confidence 85%)
Merged PR states that Launchpad now respects configured proxy environment variables instead of bypassing them; it is related to the replacement remote-build path, though not a direct Electron-specific fix.
Related issues
No related issues found above the similarity threshold.