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
npm view in stubbed-out npm-world hangs #8
Comments
Thanks for the report, a few other folks saw this yesterday at the NodeSummit workshop, so it isn't a problem with your setup. We'll have to look into it. |
After it hangs for a minute, I get an error. Here is the npm-debug.log:
|
Probably same or neary problem. $ npm view howtonpm Error Message below: npm ERR! Darwin 14.1.0
npm ERR! argv "node" "/Users/tgfjt/.nodebrew/current/bin/npm" "view" "howtonpm"
npm ERR! node v0.10.36
npm ERR! npm v2.7.3
npm ERR! code ECONNRESET
npm ERR! network tunneling socket could not be established, cause=connect ECONNREFUSED
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! Please include the following file with any support request:
npm ERR! /Users/tgfjt/workspace/howtonpm/solutions/npm-debug.log Here npm-debug.log:
My Env is:
iojs@v1.6.2
|
The way I see it, the workshopper sort of maintains state (as in, a running pseudo-registry) across various steps for a given challenge, and expects them in the exact order, then drops the registry process. This is very brittle, as so many of our NodeSchool Paris attendees, and the people in this thread, can attest. I would suggest maintaining that kind of state until either the next exercise selection (not just launching the menu: actually selecting an exercise), or a loooong timeout (say, an hour). Any exercise start procedure would drop the existing mock if need be, and start their own. This is especially important as currently, many steps implicitly require exercises are done in full sequential order, with no holes or anything, for suggested commands to work. The best way, from a user perspective (not quite from a workshopper author / maintenance / coupling perspective, though), would be a single registry mock that can handle all the challenges, so users don't have to worry about a suggested CLI usage becoming a hang-threat a couple steps down the line, and also for non-linear challenge usage. |
I've also run into this problem. It hangs, but within a few minutes returns an error:
The pertinent
A very similar series of error messages is returned when using |
I think I'm in the same boat as many others here. Getting errors when trying to publish as an example. Is there any workarounds suggested? Should i start from scratch again? |
same problem, I am using Cloud 9 IDE. Please help |
Here's a solution that worked for me:
That worked for me. |
The problem is that for some reason, the local registry stops working, so to trigger it to start working again, one has to go back to the Login step. |
Not sure if this is a problem with my setup or if it's a problem with how-to-npm, but when I do
npm view my-package-name
as instructed by the verification message in challenge 07 (Publish), it just hangs. Outside the directory I created for the how-to-npm workshopper,npm view whatever
works just fine, returning data about packages that exist or an 404 error for packages that don't exist.The text was updated successfully, but these errors were encountered: