Skip to content

Conversation

BardyBard
Copy link
Collaborator

@BardyBard BardyBard commented Oct 13, 2025

As discussed in #515 runtime errors from the little jar are exceptionally unhelpful.

R5Process.run() which is the abstract method for all for all of the methods in R5. I've placed a try catch statement to LOG the traceback in the R console through our existing logging system when an error is caught.

I believe this simple change will actually solve most of the problems. For example in the issue opened by Matt, the rjava error thrown is a ExecutionException. The only code that throws an ExceutionException in the little jar is R5Process.run() so that error would now come with a java stack trace making debugging easier.

@mattwigway
Copy link
Contributor

Good call, this lgtm

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants