Skip to content
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

Closed
wants to merge 1 commit into from

Conversation

d1jang
Copy link
Contributor

@d1jang d1jang commented Aug 11, 2021

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

@facebook-github-bot facebook-github-bot added oncall: jit Add this issue/PR to JIT oncall triage queue cla signed labels Aug 11, 2021
@facebook-github-bot
Copy link
Contributor

facebook-github-bot commented Aug 11, 2021

🔗 Helpful links

💊 CI failures summary and remediations

As of commit 8ce8b39 (more details on the Dr. CI page):


  • 3/4 failures possibly* introduced in this PR
    • 1/3 non-scanned failure(s)
  • 1/4 broken upstream at merge base 126ff62 from Aug 12 until Aug 13

2 failures not recognized by patterns:

Job Step Action
GitHub Actions Lint / shellcheck Assert that regenerating the workflows didn't change them 🔁 rerun
GitHub Actions Lint / quick-checks Ensure correct trailing newlines 🔁 rerun

1 job timed out:

  • pytorch_linux_xenial_py3_clang7_asan_test1

🚧 1 fixed upstream failure:

These were probably caused by upstream breakages that were already fixed.

Please rebase on the viable/strict branch (expand for instructions)

If your commit is older than viable/strict, run these commands:

git fetch https://github.com/pytorch/pytorch viable/strict
git rebase FETCH_HEAD

ci.pytorch.org: 1 failed


This comment was automatically generated by Dr. CI (expand for details).Follow this link to opt-out of these comments for your Pull Requests.

Please report bugs/suggestions to the (internal) Dr. CI Users group.

Click here to manually regenerate this comment.

@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D30241792

1 similar comment
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D30241792

@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D30241792

…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
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D30241792

@facebook-github-bot
Copy link
Contributor

This pull request has been merged in 61b49c8.

alanwaketan pushed a commit that referenced this pull request Aug 17, 2021
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
@tugsbayasgalan tugsbayasgalan changed the title [JIT] Add a flag to suppress stacktrace in exception messages Add a flag to suppress stacktrace in exception messages Oct 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla signed fb-exported Merged oncall: jit Add this issue/PR to JIT oncall triage queue
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants