Is lmdb-store supported on windows 7?

[dattasid]

Getting this error:

> parcel.cmd build index.html
Error: The specified procedure could not be found.
\\?\C:\Program Files\node-v13.14.0\node_modules\lmdb-store\build\Release\lmdb-store.node
    at Object.Module._extensions..node (internal/modules/cjs/loader.js:1168:18)
    at Module.load (internal/modules/cjs/loader.js:982:32)
    at Function.Module._load (internal/modules/cjs/loader.js:875:14)
    at Module.require (internal/modules/cjs/loader.js:1022:19)
    at require (C:\Program Files\node-v13.14.0\node_modules\parcel\node_modules\v8-compile-cache\v8-compile-cache.js:159
:20)
    at load (C:\Program Files\node-v13.14.0\node_modules\lmdb-store\node_modules\node-gyp-build\index.js:21:10)
    at Object.<anonymous> (C:\Program Files\node-v13.14.0\node_modules\lmdb-store\index.js:7:49)
    at Module._compile (C:\Program Files\node-v13.14.0\node_modules\parcel\node_modules\v8-compile-cache\v8-compile-cach
e.js:192:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1138:10)
    at Module.load (internal/modules/cjs/loader.js:982:32)

lmdb-store.node is a dll ? So wither the DLL cannot make a necessary system call, or wrong function in the dll is being called .

[kriszyp]

I thought even Windows 7 itself wasn't supported on Windows 7 (hasn't been for almost two years). Node v13 is also an old unsupported version, not sure if that could potentially be an issue as well. I'd be willing to take a look at seeing if I could fix it, but I have no idea where I could even find a Win7 computer, all my old computers have long since been upgraded or thrown away, and I can't find any win7 VMs on CI services either.

[kriszyp]

I was able to setup a Windows 7 VM, and fix this issue. It should be fixed in the latest release.

[dattasid]

🙏👍 . Thank you for spending time on this. Can I have the commit number?

…

On Sun, Nov 14, 2021, 9:05 PM Kris Zyp ***@***.***> wrote: I was able to setup a Windows 7 VM, and fix this issue. It should be fixed in the latest release. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#89 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADTFFCBC7NKV4RDSKOB637LUMCIJXANCNFSM5ESSQ5UQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[kriszyp]

Sure, it was fixed in 25885cb (removing the use of the Win32 setProcessMemoryPriority API, which was added in Windows 8). This fix should be available in v1.6.13 and higher.