Decide on wait_for_workers implementation in client cluster object #798
Description
Should the dask-gateway client's GatewayCluster class implement wait_for_workers?
Its a question raised without knowing if its relevant or not. I understand it as it would enable the wait_for_workers command to get dask-gateway specific logic, such as asking the dask-gateway server directly about worker startus instead of asking the scheduler - but it could be better to just ask the scheduler directly as we do now -- because it will have the final say if a worker is ready or not anyhow right?
Action points
- Conclude if there is a benefit to implementing such function.
Context
- Observed issue: AttributeError: 'GatewayCluster' object has no attribute 'wait_for_workers' #782
- Change causing issue: Cluster wait distributed#6700
- Issue fix to not force having dask-gateway client's GatewayCluster class implement
wait_for_workers