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

Change Hikari pool logging #227

Open
ElTankesitoArceus opened this issue Nov 15, 2024 · 0 comments
Open

Change Hikari pool logging #227

ElTankesitoArceus opened this issue Nov 15, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@ElTankesitoArceus
Copy link

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):

[00:22:36 ERROR]: [AuthMe] [Server thread] INFO fr.xephi.authme.libs.com.zaxxer.hikari.HikariDataSource - AuthMeMYSQLPool - Starting...
[00:22:36 ERROR]: [AuthMe] [Server thread] INFO fr.xephi.authme.libs.com.zaxxer.hikari.HikariDataSource - AuthMeMYSQLPool - Start completed.

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.

@ElTankesitoArceus ElTankesitoArceus added the enhancement New feature or request label Nov 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant