You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, when using MySQL as database, during initialization, the logs of the Hikari pool creation are logged as an error, even though they ARE just INFO logs.
Here are the logs (without coloring, of course):
The message itself starts with INFO, but the logging level is in ERROR.
I can confirm that, even with this being in the logs, the database is initialized and works properly.
Are there any alternatives?
Keep it like this, it is not a functional error.
Anything else?
Might be an issue with using slf4j-simple.
The text was updated successfully, but these errors were encountered:
What feature do you want to see added?
Right now, when using MySQL as database, during initialization, the logs of the Hikari pool creation are logged as an error, even though they ARE just INFO logs.
Here are the logs (without coloring, of course):
The message itself starts with
INFO
, but the logging level is in ERROR.I can confirm that, even with this being in the logs, the database is initialized and works properly.
Are there any alternatives?
Keep it like this, it is not a functional error.
Anything else?
Might be an issue with using
slf4j-simple
.The text was updated successfully, but these errors were encountered: