-
Notifications
You must be signed in to change notification settings - Fork 6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Core] AttributeError: 'Worker' object has no attribute 'import_thread' #44031
Labels
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
size-small
stability
Comments
@scv119 import_thread in function_manager should be removed? |
8 tasks
Is the fix for this in 2.10? It looks like it might have merged in time (Mar 15, vs. Mar 21 release date). I'm running into this while trying to find a repro for #44438, with this script: import ray
import numpy as np
ray.init()
@ray.remote
def _create_data():
return np.zeros((10000, 100))
@ray.remote
def _mul(data):
return np.multiply(data, data)
@ray.remote
def _test(data):
ray.get(_mul.remote(data))
@ray.remote
def _toplevel():
tasks = {i: _test.remote(_create_data.remote()) for i in range(0, 100)}
return tasks
results = ray.get(_toplevel.remote()) If I run it a few times in a row I'll eventually get:
|
Answered my own question - that fix did not make it into the 2.10 release |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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
size-small
stability
What happened + What you expected to happen
The import thread has been removed #36293, and it appears that the code within function_manager should also be deleted.
Versions / Dependencies
ray2.6.1
Reproduction script
None
Issue Severity
Medium: It is a significant difficulty but I can work around it.
The text was updated successfully, but these errors were encountered: