-
Notifications
You must be signed in to change notification settings - Fork 821
Fix logging crash #14388
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
Fix logging crash #14388
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/14388
Note: Links to docs will display an error until the docs builds have been completed. ❌ 3 New FailuresAs of commit 9af526c with merge base 5348ea9 ( NEW FAILURES - The following jobs have failed:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
|
@metascroy has exported this pull request. If you are a Meta employee, you can view the originating diff in D82666928. |
This PR needs a
|
Summary: The logging code will raise an uncaught exception today if message/filename are nil because adding a nil object as a value is not supported. This checks for nil and replaces with empty string. Reviewed By: linbinyu, shoumikhin Differential Revision: D82666928
86bca75 to
9af526c
Compare
|
@metascroy has exported this pull request. If you are a Meta employee, you can view the originating diff in D82666928. |
|
@metascroy is this cherry-picked on the release branch? |
Differential Revision: D82666928 Pull Request resolved: pytorch#14388
Differential Revision: D82666928 Pull Request resolved: pytorch#14388
Differential Revision: D82666928