We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently, to ensure fork safety when dealing with system resources, we add hand-baked getpid() tests in relevant APIs.
We could instead have a centralized after-fork facility such as:
AfterForkToken RegisterAtFork(std::function<void()> after_fork);
The returned token would have to be kept alive for as long as the after-fork callbacks are to be registered.
(a more elaborate overload with before-fork, after-fork-in-parent, after-fork-in-child callbacks could also be added if necessary)
Reporter: Antoine Pitrou / @pitrou Assignee: Antoine Pitrou / @pitrou
Note: This issue was originally created as ARROW-17975. Please see the migration documentation for further details.
The text was updated successfully, but these errors were encountered:
Antoine Pitrou / @pitrou: Issue resolved by pull request 14594 #14594
Sorry, something went wrong.
pitrou
No branches or pull requests
Currently, to ensure fork safety when dealing with system resources, we add hand-baked getpid() tests in relevant APIs.
We could instead have a centralized after-fork facility such as:
The returned token would have to be kept alive for as long as the after-fork callbacks are to be registered.
(a more elaborate overload with before-fork, after-fork-in-parent, after-fork-in-child callbacks could also be added if necessary)
Reporter: Antoine Pitrou / @pitrou
Assignee: Antoine Pitrou / @pitrou
Related issues:
PRs and other links:
Note: This issue was originally created as ARROW-17975. Please see the migration documentation for further details.
The text was updated successfully, but these errors were encountered: