Philipp Moritz

Julia adds a suffix to the names of BLAS (they do it so that 32-bit and 64-bit BLAS routines don't get confused), a smililar patch could be used to fix...

@babyblue1334 Do you have a reproduction for the issue (e.g. a minimal example that reproduces this behavior)?

Thanks for the report, can you check if this is gone in Ray 1.9.2? This should have been fixed.

If it still happens in 1.9.2, can you post a reproduction, i.e. which script are you running?

@matthewdeng Do you know what prevents us from being compatible with a more recent PyArrow release?

Ah this is https://issues.apache.org/jira/browse/ARROW-10739 Well, I don't think we can close this bug until that's resolved then :) However **if we install pyarrow >= 7.0, manually**, I have now verified...

Thanks for reporting, I also recently ran into this. This should be fixed by https://github.com/ray-project/ray/pull/28684 :)

@EnjianGong Have you had a look at https://docs.ray.io/en/latest/ray-core/troubleshooting.html#visualizing-tasks-in-the-ray-timeline? It provides a timeline similar to your suggestion :)

I think we should do this: Leave this function alone and introduce a new one with the new behavior. Print a deprecation warning that suggests to use the new function...

This significantly improves the error message for me if there is a version conflict: ``` Failed to unpickle serialized exception -- original error message is: ray.exceptions.RayTaskError: ray::begin_task_run() (pid=589, ip=172.31.76.169) File...