-
Notifications
You must be signed in to change notification settings - Fork 50
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
better stack traces #77
Comments
I did a small proof of concept where I modified
With the locations present on each node I then
Running this
Yields this
|
@Siubaak I would love to get some thoughts on this from you, particularly any ideas around approaches |
wow,I think this is very good!So you can send it out?Thank you very much!(^▽^) |
any updates on this? :) |
hi @doodlesbykumbi! your work is awesome. can you publish your work ? :) |
It would be nice if errors created and thrown by code running via sval could have better stack traces. Below I've shared an approach I used in a POC. All the information to create rich stack traces is available. I suspect it's even possible to have stack traces that combine traces from scripts within sval and scripts outside (i.e. when an outside script calls an inside script and vice-versa)
The text was updated successfully, but these errors were encountered: