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.

Sign up for GitHub

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

Jump to bottom

Wiring framework: resolve fork() vs. pool.execute() #9647

Open
Tracked by #5326
cody-littley opened this issue Nov 2, 2023 · 0 comments
Open
Tracked by #5326

Wiring framework: resolve fork() vs. pool.execute() #9647

cody-littley opened this issue Nov 2, 2023 · 0 comments
Assignees
@OlegMazurov @cody-littley
Labels
Platform Tickets pertaining to the platform

Comments

@cody-littley
Copy link
Contributor

@OlegMazurov has raised concerns over use of pool.execute(this) instead of fork(). We should investigate the impact of this difference, and make changes as necessary.
@cody-littley cody-littley added this to the v0.45 milestone Nov 2, 2023
@cody-littley cody-littley mentioned this issue Nov 20, 2023
Open
@poulok poulok removed this from the v0.45 milestone Feb 9, 2024
@poulok poulok added the Platform Tickets pertaining to the platform label Jun 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@OlegMazurov OlegMazurov

@cody-littley cody-littley

Labels
Platform Tickets pertaining to the platform
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@OlegMazurov @cody-littley @poulok