Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Fix lockfile and undo `npm dedupe` #1010
Resolves #1008 (maybe? pending review!)
My theory is that this was caused by
$ npm ls flumeview-hashtable atomic-file firstname.lastname@example.org /home/christianbundy/src/ssbc/patchwork ├─┬ email@example.com │ └── firstname.lastname@example.org ├─┬ email@example.com │ └── firstname.lastname@example.org └─┬ email@example.com ├─┬ firstname.lastname@example.org │ ├─┬ email@example.com │ │ └── firstname.lastname@example.org deduped │ └─┬ email@example.com │ └── firstname.lastname@example.org ├─┬ email@example.com │ └── firstname.lastname@example.org └─┬ email@example.com └── firstname.lastname@example.org deduped
Sort of a bummer that we can't trust
This seems to fix the issue! :)
On the other hand, both those machines now consistently show the "Welcome, please enter your initial name & bio" modal when they start up. But the identity is the right one.
I need some serious shut-eye now. Will pick this up again tomorrow.
I saw that problem too, but after waiting for indexing and then restarting a few times it seems to be resolved now and I can't figure out how to reproduce it. I'm hoping it was a weird race condition while the flumeview-hashtable bug was fixing itself? I wish I knew, the Scuttlebutt stack can make for a very opaque debugging experience sometimes.
Nope, that's funky. I noticed the same thing a couple of weeks ago but ended up having a bunch of trouble reproducing it. I've reopened #935 so that it's on everyone's radar, thanks for validating my sanity!