-
Notifications
You must be signed in to change notification settings - Fork 26.3k
Print fqn in the warning message #94313
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/94313
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 5bd9ef8: This comment was automatically generated by Dr. CI and updates every 15 minutes. |
52b5a7c to
a179e82
Compare
fegin
left a comment
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 PR. Linter has some errors.
awgu
left a comment
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.
I think we need to move the f to the line with the { ... } to print the correct string and fix the lint.
a179e82 to
5bd9ef8
Compare
|
@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 |
Print fqn in the warning message, also make "else" match with the "if" in _apply_to_modules()