@Mazyod Thank you for willing to help, but we already identified the root cause: the ray core layer is compiled with a protobuf not compatible with the newest protobuf (py). So until ray core upgrade the protobuf (cpp) we have to stick to the one < 3.20.x. It’s actually also broken in mac/linux as well.
We never pin or restrict protobuf version in ray/python/setup.py before and that’s why when you install ray, it’ll always try to fetch the newest version of protobuf and unfortunately, it’s not backward compatible right now. The version restrict has been added in this PR.