Skip to content

fix(runtime): reject use after fork - #136

Merged
0x676e67 merged 14 commits into
mainfrom
demo/reject-forked-runtime-use-112
Jul 27, 2026
Merged

fix(runtime): reject use after fork#136
0x676e67 merged 14 commits into
mainfrom
demo/reject-forked-runtime-use-112

Conversation

@0x676e67

@0x676e67 0x676e67 commented Jul 16, 2026

Copy link
Copy Markdown
Collaborator

It’s worth noting that native macOS APIs also don’t allow process forking. Some of wreq’s internal system-proxy APIs don’t support it either.

@0x676e67 0x676e67 linked an issue Jul 16, 2026 that may be closed by this pull request
Base automatically changed from demo/safe-cookie-expiry-semantics-114 to main July 24, 2026 01:01
@0x676e67
0x676e67 merged commit ba76d7a into main Jul 27, 2026
10 checks passed
@0x676e67
0x676e67 deleted the demo/reject-forked-runtime-use-112 branch July 27, 2026 11:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Make the native runtime safe across Process.fork

1 participant