Skip to content

fix: avert unwanted log level changes from upstream JDBCProvider#1177

Closed
c-dilks wants to merge 1 commit intodevelopmentfrom
log-guard
Closed

fix: avert unwanted log level changes from upstream JDBCProvider#1177
c-dilks wants to merge 1 commit intodevelopmentfrom
log-guard

Conversation

@c-dilks
Copy link
Copy Markdown
Member

@c-dilks c-dilks commented Apr 1, 2026

Calling JDBCProvider.connect() destroys the log level of certain loggers, viz. org.freehep.math.minuit. Instead of attempting to fix upstream, we can save desired log levels and restore them; this is the fix we pretty much do downstream anyway (e.g., in calcode), where we typically just keep setting the log level we want.

Calling `JDBCProvider.connect()` destroys the log level of certain
loggers, _viz._ `org.freehep.math.minuit`. Instead of attempting to fix
upstream, we can save desired log levels and restore them; this is the fix
we pretty much do downstream anyway (_e.g._, in `calcode`), where we
typically just keep setting the log level we want.
@c-dilks
Copy link
Copy Markdown
Member Author

c-dilks commented Apr 2, 2026

Not good enough for calcode, something else is changing the log level too. Worse yet, the point at which the log level change varies from test to test, and I suspect there may be some data race making it very difficult to track down exactly where the unwanted change happens.

@c-dilks c-dilks closed this Apr 2, 2026
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

Successfully merging this pull request may close these issues.

1 participant