Skip to content

Conversation

@midnight-wonderer
Copy link
Contributor

@midnight-wonderer midnight-wonderer commented Feb 14, 2025

Process.fork works correctly only once on certain QEMU/Ruby combinations, AFAIK.
The detection logic is added to sidestep the issue.

See #495 for the discussion.

@casperisfine
Copy link
Contributor

Only saw this now. I think it makes sense, I'd maybe write the code a bit differently though.

I'll study this idea.

casperisfine pushed a commit that referenced this pull request May 14, 2025
When building cross platform images with Docker, QEMU is often used under the hood and can have a bug that cause forked processes to deadlock. Before spawning workers we test for that bug. Fix: #495 Closes: #497 Co-Authored-By: Sarun Rattanasiri <midnight_w@gmx.tw>
casperisfine pushed a commit that referenced this pull request May 14, 2025
When building cross platform images with Docker, QEMU is often used under the hood and can have a bug that cause forked processes to deadlock. Before spawning workers we test for that bug. Fix: #495 Closes: #497 Co-Authored-By: Sarun Rattanasiri <midnight_w@gmx.tw>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

2 participants