Bug #17676: Accessing ENV from Ractor raises IsolationError

• Status: Closed
• Assignee: ko1 (Koichi Sasada)
• Target version: -
• ruby -v: ruby 3.0.0p0 (2020-12-25 revision 95aff21468) [x86_64-linux]
• Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN, 3.0: UNKNOWN
• Tags: ractor

[delner (David Elner)]

Background

Accessing ENV variables from a Ractor will raise Ractor::IsolationError, as the Hash is non-shareable.

How to reproduce

ractor = Ractor.new do
 ENV['PATH']
end
 
ractor.take

Expectation and result

Ractor raises Ractor::IsolationError for ENV

Expect to be able to access ENV variables from Ractors without raising an error.

`block in <main>': can not access non-shareable objects in constant Object::ENV by non-main Ractor. (Ractor::IsolationError)

Additional Notes

Attempting to create a shareable copy of ENV currently fails:

Ractor.make_shareable(ENV, copy: true)
# TypeError: cannot freeze ENV
# from <internal:ractor>:812:in `freeze'

Suggested solutions

1. If ENV is a mutable hash, make a Ractor-compatible copy of ENV isolated to that Ractor.

[delner (David Elner)]

• Description updated (diff)

[hsbt (Hiroshi SHIBATA)]

• Tags set to ractor
• Status changed from Open to Assigned
• Assignee set to ko1 (Koichi Sasada)

[ko1 (Koichi Sasada)]

I agree ENV should be shareable.
It is in my task list, but not high priority.

[jeremyevans0 (Jeremy Evans)]

• Status changed from Assigned to Closed

This was fixed in 3aab870761ff0138ffd29e0a08b6cdf151e2acb4

[ivoanjo (Ivo Anjo)]

Thank you Jeremy! :)