🪲 BUG-#141: Fix fork multiprocessing on macOS with OBJC safety flag#165
Merged
FernandoCelmer merged 1 commit intodevelopfrom Apr 7, 2026
Merged
🪲 BUG-#141: Fix fork multiprocessing on macOS with OBJC safety flag#165FernandoCelmer merged 1 commit intodevelopfrom
FernandoCelmer merged 1 commit intodevelopfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
dotflow/core/workflow.py— SetOBJC_DISABLE_INITIALIZE_FORK_SAFETY=YESon macOS before using fork contextMotivation and Context
On macOS,
fork()is deprecated in the presence of threads and can cause crashes with CoreFoundation. Python 3.12+ warns about this. Usingspawnorforkserveris not possible becauseActionobjects are not picklable.The
OBJC_DISABLE_INITIALIZE_FORK_SAFETYenv var is Apple's official workaround to allow safe forking.Closes #141
Types of changes
Checklist