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.

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

Stack trace suppression in console would be a handy option #346

Open
justparking opened this issue Jan 9, 2025 · 0 comments
Open

Stack trace suppression in console would be a handy option #346

justparking opened this issue Jan 9, 2025 · 0 comments

Comments

@justparking
Copy link
Contributor

Being able to optionally exclude full stacktraces would be very useful, keep noise out of the console and make it easier it figure out what's going wrong

Most of the long stack traces are not necessarily useful.

I believe this is code section that controls some of that behaviour:

} catch (Exception exc) {
hasErrors = true;
// inject into the error
_errReader.inject(exc.toString());
// log cleaner Python exception trace if possible
if (exc instanceof PyException)
_logger.warn("The bindings could not be applied to the Python instance. {}", exc.toString());
else
_logger.warn("The bindings could not be applied to the Python instance.", exc);
}

That's during initialisation. There are likely others that occur afterwards.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant