-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Tidy ExecutorService code, remove superfluous map access (Issue 1841) #1842
Conversation
Tidy ExecutorService code, remove superfluous imports and map access.
Hi @jamey-clari Here's what happens next:
The PR will be prioritized according to our internal development and testing capacity. We’ll let you know when it’s ready to move to the next step or if any changes are needed. |
NP @molivasdat - I'd expect things to wind their way through the pipeline for a bit. |
It looks like some sort of surefire test failed for only Java 11. It's hard to imagine that any of my edits were JDK version sensitive let alone to version 11 but not 8 and 16. Is it possible the build had some sort of transient issue and simply needs to be retried? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code review and test results:
Things to be aware of:
- The changes make sense, mainly cleanup work
- No change in behavior, so existing tests should would anything changed
Things to worry about:
- Nothing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- PR makes the code in ExecutorService and AbstractJdbcDatabase classes more readable.
- Fix prevents duplication of stack trace in log output.
- No additional testing required.
APPROVED
Description
Tidy ExecutorService code, remove superfluous imports and map access.