You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
edoakes opened this issue
Apr 24, 2025
· 0 comments
Assignees
Labels
bugSomething that is supposed to be working; but isn'tcoreIssues that should be addressed in Ray Corejira-coreP1Issue that should be fixed within a few weeks
When setting working_dir and py_modules to the same URI within the same runtime_env, only one of them will be GC'd. I added logs in the runtime_env agent, and it appears to call the deletion callback twice on ("py_modules", URI) instead of once on ("py_modules", URI) and once on ("working_dir", URI) as expected.
I haven't dug too deep yet, but it appears to be caused by the fact that this dictionary is keyed on URI only, not the (option, URI) tuple.
Versions / Dependencies
Master
Reproduction script
See the comment on test_runtime_env_working_dir_3::TestGC::test_actor_level_gc added here: #52553
The text was updated successfully, but these errors were encountered:
edoakes
added
bug
Something that is supposed to be working; but isn't
core
Issues that should be addressed in Ray Core
P1
Issue that should be fixed within a few weeks
labels
Apr 24, 2025
bugSomething that is supposed to be working; but isn'tcoreIssues that should be addressed in Ray Corejira-coreP1Issue that should be fixed within a few weeks
What happened + What you expected to happen
When setting
working_dir
andpy_modules
to the same URI within the same runtime_env, only one of them will be GC'd. I added logs in the runtime_env agent, and it appears to call the deletion callback twice on("py_modules", URI)
instead of once on("py_modules", URI)
and once on("working_dir", URI)
as expected.I haven't dug too deep yet, but it appears to be caused by the fact that this dictionary is keyed on URI only, not the
(option, URI)
tuple.Versions / Dependencies
Master
Reproduction script
See the comment on
test_runtime_env_working_dir_3::TestGC::test_actor_level_gc
added here: #52553The text was updated successfully, but these errors were encountered: