fix(issue #3279): More traceback cleaning - #3498
Open
arunsoman wants to merge 2 commits into
Open
Conversation
Signed-off-by: Arun Soman <aarunsoman@gmail.com>
for more information, see https://pre-commit.ci
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #3498 +/- ##
====================================================
- Coverage 100.00000% 99.99486% -0.00514%
====================================================
Files 128 128
Lines 19452 19454 +2
Branches 1321 1322 +1
====================================================
+ Hits 19452 19453 +1
- Partials 0 1 +1
🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #3279
What
autonomous fix via
atomic-forge fix— CIE (code graph over MCP) localized the bug, generated a failing regression test, and forge's repair loop fixed the source against it.Issue
https://vorpus.org/blog/beautiful-tracebacks-in-trio-v070/ made tracebacks in some scenarios nicer, but afaict it mostly just affects calls to
trio.runand when spawning tasks. (Implementation. Tested in test_traceback_frame_removal).But there's still a lot of other scenarios that cause verbose outputs: