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
Currently, setting preSpawnProcessConfigurator requires pre-fork on Linux, meaning preSpawnProcessConfigurator can't be used to control the posix_spawn path.
...and then the configurator could be called for both the posix_spawn and fork/exec paths, without influencing which one is taken.
Bonus points if this could be applied to Darwin as well (removing the forkExec option), to make the PlatformOptions API interface a little more similar.
The text was updated successfully, but these errors were encountered:
Currently, setting
preSpawnProcessConfigurator
requires pre-fork on Linux, meaningpreSpawnProcessConfigurator
can't be used to control the posix_spawn path.On Linux, the signature is:
Could it instead become:
...and then the configurator could be called for both the posix_spawn and fork/exec paths, without influencing which one is taken.
Bonus points if this could be applied to Darwin as well (removing the forkExec option), to make the PlatformOptions API interface a little more similar.
The text was updated successfully, but these errors were encountered: