-
Notifications
You must be signed in to change notification settings - Fork 858
Fixing log issue for Label Model #1652
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
Merged
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
7be7aea
adding tqdm progress bar on label fit method
anerirana 92a7ce3
correcting import order to pass tox check
anerirana e2f5c9d
tox check error fixed
anerirana 2f3837b
adding progress bar parameter to fit method
anerirana d39c6e9
adding unit test to cover new progress bar paths
anerirana 2248532
Issue #1638 logging fix for LabelModel.fit()
anerirana aebfe31
Merge branch 'master' of https://github.com/snorkel-team/snorkel
anerirana 7757119
trigger another pipeline build
anerirana f1e4208
removing extra space from label model
anerirana File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This appears to be changing the default logging the logging module, not for this specific class's logger. Can you modify just the logging level of self.logger instead?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I did consider this. But, the logging has been implemented throughout the code at the root level. The logging inside
fit()
ofLabelModel
andlog()
ofLogger
are using module level logging functionlogging.info()
. Therefore all the logs are generated by root level logger and the only way to set log level forLabelModel
specifically is to change theCustomeLogger
significantly. However, I don't think that is necessary. Even if I change the root logger level toINFO
, it would not interfere with the logging flow. Because, before creating anINFO
level log, there will always be a check for the verbose parameter.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see. Alright, this looks good to me then!