Closed NKcqx closed 1 year ago
This PR remove the original cross_silo_send_max_retries
argument in fed.init
, because it has become the field "max_task_retries" of cross_silo_xx_options
, which is what cross_silo_send_max_retries
stands for under the hood, keeping it will cause conflicts.
+1. Expose some common options is more maintainable and extensible instead of the options of ray.Actor. SendProxy could be ray.actor or something else.
Make sense, I'll use a class to only expose certain options
This PR remove the original cross_silo_send_max_retries argument in fed.init, because it has become the field "max_task_retries" of cross_silo_xx_options, which is what cross_silo_send_max_retries stands for under the hood, keeping it will cause conflicts.
Move this to PR description?
As discussed offline, this PR LGTM.
And you may need file an issue to trace the related coming items.
Sure
This is the first step of #134
This PR provides
cross_silo_send_resource_label
andcross_silo_recv_resource_label
config infed.init
and convert them to the "resources" field of ActorClass.options.