Reintroduce stacktrace trimming
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 228
- Forks
- 81
- Avg merge
- 1d 29m
- Merged PRs (30d)
- 1
Description
In https://github.com/JuliaIO/FileIO.jl/pull/415 the handle_error function was updated to the new API of CapturedException, which just gives a backtrace to it (instead of a stacktrace). It was not obvious how to retain the existing trim! functionality, so that is now disabled on 1.13+. This should probably be reintroduced if possible.
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
Start by reviewing the handle_error changes in PR #415 and the Julia 1.13+ CapturedException API, focusing on how it now provides a backtrace instead of a stacktrace. Determine how the existing trim! behavior can be retained, then verify that stacktrace trimming is restored for Julia 1.13+.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100