You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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.
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.
The text was updated successfully, but these errors were encountered: