Handle situation where a closed ractor results in an IOError

Author: azimux

CHANGELOG.md

@@ -1,3 +1,7 @@
+## [0.0.7] - 2026-06-06
+
+- Closed Ractor::Ports sometimes give IOError instead of Ractor::ClosedError so handle both
+
 ## [0.0.6] - 2026-06-06
 
 - Fix a bug where a closed port mysteriously breaks out of Kernel#loop

Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    ractorize (0.0.6)
+    ractorize (0.0.7)
 
 GEM
   remote: https://rubygems.org/
@@ -208,7 +208,7 @@ CHECKSUMS
   pry-byebug (3.12.0) sha256=594e094ae8a8390a7ad4c7b36ae36e13304ed02664c67417d108dc5f7213d1b7
   psych (5.4.0) sha256=14f72d69a611af663d7d70e4a7b67d9eb1f3ae9f8d916b478961d5a0075ba5b7
   racc (1.8.1) sha256=4a7f6929691dbec8b5209a0b373bc2614882b55fc5d2e447a21aaa691303d62f
-  ractorize (0.0.6)
+  ractorize (0.0.7)
   rainbow (3.1.1) sha256=039491aa3a89f42efa1d6dec2fc4e62ede96eb6acd95e52f1ad581182b79bc6a
   rake (13.4.2) sha256=cb825b2bd5f1f8e91ca37bddb4b9aaf345551b4731da62949be002fa89283701
   rb-fsevent (0.11.2) sha256=43900b972e7301d6570f64b850a5aa67833ee7d87b458ee92805d56b7318aefe

src/ractorize.rb

@@ -275,6 +275,12 @@ def extract_args(port_like)
 
           begin
             return_port.send(value)
+          rescue IOError => e
+            # Unclear why this sometimes manifests as this error instead of ClosedError but
+            # need to handle them both.
+            # :nocov:
+            raise unless e.message == "closed stream"
+            # :nocov:
           rescue Ractor::ClosedError
             # Whoa... this error inherits from StopIteration and will kill the loop!!!
             # Nothing really to do here but keep the loop going and handle other

version.rb

@@ -1,4 +1,4 @@
 module Ractorize
-  VERSION = "0.0.6".freeze
+  VERSION = "0.0.7".freeze
   MINIMUM_RUBY_VERSION = ">= 4.0.0".freeze
 end