Closed mrinalwahal closed 5 years ago
A few more comments:
log()
function doesn't offer much to begin with. The logging module prints to stderr by default when no filename is specified and it supports setting a loglevel which you already use. So why not just initialise the logging module every time (irrespective of LOG_DIR
) and set the log level. If and when LOG_DIR
is specified, pass it to the filename
argument is logging.basicConfig()
. Then all calls to the custom log()
function can be replaced by direct calls to the logging module methods (so instead of doing log("error", "message")
we can just do logging.error("message")
and let the logging module take care of the rest.Updated the logger func and pushed.
This pull request introduces 3 alerts when merging d7e5d07e1d48f4810fc4c6e496bebabfeaea3b19 into 24d88e2e250480cc18f94c3a7024a2af3200a06f - view on LGTM.com
new alerts:
This pull request fixes 3 alerts when merging 5873beb04d6737df4753f4fabfaad10f5eb2495e into 24d88e2e250480cc18f94c3a7024a2af3200a06f - view on LGTM.com
fixed alerts:
This pull request fixes 2 alerts when merging 8b9e6dfba8968aed1afdd4c116de03973ed802ca into 24d88e2e250480cc18f94c3a7024a2af3200a06f - view on LGTM.com
fixed alerts:
Following issues are either resolved, or can simply be closed:
[1] #43 - Now secrets are updated for all repos as soon as the user logs in. [2] #4 - Pipeline steps for restoring and rebuilding the cache have been added - BUT I'm still testing this. [3] #3 - I figured we don't need this since we are not using multiple steps for same dir. Perhaps this issue can either be closed or kept separate for future discussions. [4] #17 - Only important logs are shown to the user now, like critical messages and errors. However, user can now specify a new
DEBUG=True
environment variable, and if they do, all logs even from the DEBUG level will be produced for the user. Otherwise only aforementioned ones.I'm still writing the documentation (see #44 ) and will push it soon.