Pierre Chapuis

In case you're interested, [I forked it and fixed it](https://github.com/catwell/mercury). I might decide to port it to Lua 5.3 as well sometime. I don't think @nrk intends to keep maintaining...

See [here](https://github.com/Etiene/luatakeme/pull/7). @nrk, I concur: how can we help? Also, how do your branches work? What is the difference between version-2.0 and master? Apparently master is version 3 but it...

(related: https://github.com/catwell/fakeredis/commit/a076588b87f24b1f5982c01e3265074a81b95db0#diff-cb226e1732729d7a5e8f0508ee7de92eR127)

For reference this fork apparently solves the problem for `spawn`: https://github.com/jhawthorn/posix-spawn/commit/529e2147f6e900507efea2559562bd262d816ec3 @jhawthorn Is that patch used at GitHub? If so is there any chance to upstream it? Regarding `popen4` it...

OK, thanks for the answer! I was still using it in part because I prefer its API - see [this blobpost](https://www.johnnunemaker.com/resilience-in-ruby-shell-commands/) by @jnunemaker for an example - but I can...

@midnight-wonderer I only suggest the gem should be deprecated if the maintainers don't use it anymore and don't intend to fix its bugs. Process.spawn is not what changed, it's IO...

Not entirely sure that is what he was referring to but Ruby now uses vfork when it can. Like I said that wasn't my reason for using this gem anyway.

Yes, that is probably what I will do now. In the meantime we monkey patched this gem to have it work on Ruby 3 since we wanted to avoid such...

That's very likely. I never used LMDB on a BE machine, nor do I have one. I am not actively maintaining this code, it's more a toy than anything else...

That's very likely. I never used LMDB on a BE machine, nor do I have one. I am not actively maintaining this code, it's more a toy than anything else...