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
Add a flag to suppress stacktrace in exception messages #63073
Conversation
🔗 Helpful links
💊 CI failures summary and remediationsAs of commit 8ce8b39 (more details on the Dr. CI page):
2 failures not recognized by patterns:
1 job timed out:
🚧 1 fixed upstream failure:These were probably caused by upstream breakages that were already fixed.
Please rebase on the
|
This pull request was exported from Phabricator. Differential Revision: D30241792 |
1 similar comment
This pull request was exported from Phabricator. Differential Revision: D30241792 |
4f380a8
to
c699348
Compare
This pull request was exported from Phabricator. Differential Revision: D30241792 |
c699348
to
b7340b6
Compare
…rch#63073) Summary: Pull Request resolved: pytorch#63073 It turned out that it's less than ideal to print out verbose stacktrace in exception messages in high-QPS services (see the related task) with a non-significant failure rate due to the truncation of long stacktrace which results in losing the original exception message thrown from native code. It is actually desirable to retain only the message of the original exception directly thrown from native code in such a usecase. This change adds a new flag `torch_jit_disable_exception_stacktrace` to the pytorch jit interpreter to suppress stacktrace in the messages of exception thrown from the interpreter. Reviewed By: Krovatkin Differential Revision: D30241792 fbshipit-source-id: fbc90c11e99ab8c1623f016559ad5bfeeaca8465
This pull request was exported from Phabricator. Differential Revision: D30241792 |
b7340b6
to
8ce8b39
Compare
This pull request has been merged in 61b49c8. |
Summary: Pull Request resolved: #63073 It turned out that it's less than ideal to print out verbose stacktrace in exception messages in high-QPS services (see the related task) with a non-significant failure rate due to the truncation of long stacktrace which results in losing the original exception message thrown from native code. It is actually desirable to retain only the message of the original exception directly thrown from native code in such a usecase. This change adds a new flag `torch_jit_disable_exception_stacktrace` to the pytorch jit interpreter to suppress stacktrace in the messages of exception thrown from the interpreter. Reviewed By: Krovatkin Differential Revision: D30241792 fbshipit-source-id: c340225c69286663cbd857bd31ba6f1736b1ac4c
Summary:
It turned out that it's less than ideal to print out verbose stacktrace in exception messages in high-QPS services (see the related task) with a non-significant failure rate due to the truncation of long stacktrace which results in losing the original exception message thrown from native code. It is actually desirable to retain only the message of the original exception directly thrown from native code in such a usecase.
This change adds a new flag
torch_jit_disable_exception_stacktrace
to the pytorch jit interpreter to suppress stacktrace in the messages of exception thrown from the interpreter.Differential Revision: D30241792