Fix failfast Hikari configuration parameter #185
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
initializationFailFast has been removed from Hikari >= 3.0.0 and replaced with initializationFailTimeout. See https://github.com/brettwooldridge/HikariCP#infrequently-used
jopereira
force-pushed
the
fix-failfast
branch
from
1f202f7
to
c8573bc
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is just a very minor bug fix: initializationFailFast has been removed from Hikari >= 3.0.0 and replaced with initializationFailTimeout. See https://github.com/brettwooldridge/HikariCP#infrequently-used
FailFast was still in WSProdConfig but not being used. This changes it to initializationFailTimeout without changing current behavior (timeout = 1 is equivalent to failfast = true).