-
Notifications
You must be signed in to change notification settings - Fork 26.3k
[FX] Assert None concrete_args and improve error messages #74662
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
[ghstack-poisoned]
🔗 Helpful links
💊 CI failures summary and remediationsAs of commit b692bfd (more details on the Dr. CI page):
🕵️ 2 new failures recognized by patternsThe following CI failures do not appear to be due to upstream breakages:
|
| Job | Step | Action |
|---|---|---|
| Unknown | 🔁 rerun |
This comment was automatically generated by Dr. CI (expand for details).
Please report bugs/suggestions to the (internal) Dr. CI Users group.
Previously, we would not emit a check that `concrete_args` with value `None` matched that value during runtime. This fixes that and improves some of the warning messages [ghstack-poisoned]
Previously, we would not emit a check that `concrete_args` with value `None` matched that value during runtime. This fixes that and improves some of the warning messages [ghstack-poisoned]
|
@jamesr66a has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator. |
Chillee
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.
Makes sense for what it does.
I do kinda wonder whether these checks are a good idea in the first place though... I'm worried it just adds unnecessary complexity/don't always work.
Although, I'm guessing that you want these guards here since you find them helpful, in which case, ignore that :P
|
@Chillee yeah I was helping @pbelevich debug an issue in PiPPy that probably would have been more clear if we had these guards |
Previously, we would not emit a check that `concrete_args` with value `None` matched that value during runtime. This fixes that and improves some of the warning messages Differential Revision: [D35137362](https://our.internmc.facebook.com/intern/diff/D35137362) [ghstack-poisoned]
Summary: Pull Request resolved: #74662 Previously, we would not emit a check that `concrete_args` with value `None` matched that value during runtime. This fixes that and improves some of the warning messages Test Plan: Imported from OSS Reviewed By: Chillee Differential Revision: D35137362 Pulled By: jamesr66a fbshipit-source-id: 222a2c8a907748f90290f1c1b4ab8012b46099a0
Stack from ghstack (oldest at bottom):
Previously, we would not emit a check that
concrete_argswith valueNonematched that value during runtime. This fixes that and improves some of the warning messagesDifferential Revision: D35137362