-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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] Clean up some deprecation messages (they shouldn't be there) and make others error=True
(from error=False
)
#38555
[RLlib] Clean up some deprecation messages (they shouldn't be there) and make others error=True
(from error=False
)
#38555
Conversation
…te_deprecation_messages_for_old_stack
rllib/BUILD
Outdated
# size = "medium", | ||
# srcs = ["examples/batch_norm_model.py"], | ||
# args = ["--as-test", "--framework=tf", "--run=PPO", "--stop-reward=80"] | ||
# ) |
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.
Can we leave a comment here on why this is commented out and when it should be reenabled, please?
Also, depending on the reason, it might become a "new stack issue"?
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.
reestablished test case. It's ok to leave our old tf register_variables
NOT deprecated for now.
@@ -207,7 +207,6 @@ def _update_outputs_and_next_state( | |||
return outputs, next_state | |||
|
|||
|
|||
@Deprecated(error=False) |
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.
Why are we removing this deprecation warning? This is going to be deprecated soon according to our plans, no?
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.
Yes, absolutely. However, it is still active in many algos and thus users receive deprecation warnings for using non-deprecated algos. Also most algos (except PPO) still use the _enable_learner_api=False
by default, so these warnings are too confusing.
@@ -202,7 +201,6 @@ | |||
# fmt: on | |||
|
|||
|
|||
@Deprecated(old="rllib.models.catalog.ModelCatalog", error=False) |
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.
Same here, why are we removing this? Simply too verbose?
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.
Yes, too verbose and confusing.
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.
Cool cleanup. Thanks! Just one nit on the commented out ppo test and I'd like to know why we are moving all of this stuff we want to deprecate from warnings to developer API.
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.
Does this PR solve the deprecation warning regarding exploration setting being deprecated? If so, I couldn't find the code that deals with this.
Hey @kouroshHakha , the deprecation warnings for all exploration classes had already been fixed in an earlier PR. |
Signed-off-by: sven1977 <svenmika1977@gmail.com>
Hey @ArturNiederfahrenhorst , we are moving "back to" DeveloperAPI b/c these classes/functions must - per our LINTer - have some API tag. |
…te_deprecation_messages_for_old_stack
…and make others `error=True` (from `error=False`) (ray-project#38555) Signed-off-by: e428265 <arvind.chandramouli@lmco.com>
…and make others `error=True` (from `error=False`) (ray-project#38555)
…and make others `error=True` (from `error=False`) (ray-project#38555) Signed-off-by: Jim Thompson <jimthompson5802@gmail.com>
…and make others `error=True` (from `error=False`) (ray-project#38555) Signed-off-by: Victor <vctr.y.m@example.com>
Clean up some deprecation messages (they shouldn't be there) and make others
error=True
(fromerror=False
)Why are these changes needed?
Related issue number
Checks
git commit -s
) in this PR.scripts/format.sh
to lint the changes in this PR.method in Tune, I've added it in
doc/source/tune/api/
under thecorresponding
.rst
file.