-
Notifications
You must be signed in to change notification settings - Fork 5.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[RLlib] Better behavior if user does not specify stopping condition in RLLib CLI #31078
[RLlib] Better behavior if user does not specify stopping condition in RLLib CLI #31078
Conversation
Signed-off-by: Artur Niederfahrenhorst <[email protected]>
rllib/common.py
Outdated
@@ -216,7 +218,7 @@ class CLIArguments: | |||
|
|||
# Train arguments | |||
# __cli_train_start__ | |||
Stop = typer.Option(None, "--stop", "-s", help=get_help("stop")) | |||
Stop = typer.Option(None, *STOP_ARG_NAMES, help=get_help("stop")) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ArturNiederfahrenhorst hmm, I think you can fix all of this by making the default arg "{}"
instead of None
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
great, thanks for spotting this @ArturNiederfahrenhorst! I think we can simplify
Signed-off-by: Artur Niederfahrenhorst <[email protected]>
@maxpumperla I have also removed the warning I introduced about stop being empty to simplify this. |
@ArturNiederfahrenhorst I think we can add this to the typer help of the stop command, if not already there |
@maxpumperla Info on how to use stop is already in the help string. I'll leave it there and not warn users when it's missing. |
…n RLLib CLI. (ray-project#31078) Signed-off-by: Weichen Xu <[email protected]>
…n RLLib CLI. (ray-project#31078) Signed-off-by: tmynn <[email protected]>
Signed-off-by: Artur Niederfahrenhorst [email protected]
Why are these changes needed?
We have lots of examples inside RLlib of running ray CLI similar to
rllib train --env ... --config ...
that lack a stopping condition.They error out with the following message.
We should not error out, since a workflow to be expected from us is to quickly start an experiment from CLI, observe it and cancel it manually without caring for stopping condidations.
Related issue number
https://discuss.ray.io/t/problem-with-rllib-configuration-by-command-line/8624
Checks
git commit -s
) in this PR.scripts/format.sh
to lint the changes in this PR.