Files
ray/src/ray
Stephanie Wang 4abafd7e62 Fix bug in ray.wait (#3445)
ray.wait depends on callbacks from the GCS to decide when an object has appeared in the cluster. The raylet crashes if a callback is received for a wait request that has already completed, but this actually can happen, depending on the order of calls. More precisely:

1. Objects A and B are put in the cluster.
2. Client calls ray.wait([A, B], num_returns=1).
3. Client subscribes to locations for A and B. Locations are cached for both, so callbacks are posted for each.
4. Callback for A fires. The wait completes and the request is removed.
5. Callback for B fires. The wait request no longer exists and raylet crashes.
2018-12-01 19:40:33 -08:00
..
2018-10-26 13:36:58 -07:00
2018-11-19 17:01:18 -08:00
2018-10-26 13:36:58 -07:00
2018-08-30 22:42:49 -07:00
2018-10-26 13:36:58 -07:00
2018-10-26 13:36:58 -07:00