-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Fix optim.lr_scheduler examples in doc to use optimizer vs self.opt #119563
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
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/119563
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit a038584 with merge base 90dabff ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
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.
Thanks for the catch!
Hm weird...the normal PR jobs aren't triggering. We should verify the docs look good before merging. |
@clee2000 do you know why the jobs aren't getting triggered? |
The commit title contains |
Is CI needed for docs regeneration? Can I force-push the commit? |
Yes, we have a docs build that depends on building torch, so could you recommit without the skip ci message? Yes, forcepushing would work. |
@janeyx99 , done. |
@pytorchbot merge |
Merge startedYour change will be merged once all checks pass (ETA 0-4 Hours). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
…119563) Fixes #119561 Pull Request resolved: #119563 Approved by: https://github.com/janeyx99
Fixes #119561