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

Exceptions aren't always passed on, making troubleshooting difficult #203

Closed
pmonks opened this issue Sep 14, 2023 · 0 comments
Closed

Exceptions aren't always passed on, making troubleshooting difficult #203

pmonks opened this issue Sep 14, 2023 · 0 comments

Comments

@pmonks
Copy link
Collaborator

pmonks commented Sep 14, 2023

In some parts of the code exceptions are caught, but then a brand new exception is thrown without passing on the original causative exception. This makes troubleshooting more difficult.

Here's an example of this kind of thing.

Note: I'm already halfway through fixing this throughout the codebase, and will submit a PR for it shortly. I suspect this should be a fairly easy / low risk change to review and merge in, despite the potentially large number of changes throughout the codebase, but as always would welcome additional pairs of eyes on my rusty Java!

goneall added a commit that referenced this issue Sep 14, 2023
@pmonks pmonks closed this as completed Sep 15, 2023
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

No branches or pull requests

1 participant