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

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

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

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

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

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

This seems to have resolved itself, closing for now.

👍 1