Conversation
setup_logger() was a helper for the main() function to setup the default logging level and set the output. It was never intended to be called by modules.
Updated all the workflows to use a consistent way to setup the logging with a config and no longer use setup_logger() to setup the module level logger to avoid confusion in the future.
achatur
approved these changes
Feb 18, 2026
Make the log output a little bit more structured to make it easier to follow hopefully.
Add a logging message to make it clear why storage is skipped.
c4a07ee to
72d5e55
Compare
This file contains hidden or 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
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.
Fixed up workflow logging to not call basicConfig() constantly. Setup the logs in the same consistent way to not be verbose for modules we are not interested in debug details. Improved output of the event handler to make troubleshooting more easy.