Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is posix-spawn still maintained? #94

Open
tatethurston opened this issue Apr 3, 2024 · 1 comment
Open

Is posix-spawn still maintained? #94

tatethurston opened this issue Apr 3, 2024 · 1 comment

Comments

@tatethurston
Copy link

tatethurston commented Apr 3, 2024

It's my understanding that this gem is no longer maintained. I'm creating this issue to help others who are trying to understand the current maintenance posture or reporting new issues. If I'm incorrect, please let me know so I can close this issue.

The last commit was 4 years ago. The last closed issue was also 4 years ago.

Packages can become "complete" and not need code changes, but it looks like recent issues #91 and #93 have not received feedback from a maintainer, in addition to #90 from 2021.

Also, for folks using modern rubies, it's my understanding that since Ruby 2.2 it is no longer necessary to use POSIX:Spawn to get good fork performance. Also see luanzeba@00dac13.

@tatethurston tatethurston changed the title posix-spawn is no longer maintained Is posix-spawn still maintained? Apr 3, 2024
@luanzeba
Copy link

Just wanted to chime in here that we stopped using posix-spawn at GitHub for the reasons shared above. That being said, developers still enjoyed the interface provided by POSIX::Spawn::Child, so we kept it under a new namespace Progeny::Command.
It provides the same functionality while leveraging Ruby's native Process.spawn.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants