Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Don't print empty goja stacktraces on captured panics #3749

Merged
merged 1 commit into from
May 22, 2024
Merged

Don't print empty goja stacktraces on captured panics #3749

merged 1 commit into from
May 22, 2024

Commits on May 20, 2024

  1. Don't print empty goja stacktraces on captured panics 

    This has been broken for years after some goja refactoring.

There doesn't seem to be a way for this to be fixed without a lot of
boilerplate all over the code. And this functionality has not been used
in the last few years in my experience.

closes #1906
    @mstoykov
    mstoykov committed May 20, 2024
    Configuration menu
    Copy the full SHA
    3723047 View commit details
    Browse the repository at this point in the history