News for hackers. Stuff that matters.
Re:Why Ruby App Servers Break on MacOS High Sierra by joshmn on Thursday October 19, 2017 @02:41AM (#15505901)
This issue has been addressed on ruby-head

https://github.com/ruby/ruby/commit/8b182a7f7d798ab6539518fb...

Re:Why Ruby App Servers Break on MacOS High Sierra by jasonmp85 on Thursday October 19, 2017 @12:07PM (#15509112)
Right; this article is almost a week old at this point and some progress has been made in addressing this. In particular, I found the characterization that other app servers are not taking action on this problem to be a lie in poor taste.

This kind of talking up of one's own product and saying "we're first; we're best!" rather than working within the ecosystem to help fix a shared issue confirms my feeling that Passenger is a bit of an outlier in the Ruby community.

Re:Why Ruby App Servers Break on MacOS High Sierra by akvadrako on Thursday October 19, 2017 @07:15AM (#15506929)
It's been addressed, but it's a hack. To be safe, apps must stop all other threads before forking.

The only correct fix I can see is to have pre- and post- fork hooks in every library, which make that guarantee.

Re:Why Ruby App Servers Break on MacOS High Sierra by nateberkopec on Thursday October 19, 2017 @08:53AM (#15507429)
In Puma, we emit a warning if we detect any additional threads running prior to fork.