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
For #3075, we restored the old non-spawn-based open3.rb for Windows users. That allows popen3 to continue working (as well as it did in 1.7) but it was not really a complete fix. The complete fix would be to get Kernel/Process.spawn working on Windows, so the stock open3.rb could be used.
This will take some effort, considering that there's no posix_spawn on Windows and we'll have to use win32 calls to do it. The code in MRI may be illustrative, but it's a lot to port right now.
Once completed, we should also restore the standard open3.rb rather than using our custom logic.
The text was updated successfully, but these errors were encountered:
Just ran into this on 9.1.2.0/Windows/jre8u45. I'm attempting to start a Python subprocess that will proxy requests from the rest of my ruby script, like so:
Open3.popen3('python','proxy.py') do |stdout, stderr, status, thread|
# todo: read logged proxy port number, start client
end
This is currently erroring with NotImplementedError: waitpid unsupported or native support failed to load; see http://wiki.jruby.org/Native-Libraries. Running with -Xnative.verbose=true logs Successfully loaded native POSIX impl. and no errors other than the one I mentioned.
For #3075, we restored the old non-spawn-based open3.rb for Windows users. That allows popen3 to continue working (as well as it did in 1.7) but it was not really a complete fix. The complete fix would be to get Kernel/Process.spawn working on Windows, so the stock open3.rb could be used.
This will take some effort, considering that there's no posix_spawn on Windows and we'll have to use win32 calls to do it. The code in MRI may be illustrative, but it's a lot to port right now.
Once completed, we should also restore the standard open3.rb rather than using our custom logic.
The text was updated successfully, but these errors were encountered: