You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All prints to stdout used for debugging, error tracking, or general info should be replaced with formal logging. These logs should be written to a log/ file in the root directory of this repo with a new log file created every day and only the previous two weeks worth of log files being kept before being overwritten by new log files (a lot of this is handled under the hood by logging libraries).
Additional Info
A good starting point would be to find all prints in the repo and replace them with calls to the logger module once it is set up/an external library has been chosen. From that point, logging should be added for all cases where exceptions are handled or errors could occur.
Priority
Medium
The text was updated successfully, but these errors were encountered:
Brief Feature Description
All prints to stdout used for debugging, error tracking, or general info should be replaced with formal logging. These logs should be written to a log/ file in the root directory of this repo with a new log file created every day and only the previous two weeks worth of log files being kept before being overwritten by new log files (a lot of this is handled under the hood by logging libraries).
Additional Info
A good starting point would be to find all prints in the repo and replace them with calls to the logger module once it is set up/an external library has been chosen. From that point, logging should be added for all cases where exceptions are handled or errors could occur.
Priority
Medium
The text was updated successfully, but these errors were encountered: