[logging/debugging] handle None (constant) args in debug log#137032
[logging/debugging] handle None (constant) args in debug log#137032coconutruben wants to merge 1 commit intopytorch:mainfrom
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/137032
Note: Links to docs will display an error until the docs builds have been completed. ✅ You can merge normally! (4 Unrelated Failures)As of commit f150c7d with merge base 1f3a793 ( FLAKY - The following job failed but was likely due to flakiness present on trunk:
BROKEN TRUNK - The following jobs failed but was present on the merge base:👉 Rebase onto the `viable/strict` branch to avoid these failures
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
|
This pull request was exported from Phabricator. Differential Revision: D63652564 |
0347578 to
c8a7458
Compare
…#137032) Summary: Pull Request resolved: pytorch#137032 # Why The arguments are filtered out as they are just const in the compiled graph, but the logger still expects a non-None type # What When passing a filtered out arg (None) to the debug logger, just log that it's a filtered out argument, instead of throwing a Type error also add unit test to capture this behavior going forward # Background pytorch#131594 Test Plan: - execute repro from pytorch#135584 (comment) with and without the edits Reviewed By: angelayi Differential Revision: D63652564
|
This pull request was exported from Phabricator. Differential Revision: D63652564 |
c8a7458 to
3a632df
Compare
|
This pull request was exported from Phabricator. Differential Revision: D63652564 |
3a632df to
9035394
Compare
|
This pull request was exported from Phabricator. Differential Revision: D63652564 |
…#137032) Summary: Pull Request resolved: pytorch#137032 # Why The arguments are filtered out as they are just const in the compiled graph, but the logger still expects a non-None type # What When passing a filtered out arg (None) to the debug logger, just log that it's a filtered out argument, instead of throwing a Type error also add unit test to capture this behavior going forward # Background pytorch#131594 Test Plan: - execute repro from pytorch#135584 (comment) with and without the edits Reviewed By: angelayi Differential Revision: D63652564
9035394 to
5f3dbf2
Compare
|
This pull request was exported from Phabricator. Differential Revision: D63652564 |
5f3dbf2 to
226c16e
Compare
|
This pull request was exported from Phabricator. Differential Revision: D63652564 |
…#137032) Summary: Pull Request resolved: pytorch#137032 # Why The arguments are filtered out as they are just const in the compiled graph, but the logger still expects a non-None type # What When passing a filtered out arg (None) to the debug logger, just log that it's a filtered out argument, instead of throwing a Type error also add unit test to capture this behavior going forward # Background pytorch#131594 Test Plan: - execute repro from pytorch#135584 (comment) with and without the edits Reviewed By: angelayi Differential Revision: D63652564
|
This pull request was exported from Phabricator. Differential Revision: D63652564 |
226c16e to
f150c7d
Compare
|
@pytorchbot merge -f 'Landed internally' (Initiating merge automatically since Phabricator Diff has merged, using force because this PR might not pass merge_rules.json but landed internally) |
Merge startedYour change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
…#137032) Summary: # Why The arguments are filtered out as they are just const in the compiled graph, but the logger still expects a non-None type # What When passing a filtered out arg (None) to the debug logger, just log that it's a filtered out argument, instead of throwing a Type error # Background pytorch#131594 Test Plan: - execute repro from pytorch#135584 (comment) with and without the edits Differential Revision: D63652564 Pull Request resolved: pytorch#137032 Approved by: https://github.com/angelayi
Summary:
Why
The arguments are filtered out as they are just const in the compiled graph, but the logger still expects a non-None type
What
When passing a filtered out arg (None) to the debug logger, just log that it's a filtered out argument, instead of throwing a Type error
Background
#131594
Test Plan: - execute repro from #135584 (comment) with and without the edits
Differential Revision: D63652564
cc @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @ColinPeppler @amjames @desertfire @chauhang @rec