Alex Wu
Alex Wu
Hmmm I feel like this is actually the behavior we want in master? I feel like when we cut release branches that's when the default should change.
> Most people ... Yeah I agree that the behavior for most people should be latest, but they will be using a release wheel, and I think that's where the...
@can-anyscale do you have any suggestions about how we should solve this problem? let me know if you need any context about this problem.
I think it would actually mean that it should point to the specific version the wheel was built with. E.g. a wheel built today should always point to the docker...
``` So here's my proposal, we split this REP into two separate REPs: Introducing the label mechanism for nodes. This should cover: The proposed API for ray start, scheduling_strategy. Ray...
cc @iycheng who has thought a lot about related topics (durable/named objects, ownership transfer to GCS, etc)
In the absence of error messages i'm assuming this is a race condition where that `ray status` is happening before the autoscaler is fully up. I assume this should get...
I can probably take a look at this later this week/next week if no one gets to it before then.
@pcmoritz are you running `ray up` from a nightly wheel or from a released wheel?
I chatted with @can-anyscale about this and he should provide his opinion. Generally, I think there's 2 scenarios we should consider. 1. Running `ray up` where my laptop has a...