This repository has been archived by the owner on Jan 5, 2024. It is now read-only.
Use logger instead of logging consistently accross the scripts #36
Conversation
This file contains 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
emkll
changed the title
redshiftzero
previously approved these changes
Dec 4, 2019
|
this need a rebase now <3 |
|
heads up I still see two cases where |
Logging works, but does not provide the class/method/line where the logging was invoked. Logger was used inconsistently accross the codebase.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Logging works, but does not provide the class/method/line where the logging was invoked. Logger was used inconsistently accross the codebase.
Ensure that the logs properly appear with class + methodname + line number in the logs in
/home/user/.securedrop_export/logs/export.loginsd-export-usb