adamoffat (Adam Moffat)
- Login: adamoffat
- Registered on: 12/17/2025
- Last sign in: 06/17/2026
Issues
| open | closed | Total | |
|---|---|---|---|
| Assigned issues | 0 | 0 | 0 |
| Reported issues | 0 | 1 | 1 |
Activity
06/17/2026
-
08:57 PM Ruby Bug #21790: `Socket.getaddrinfo` hangs after `fork()` on macOS 26.1 (Tahoe) for IPv4-only hosts
- Update: Apple has formally declined to fix this (still present in macOS 27 beta).
I'm the reporter of the underlying Apple Feedback (FB21364061). Posting a status update since this issue is the canonical landing spot for anyone hittin...
12/18/2025
-
- Ah my earlier Python script had a bug.
My initial Python test incorrectly reported success. The script used `os.WEXITSTATUS()` to check the child's exit status, but this function only works for processes that exit normally. When a pro... -
- mame (Yusuke Endoh) wrote in #note-3:
> Thank you for the report.
> ...
Ah yes, sorry I should have clarified this in my post. I tested this in 3.2.6 but it manifests differently in that version.
When I ran the same reproduction script ...
12/17/2025
-
- I saw that this was added in 3.4.0: https://github.com/ruby/ruby/pull/10864
Seen here: (https://github.com/ruby/ruby/releases/tag/v3_4_0_preview2)
But I also tested this using 3.4.1 and it was still an issue. -
- To confirm: MacOS Sequoia also did not have this issue.
-
- Ruby's `Socket.getaddrinfo` hangs indefinitely in forked child processes on macOS 26.1 (Tahoe) when resolving IPv4-only hostnames. This is a regression that does not occur on macOS 15.x (Sonoma) or earlier.
**Ruby version:**
ruby 3.3...