Make the check for the availability of fork() more precise #1630
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
So that it also triggers for TruffleRuby which currently doesn't support
fork
.Methods can have
respond_to?
=>false
if they are "unimplemented"/"not supported on this platform", but yet be actually defined and be part ofModule#methods
.Those methods usually just raise a NotImplementedError like
fork is not available (NotImplementedError)
.This is what MRI does and it's also supported in at least JRuby, Rubinius and TruffleRuby.
The error message is made generic and now looks like this:
Related: I wonder, why does the cluster mode of Puma needs
fork
and not justspawn
?