atom @1.37.0: npm ERR! code ETIMEDOUT

[tifrel (Till)]

Building atom on a M1 fails for me. I suspected the architecture to be at fault, but the log says that npm encounters some timeout while accessing its own API. I tried cleaning distifles and build directories, updating port, updating npm, retried yesterday and today in case npm servers are in trouble, still fails.

:notice:build --->  Building atom
:debug:build Executing org.macports.build (atom)
:debug:build Environment: 
:debug:build CC='/usr/bin/clang -arch arm64'
:debug:build CC_PRINT_OPTIONS='YES'
:debug:build CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_editors_atom/atom/work/.CC_PRINT_OPTIONS'
:debug:build CFLAGS='-Os -mmacosx-version-min=11.0'
:debug:build CPATH='/opt/local/include'
:debug:build CXX='/usr/bin/clang++ -arch arm64'
:debug:build CXXFLAGS='-Os -mmacosx-version-min=11.0 -stdlib=libc++'
:debug:build DEVELOPER_DIR='/Library/Developer/CommandLineTools'
:debug:build LDFLAGS='-L/opt/local/lib -Wl,-headerpad_max_install_names -mmacosx-version-min=11.0'
:debug:build LIBRARY_PATH='/opt/local/lib'
:debug:build MACOSX_DEPLOYMENT_TARGET='11.0'
:debug:build PYTHON='/opt/local/bin/python2.7'
:debug:build SDKROOT='/Library/Developer/CommandLineTools/SDKs/MacOSX11.sdk'
:info:build Executing:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_editors_atom/atom/work/atom-1.37.0" && script/build --ci 
:debug:build system:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_editors_atom/atom/work/atom-1.37.0" && script/build --ci 
:info:build Node:	v16.5.0
:info:build Npm:	v7.20.0
:info:build Installing script dependencies
:info:build npm notice 
:info:build npm notice New patch version of npm available! 7.20.0 -> 7.20.1
:info:build npm notice Changelog: <https://github.com/npm/cli/releases/tag/v7.20.1>
:info:build npm notice Run `npm install -g npm@7.20.1` to update!
:info:build npm notice 
:info:build npm ERR! code ETIMEDOUT
:info:build npm ERR! syscall connect
:info:build npm ERR! errno ETIMEDOUT
:info:build npm ERR! network request to https://registry.npmjs.org/readable-stream/-/readable-stream-1.0.34.tgz failed, reason: connect ETIMEDOUT 104.16.22.35:443
:info:build npm ERR! network This is a problem related to network connectivity.
:info:build npm ERR! network In most cases you are behind a proxy or have bad network settings.
:info:build npm ERR! network 
:info:build npm ERR! network If you are behind a proxy, please make sure that the
:info:build npm ERR! network 'proxy' config is set properly.  See: 'npm help config'
:info:build npm ERR! A complete log of this run can be found in:
:info:build npm ERR!     /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_editors_atom/atom/work/.home/.npm/_logs/2021-07-24T19_31_40_746Z-debug.log
:info:build node:child_process:867
:info:build     throw err;
:info:build     ^
:info:build Error: Command failed: npm --loglevel=error ci
:info:build npm notice 
:info:build npm notice New patch version of npm available! 7.20.0 -> 7.20.1
:info:build npm notice Changelog: <https://github.com/npm/cli/releases/tag/v7.20.1>
:info:build npm notice Run `npm install -g npm@7.20.1` to update!
:info:build npm notice 
:info:build npm ERR! code ETIMEDOUT
:info:build npm ERR! syscall connect
:info:build npm ERR! errno ETIMEDOUT
:info:build npm ERR! network request to https://registry.npmjs.org/readable-stream/-/readable-stream-1.0.34.tgz failed, reason: connect ETIMEDOUT 104.16.22.35:443
:info:build npm ERR! network This is a problem related to network connectivity.
:info:build npm ERR! network In most cases you are behind a proxy or have bad network settings.
:info:build npm ERR! network 
:info:build npm ERR! network If you are behind a proxy, please make sure that the
:info:build npm ERR! network 'proxy' config is set properly.  See: 'npm help config'
:info:build npm ERR! A complete log of this run can be found in:
:info:build npm ERR!     /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_editors_atom/atom/work/.home/.npm/_logs/2021-07-24T19_31_40_746Z-debug.log
:info:build     at checkExecSyncError (node:child_process:826:11)
:info:build     at Object.execFileSync (node:child_process:864:15)
:info:build     at module.exports (/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_editors_atom/atom/work/atom-atom-687a9c7/script/lib/install-script-dependencies.js:9:16)
:info:build     at Object.<anonymous> (/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_editors_atom/atom/work/atom-atom-687a9c7/script/bootstrap:37:1)
:info:build     at Module._compile (node:internal/modules/cjs/loader:1095:14)
:info:build     at Object.Module._extensions..js (node:internal/modules/cjs/loader:1124:10)
:info:build     at Module.load (node:internal/modules/cjs/loader:975:32)
:info:build     at Function.Module._load (node:internal/modules/cjs/loader:816:12)
:info:build     at Module.require (node:internal/modules/cjs/loader:999:19)
:info:build     at require (node:internal/modules/cjs/helpers:93:18) {
:info:build   status: 1,
:info:build   signal: null,
:info:build   output: [
:info:build     null,
:info:build     Buffer(0) [Uint8Array] [],
:info:build     Buffer(1007) [Uint8Array] [
:info:build       110, 112, 109,  32, 110, 111, 116, 105,  99, 101,  32,  10,
:info:build       110, 112, 109,  32, 110, 111, 116, 105,  99, 101,  32,  78,
:info:build       101, 119,  32, 112,  97, 116,  99, 104,  32, 118, 101, 114,
:info:build       115, 105, 111, 110,  32, 111, 102,  32, 110, 112, 109,  32,
:info:build        97, 118,  97, 105, 108,  97,  98, 108, 101,  33,  32,  55,
:info:build        46,  50,  48,  46,  48,  32,  45,  62,  32,  55,  46,  50,
:info:build        48,  46,  49,  10, 110, 112, 109,  32, 110, 111, 116, 105,
:info:build        99, 101,  32,  67, 104,  97, 110, 103, 101, 108, 111, 103,
:info:build        58,  32,  60, 104,
:info:build       ... 907 more items
:info:build     ]
:info:build   ],
:info:build   pid: 4125,
:info:build   stdout: Buffer(0) [Uint8Array] [],
:info:build   stderr: Buffer(1007) [Uint8Array] [
:info:build     110, 112, 109,  32, 110, 111, 116, 105,  99, 101,  32,  10,
:info:build     110, 112, 109,  32, 110, 111, 116, 105,  99, 101,  32,  78,
:info:build     101, 119,  32, 112,  97, 116,  99, 104,  32, 118, 101, 114,
:info:build     115, 105, 111, 110,  32, 111, 102,  32, 110, 112, 109,  32,
:info:build      97, 118,  97, 105, 108,  97,  98, 108, 101,  33,  32,  55,
:info:build      46,  50,  48,  46,  48,  32,  45,  62,  32,  55,  46,  50,
:info:build      48,  46,  49,  10, 110, 112, 109,  32, 110, 111, 116, 105,
:info:build      99, 101,  32,  67, 104,  97, 110, 103, 101, 108, 111, 103,
:info:build      58,  32,  60, 104,
:info:build     ... 907 more items
:info:build   ]
:info:build }
:info:build Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_editors_atom/atom/work/atom-1.37.0" && script/build --ci 
:info:build Exit code: 1
:error:build Failed to build atom: command execution failed
:debug:build Error code: CHILDSTATUS 4122 1
:debug:build Backtrace: command execution failed
:debug:build     while executing
:debug:build "system {*}$notty {*}$callback {*}$nice $fullcmdstring"
:debug:build     invoked from within
:debug:build "command_exec -callback portprogress::target_progress_callback build"
:debug:build     (procedure "portbuild::build_main" line 8)
:debug:build     invoked from within
:debug:build "$procedure $targetname"
:error:build See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_editors_atom/atom/main.log for details.

Any ideas/suggestions? :)

OSX: 11.3.1
port: 2.7.1
npm: 7.20.1

[ryandesign (Ryan Carsten Schmidt)]

atom in MacPorts has no maintainer so if you or anyone would like to help figure out why it's not working, please do.

It does build and run for me on High Sierra bug I have not tested on Big Sur. The build failed on Big Sur on our automated build system.

atom in MacPorts is outdated: we have version 1.37 while upstream has 1.57. There is a comment in the port saying versions newer than 1.37 require npm6 or later, which was apparently a problem for some reason, in addition to other issues.

Things may be complicated by the fact that atom builds using npm and npm has a different philosophy for handling dependencies than MacPorts does. There has been recent talk of "javascript" and "npm" portgroups being considered that might help.

[tifrel (Till)]

Well that's a bummer. I am sorry I cannot guarantee to find the time, but as I just got my new machine and found a few pain points while setting up, I may just be tempted to write a portfile or two. However, I would start out with a less difficult project, e.g. MiniForge. Two questions though: Is there a) a Discord or something like that to get in touch with other port maintainers in case I have questions and b) do you have official guidelines somewhere as to which ports are allowed, especially when it comes to licenses, but there might be other factors that I am not aware of?

[kencu (Ken)]

atom no longer exists as a port