ALHP/ALHP.GO
7
43
Fork 8
Code Issues 30 Pull Requests Projects Releases Wiki Activity

Build with nodejs seems to fail due to network issues #72

New Issue
Closed
opened 2021-11-30 22:33:03 +01:00 by Gontier-Julien · 5 comments
Gontier-Julien commented 2021-11-30 22:33:03 +01:00
Copy Link

All new builds with nodejs seems to fail due to a network issue.

quick lists:

  • code
  • all electrons build
  • and others...

quick log

node build/npm/preinstall.js
[1/4] Resolving packages...
[2/4] Fetching packages...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
All new builds with nodejs seems to fail due to a network issue. quick lists: - code - all electrons build - and others... quick log ``` node build/npm/preinstall.js [1/4] Resolving packages... [2/4] Fetching packages... info There appears to be trouble with your network connection. Retrying... info There appears to be trouble with your network connection. Retrying... info There appears to be trouble with your network connection. Retrying... ```
anonfunc commented 2021-11-30 22:38:38 +01:00
Owner
Copy Link

I noticed that as well. Server overall connection status is fine, so there is either some routing issue to some npm reg. or a specific issue on their side, not sure.

I noticed that as well. Server overall connection status is fine, so there is either some routing issue to some npm reg. or a specific issue on their side, not sure.
👍 1
Gontier-Julien commented 2021-12-02 11:30:18 +01:00
Author
Copy Link

I noticed that as well. Server overall connection status is fine, so there is either some routing issue to some npm reg. or a specific issue on their side, not sure.

I've found a pottential fix that we could test, but i don't think there is a proxy, but it good to try:

npm config rm proxy
npm config rm https-proxy

> I noticed that as well. Server overall connection status is fine, so there is either some routing issue to some npm reg. or a specific issue on their side, not sure. I've found a pottential fix that we could test, but i don't think there is a proxy, but it good to try: > npm config rm proxy npm config rm https-proxy
anonfunc commented 2021-12-02 11:58:23 +01:00
Owner
Copy Link

I've found a pottential fix that we could test, but i don't think there is a proxy, but it good to try:

npm config rm proxy
npm config rm https-proxy

That should not apply to a clean chroot, since there is no npm config that could have a proxy set.

My guess is it was some sort of temporary issue, and we just hit bad timing with all these builds falling into a short timeframe.

Lets observe if this problem persist first, then we can think about possible solutions.

> I've found a pottential fix that we could test, but i don't think there is a proxy, but it good to try: > > > npm config rm proxy > npm config rm https-proxy That should not apply to a clean chroot, since there is no npm config that could have a proxy set. My guess is it was some sort of temporary issue, and we just hit bad timing with all these builds falling into a short timeframe. Lets observe if this problem persist first, then we can think about possible solutions.
Gontier-Julien commented 2021-12-02 12:37:41 +01:00
Author
Copy Link

I've found a pottential fix that we could test, but i don't think there is a proxy, but it good to try:

npm config rm proxy
npm config rm https-proxy

That should not apply to a clean chroot, since there is no npm config that could have a proxy set.

My guess is it was some sort of temporary issue, and we just hit bad timing with all these builds falling into a short timeframe from another.

Lets observe if this problem persist first, then we can think about possible solutions.

Okay no problem 👍

> > I've found a pottential fix that we could test, but i don't think there is a proxy, but it good to try: > > > > > npm config rm proxy > > npm config rm https-proxy > > That should not apply to a clean chroot, since there is no npm config that could have a proxy set. > > My guess is it was some sort of temporary issue, and we just hit bad timing with all these builds falling into a short timeframe from another. > > Lets observe if this problem persist first, then we can think about possible solutions. Okay no problem 👍
anonfunc commented 2021-12-05 13:27:49 +01:00
Owner
Copy Link

This seems to have resolved itself, closing for now.

This seems to have resolved itself, closing for now.
👍 1
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
blocked upstream
bug
Something is not working
 build-failure
package build fails
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 informational
Provides information about something
 invalid
Something is wrong
 invalid/corrupt package
Package needs to be rebuild
 packaging issue
priority: high
High priority
 question
More information is needed
 support
wontfix
This won't be fixed
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
anonfunc
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: ALHP/ALHP.GO#72
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?