-
Notifications
You must be signed in to change notification settings - Fork 7.1k
reverting some recently introduced exceptions #5659
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
💊 CI failures summary and remediationsAs of commit 25eda42 (more details on the Dr. CI page): 💚 💚 Looks good so far! There are no failures yet. 💚 💚 This comment was automatically generated by Dr. CI (expand for details).Please report bugs/suggestions to the (internal) Dr. CI Users group. |
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 @jdsgomes, just a few comments. Let me know your thoughts.
Co-authored-by: Vasilis Vryniotis <[email protected]>
@jdsgomes The problem seems to be on the assertion message (type/tostring operator) of the Do you mind converting the PR to draft and ping us when you want a review? |
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 @jdsgomes. I understand that's far from a perfect situation, I left one comment below and marked all places where it appears. Let me know your thoughts.
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 all the updates. Feel free to merge on green CI.
Hey @jdsgomes! You merged this PR, but no labels were added. The list of valid labels is available at https://github.com/pytorch/vision/blob/main/.github/process_commit.py |
Summary: * reverting some recently introduced exceptions * Update torchvision/ops/poolers.py * address PR comments * replace one more assert with torch._assert: * address PR comments * make type checker happy * Fix bug * fix bug * fix for wrong asserts * attempt to make tests pass * Fix test_ops tests * Fix expected exception in tests * fix typo * fix tests and format * fix flake8 * remove one last exception * fix error * remove unused immport * replace fake returns by else (Note: this ignores all push blocking failures!) Reviewed By: YosuaMichael Differential Revision: D35216770 fbshipit-source-id: 68d01d50d083070976a6cd7bd4a98cc270be9723 Co-authored-by: Vasilis Vryniotis <[email protected]> Co-authored-by: Vasilis Vryniotis <[email protected]>
Removing exceptions and asserts from the forward pass in order to enable FX traceability. Instead reverting to torch._assert which is FX traceable