WIP/RFC: print stacktrace when eval fails #160
Draft
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.
Currently, suppose I have a file like
I get an error which does not actually show a stacktrace of where the exception was raised
The stacktrace traces back to this
error
call:Literate.jl/src/Literate.jl
Lines 785 to 792 in 42f3941
With this patch you get something like the following (which could be much longer if the error thrown is deep in some dependency, which is the information you would want):
Now, I don't yet quite have a good idea of how to do this well, so opening this for discussion. This was just a side tangent when working on a notebook. A few notes though:
sprintf
the backtrace intoerror
. However, returning a custom exception object seems like the more correct thing to do.@error
from the parent function seems actually redundant.include_string
, any error I think gets wrapped inLoadError
(but this does not seem to be documented). It also adds a bunch of things into the stacktrace which are hard to get rid of.rethrow
-type magic..