Comments (10)
joshaber
commented on August 15, 2024
Oh gosh, what new npm hell is this.
from github.
joshaber
commented on August 15, 2024
So if you remove pathwatcher from the dependencies and run apm install, it will work. And then re-add pathwatcher, run apm install again, and it will again work.
I'm not sure why the initial install fails when pathwatcher is included 😢
from github.
thedaniel
commented on August 15, 2024
The same error occurs when using the new apm install atom/git method.
from github.
joshaber
commented on August 15, 2024
@thedaniel Could you see if #95 fixes it?
from github.
kuychaco
commented on August 15, 2024
Retried 'apm install atom/git' and am still getting errors 😕
Cloning https://github.com/atom/git.git ✓
Installing modules ✗
> [email protected] install /private/var/folders/3r/m5xlpjyd1t38_8yrvdssgw840000gn/T/atom-git-package-clone-116218-5907-rlmi16/node_modules/pathwatcher/node_modules/runas
> node-gyp rebuild
CXX(target) Release/obj.target/runas/src/main.o
> [email protected] postinstall /private/var/folders/3r/m5xlpjyd1t38_8yrvdssgw840000gn/T/atom-git-package-clone-116218-5907-rlmi16/node_modules/flow-bin/node_modules/bin-wrapper/node_modules/bin-check/node_modules/spawn-sync
> node postinstall
Installing native dependencies (this may take up to a minute)
> [email protected] postinstall /private/var/folders/3r/m5xlpjyd1t38_8yrvdssgw840000gn/T/atom-git-package-clone-116218-5907-rlmi16/node_modules/flow-bin
> node lib/install.js
> [email protected] postinstall /private/var/folders/3r/m5xlpjyd1t38_8yrvdssgw840000gn/T/atom-git-package-clone-116218-5907-rlmi16/node_modules/standard/node_modules/standard-format/node_modules/esformatter/node_modules/npm-run/node_modules/spawn-sync
> node postinstall
Installing native dependencies (this may take up to a minute)
npm WARN engine [email protected]: wanted: {"node":"~0.8.x"} (current: {"node":"0.10.40","npm":"2.13.3"})
In file included from ../src/main.cc:1:
../../../../nan/nan.h:200:10: fatal error: 'nan_new.h' file not found
#include "nan_new.h" // NOLINT(build/include)
^
1 error generated.
make: *** [Release/obj.target/runas/src/main.o] Error 1
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/Applications/Atom.app/Contents/Resources/app/apm/node_modules/npm/node_modules/node-gyp/lib/build.js:269:23)
gyp ERR! stack at ChildProcess.emit (events.js:98:17)
gyp ERR! stack at Process.ChildProcess._handle.onexit (child_process.js:820:12)
gyp ERR! System Darwin 15.3.0
gyp ERR! command "node" "/Applications/Atom.app/Contents/Resources/app/apm/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /private/var/folders/3r/m5xlpjyd1t38_8yrvdssgw840000gn/T/atom-git-package-clone-116218-5907-rlmi16/node_modules/pathwatcher/node_modules/runas
gyp ERR! node -v v0.10.40
gyp ERR! node-gyp -v v2.0.2
gyp ERR! not ok
npm WARN deprecated [email protected]: graceful-fs version 3 and before will fail on newer node releases. Please update to graceful-fs@^4.0.0 as soon as possible.
npm WARN deprecated [email protected]: lodash@<3.0.0 is no longer maintained. Upgrade to lodash@^4.0.0.
npm WARN deprecated [email protected]: graceful-fs version 3 and before will fail on newer node releases. Please update to graceful-fs@^4.0.0 as soon as possible.
✔ flow binary test passed successfully
npm WARN engine [email protected]: wanted: {"node":">=0.12"} (current: {"node":"0.10.40","npm":"2.13.3"})
npm WARN engine [email protected]: wanted: {"node":">=0.12"} (current: {"node":"0.10.40","npm":"2.13.3"})
npm WARN engine [email protected]: wanted: {"node":">=0.12"} (current: {"node":"0.10.40","npm":"2.13.3"})
npm WARN engine [email protected]: wanted: {"node":">=0.12"} (current: {"node":"0.10.40","npm":"2.13.3"})
npm WARN engine [email protected]: wanted: {"node":">=0.12"} (current: {"node":"0.10.40","npm":"2.13.3"})
npm WARN engine [email protected]: wanted: {"node":">=0.12"} (current: {"node":"0.10.40","npm":"2.13.3"})
npm ERR! Darwin 15.3.0
npm ERR! argv "/Applications/Atom.app/Contents/Resources/app/apm/bin/node" "/Applications/Atom.app/Contents/Resources/app/apm/node_modules/npm/bin/npm-cli.js" "--globalconfig" "/Users/kuychaco/.atom/.apm/.apmrc" "--userconfig" "/Users/kuychaco/.atom/.apmrc" "install" "--target=0.36.8" "--arch=x64"
npm ERR! node v0.10.40
npm ERR! npm v2.13.3
npm ERR! code ELIFECYCLE
npm ERR! [email protected] install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script 'node-gyp rebuild'.
npm ERR! This is most likely a problem with the runas package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get their info via:
npm ERR! npm owner ls runas
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /private/var/folders/3r/m5xlpjyd1t38_8yrvdssgw840000gn/T/atom-git-package-clone-116218-5907-rlmi16/npm-debug.log
version info:
Atom : 1.8.0-dev-292233f
Electron: 0.36.8
Chrome : 47.0.2526.110
Node : 5.1.1
from github.
BinaryMuse
commented on August 15, 2024
So as I was debugging a different issue I came across this fun case (worked the first time, failed the second):
mtilley@deep-thought ~/github/apm on master $ GIT_TERMINAL_PROMPT=0 ./bin/apm install atom/git
Cloning https://github.com/atom/git.git ✗
Cloning git+ssh://[email protected]/atom/git.git ✓
Installing modules ✓
Moving git to /Users/mtilley/.atom/packages/git ✓
mtilley@deep-thought ~/github/apm on master $ GIT_TERMINAL_PROMPT=0 ./bin/apm install [email protected]:atom/git.git
Cloning git+ssh://[email protected]/atom/git.git ✓
Installing modules ✗
> [email protected] install /private/var/folders/tx/lmcxjv9n73g0hy0zxf27y_rc0000gn/T/atom-git-package-clone-116218-35566-8novdx/node_modules/pathwatcher/node_modules/runas
> node-gyp rebuild
CXX(target) Release/obj.target/runas/src/main.o
> [email protected] postinstall /private/var/folders/tx/lmcxjv9n73g0hy0zxf27y_rc0000gn/T/atom-git-package-clone-116218-35566-8novdx/node_modules/flow-bin/node_modules/bin-wrapper/node_modules/bin-check/node_modules/spawn-sync
> node postinstall
Installing native dependencies (this may take up to a minute)
> [email protected] postinstall /private/var/folders/tx/lmcxjv9n73g0hy0zxf27y_rc0000gn/T/atom-git-package-clone-116218-35566-8novdx/node_modules/flow-bin
> node lib/install.js
> [email protected] postinstall /private/var/folders/tx/lmcxjv9n73g0hy0zxf27y_rc0000gn/T/atom-git-package-clone-116218-35566-8novdx/node_modules/standard/node_modules/standard-format/node_modules/esformatter/node_modules/npm-run/node_modules/spawn-sync
> node postinstall
Installing native dependencies (this may take up to a minute)
npm WARN engine [email protected]: wanted: {"node":"~0.8.x"} (current: {"node":"0.10.40","npm":"2.13.3"})
In file included from ../src/main.cc:1:
../../../../nan/nan.h:194:11: fatal error: 'nan_maybe_43_inl.h' file not found
# include "nan_maybe_43_inl.h" // NOLINT(build/include)
^
1 error generated.
make: *** [Release/obj.target/runas/src/main.o] Error 1
from github.
joshaber
commented on August 15, 2024
@kuychaco @BinaryMuse Could you both try running apm rebuild-module-cache and then apm install again?
from github.
kuychaco
commented on August 15, 2024
So that worked and I got excited, but that excitement was short-lived. When I tried again I got a failure. Seems like it'll sporadically work, but for the most part fail.
@BinaryMuse suggested that we try deleting the module cache and that worked consistently. To build up confidence we did this several times and got 40 consecutive successful installations (by running while true; do rm -rf ~/.atom/.apm && apm install atom/git; done and letting that go for a while)
Then we tried rebuilding the module cache and then installing in a loop (while true; do; apm rebuild-module-cache && apm install atom/git; done) and got 10 consecutive failures.
from github.
joshaber
commented on August 15, 2024
This is a more widespread problem. Tracking it in atom/atom-keymap#118.
from github.
iolsen
commented on August 15, 2024
Fixed with npm upgrade.
from github.
Related Issues (20)
- .
- knknkn
- Default branch name of new git repositories is `master`, despite init.defaultbranch settings HOT 1
- Cannot stage changes, make commits, make branches
- Can't open tlauncher
- Cannot see autocomplete in Search Input
- [email protected] HOT 1
- Credit HOT 1
- Credit HOT 1
- Can't push to organization repo HOT 3
- Port these views to VSCode? HOT 2
- Startup & Hydrogen issues HOT 3
- Can't push from Atom to Github
- Profiles
- ## Environment
- Github Desktop deleted all files in folder (pls help i spent so much time on these projects)
- Jusc HOT 1
- unstaged changes do not show up in git panel HOT 3
- I'm HOT 1
- Not
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from github.