Kris Zyp

Ok, I am a bit confused, as these are different errors, but more importantly, different packages. The first error looks like it is for lmdb-store (different package/repo) and the second...

But the package you referenced is lmdb-store. I don't think using `npm ls node-lmdb` will find lmdb-store, you need to type `npm ls lmdb-store`? And updating node-lmdb won't fix your...

Yes, lmdb-store is a dependency of parcel. [email protected] already includes a prebuild for linux-x64+node-v16 (you could verify it at node_modules/lmdb-store/prebuilds/linux-64/node-abi94.node). So the prebuild must somehow be failing to work on...

Github gives a 500 error when I try to transfer the issue, so I guess that won't work right now.

Well, I was just going to try to run the current lmdb-store test suite github action using your docker file. Another thing that would be a helpful for debugging would...

So I ran this github action, which I think should be a close resemblance of your docker configuration, but specifically building and testing lmdb-store: https://github.com/DoctorEvidence/lmdb-js/runs/4301924530?check_suite_focus=true The build succeeded and lmdb-store...

Ok, I also tried using `npm ci` instead of `npm i` in my github action, but still no luck in reproducing an error.

Thank you for putting together this benchmark. I took a look at these benchmarks to see what might be the bottlenecks. From what I can tell, it is actually less...

Yes, I get about a 20% speed up from using the keyIsUint32 keys instead of strings.

So I actually spent some time prototyping a function (in native/C) that could retrieve a range of entries using a start and end key. I thought this might provide a...