Open drpepper opened 10 years ago
That isn't hanging, it's still connected and getting updates live.
Hmm, what could be changed to make that more obvious?
Unfortunately, I don't have time to work on this right now, but when I do I'll investigate
--verbose
mode.
Oh, ok. So it's npmd --sync
that we're supposed to be running in the background? Just updating the README would help to understand that. Another possibility would be to add a flag like --sync-once
that quits when it reaches 100% .
Another idea: when it reaches 100% you could write something like "Waiting for more updates..." on the next line.
Ah, got it. Okay, I've fixed the readme. thanks for your feedback, this has been a really hard "bug" to diagnose, I've answered lots of issues where someone has gotten the wrong impression about this feature. I think we got it now though!
npmd sync
(without -- also works) recovers if it crashes, so you can just stop it when you get to 100 and use the data that is already in the database.
I try installing npmd every month or so, and the npmd sync
step never seems to work/finish. Here's what it does today:
$ which npmd
/Users/zeke/.nvm/v0.10.26/bin/npmd
$ npmd -v
0.20.2
$ npmd sync
connected to npm registry!!!
|....:....|....:....|....:....|....:....|....:....| 0.0%
^ twenty minutes later, still at 0.0%
some npm stuff has changed because of the recent changes to how the npm registry works. I just pushed 0.20.3 can you try that?
hopefully I'll get time to work on this again soon!
So far so good. Thanks!
awesome!
When I run --sync, it hangs at 100%
And when I run
--sync --verbose
:I'm on OSX 10.9.1, node v0.10.22.