Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dependency superagent-use fails installation. #1

Closed
Alexintosh opened this issue Jan 19, 2018 · 7 comments
Closed

Dependency superagent-use fails installation. #1

Alexintosh opened this issue Jan 19, 2018 · 7 comments

Comments

@Alexintosh
Copy link

Looks like the shesek/superagent-use it's breaking the installation process.

@shesek
Copy link
Contributor

shesek commented Jan 20, 2018

What error are you getting?

@shesek
Copy link
Contributor

shesek commented Jan 23, 2018

@Alexintosh were you able to resolve this?

@Alexintosh
Copy link
Author

I couldn't, this is the full log:

0 info it worked if it ends with ok
1 verbose cli [ '/Users/alexintosh/.nvm/versions/node/v8.1.2/bin/node',
1 verbose cli   '/Users/alexintosh/.nvm/versions/node/v8.1.2/bin/npm',
1 verbose cli   'install',
1 verbose cli   'lightning-charge-client' ]
2 info using [email protected]
3 info using [email protected]
4 verbose npm-session ad9f41bd1da4b4a9
5 silly install loadCurrentTree
6 silly install readLocalPackageData
7 http fetch GET 304 https://registry.npmjs.org/lightning-charge-client 408ms (from cache)
8 silly pacote tag manifest for lightning-charge-client@latest fetched in 473ms
9 silly install loadIdealTree
10 silly install cloneCurrentTreeToIdealTree
11 silly install loadShrinkwrap
12 silly pacote git manifest for lightning-charge-client@git+https://github.com/Alexintosh/lightning-charge-client-js.git#14f6acbd1d10a57e708717c694ac66e7b46106e9 fetched in 483ms
13 silly install loadAllDepsIntoIdealTree
14 silly resolveWithNewModule [email protected] checking installable status
15 http fetch GET 304 https://registry.npmjs.org/superagent-baseuri 246ms (from cache)
16 silly pacote range manifest for superagent-baseuri@^0.1.1 fetched in 251ms
17 silly resolveWithNewModule [email protected] checking installable status
18 silly fetchPackageMetaData error for superagent-use@git://github.com/shesek/superagent-use.git#patch-1 Error while executing:
18 silly fetchPackageMetaData /usr/local/bin/git ls-remote -h -t git://github.com/shesek/superagent-use.git
18 silly fetchPackageMetaData
18 silly fetchPackageMetaData fatal: unable to connect to github.com:
18 silly fetchPackageMetaData github.com[0: 192.30.253.112]: errno=Operation timed out
18 silly fetchPackageMetaData github.com[1: 192.30.253.113]: errno=Operation timed out
18 silly fetchPackageMetaData
18 silly fetchPackageMetaData
18 silly fetchPackageMetaData exited with error code: 128
19 silly saveTree [email protected]
19 silly saveTree └─┬ [email protected]
19 silly saveTree   ├─┬ [email protected]
19 silly saveTree   │ └── [email protected]
19 silly saveTree   └─┬ [email protected]
19 silly saveTree     ├── [email protected]
19 silly saveTree     ├── [email protected]
19 silly saveTree     ├─┬ [email protected]
19 silly saveTree     │ └── [email protected]
19 silly saveTree     ├── [email protected]
19 silly saveTree     ├─┬ [email protected]
19 silly saveTree     │ ├── [email protected]
19 silly saveTree     │ ├─┬ [email protected]
19 silly saveTree     │ │ └── [email protected]
19 silly saveTree     │ └─┬ [email protected]
19 silly saveTree     │   └── [email protected]
19 silly saveTree     ├── [email protected]
19 silly saveTree     ├── [email protected]
19 silly saveTree     ├── [email protected]
19 silly saveTree     ├── [email protected]
19 silly saveTree     └─┬ [email protected]
19 silly saveTree       ├── [email protected]
19 silly saveTree       ├── [email protected]
19 silly saveTree       ├── [email protected]
19 silly saveTree       ├── [email protected]
19 silly saveTree       ├── [email protected]
19 silly saveTree       ├── [email protected]
19 silly saveTree       └── [email protected]
20 verbose stack Error: exited with error code: 128
20 verbose stack     at ChildProcess.onexit (/Users/alexintosh/.nvm/versions/node/v8.1.2/lib/node_modules/npm/node_modules/mississippi/node_modules/end-of-stream/index.js:39:36)
20 verbose stack     at emitTwo (events.js:125:13)
20 verbose stack     at ChildProcess.emit (events.js:213:7)
20 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:197:12)
21 verbose cwd /Users/alexintosh/Code/kairos/LIGHTNING/demo-app
22 verbose Darwin 16.7.0
23 verbose argv "/Users/alexintosh/.nvm/versions/node/v8.1.2/bin/node" "/Users/alexintosh/.nvm/versions/node/v8.1.2/bin/npm" "install" "lightning-charge-client"
24 verbose node v8.1.2
25 verbose npm  v5.6.0
26 error Error while executing:
26 error /usr/local/bin/git ls-remote -h -t git://github.com/shesek/superagent-use.git
26 error
26 error fatal: unable to connect to github.com:
26 error github.com[0: 192.30.253.112]: errno=Operation timed out
26 error github.com[1: 192.30.253.113]: errno=Operation timed out
26 error
26 error
26 error exited with error code: 128
27 verbose exit [ 1, true ]

@shesek
Copy link
Contributor

shesek commented Jan 24, 2018

@Alexintosh This appears to be an internet connectivity issue, your npm client is for some reason unable to pull code from github (but can pull from the npm registry, it seems).

The reason it tries to pull code from github is that superagent-baseuri depends on a modified copy of superagent-use that only exists on github and not on npm. I sent a PR to get these changes merged upstream, so that they'll be available from the npm registry directly.

Note that this doesn't explain why your client is unable to connect to github... if you can figure this out, you should be able to use lightning-charge-client-js as-is. But in any case, I'll keep you updated about getting these changes available on npm.

@Alexintosh
Copy link
Author

@shesek I can pull dependencies and code from whatever github repo besides git://github.com/shesek/superagent-use.git. It is an issue specifically to that repo, tried with different internet connection and different machine already.

@shesek
Copy link
Contributor

shesek commented Jan 27, 2018

Are you still experiencing this issue? I'm unable to reproduce this and haven't heard about anyone else running into this.

@Alexintosh
Copy link
Author

Hey @shesek thanks for asking again, looks like the issue solved itself somehow, now sure what happened tho. Wil close the issue, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants