Lightning-AI / Lightning-AI/lightning-thunder
materialize frames / tracebacks less often
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.5k
- Forks
- 121
- PR merge metrics
- No merged PRs in 30d
Description
We currently create stack traces with the exception and convert Thunder frames -> fake Python frames then. We might instead look at keeping our own stack trace until we need to hand the exception to the outside to save the conversion for internally caught things (in particular StopIteration).
I don't have numbers, but I expect it to be perf-relevant in a way that will show on the CI run times.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is named in the issue. Start by locating where exceptions create stack traces and where Thunder frames are converted to fake Python frames, then compare internally caught StopIteration handling with exceptions handed outside. Done should include evidence of improved CI runtime without changing externally visible traceback behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- compilers, performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100