-
Notifications
You must be signed in to change notification settings - Fork 43
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
Update logging #1167
Update logging #1167
Conversation
Codecov ReportAttention: Patch coverage is
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## main #1167 +/- ##
==========================================
- Coverage 53.10% 52.50% -0.60%
==========================================
Files 674 674
Lines 23120 23185 +65
Branches 1762 1770 +8
==========================================
- Hits 12278 12174 -104
- Misses 10441 10607 +166
- Partials 401 404 +3
Flags with carried forward coverage won't be shown. Click here to find out more.
|
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.
Looks ok if there are no objections to splitting the log file from others
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.
Looks good to me, good solution to the problem
nexusmods.app.main
for the main process onlynexusmods.app.slim
for the "slim" process onlyHaving two logging files fixes the issue where both the main and slim process try to write to the same file. While we didn't have any corruptions of log files, we did have an issue where a slim process will move the current main log to an archive log while the main process would continue writing to the archive log. It made debugging and viewing logs difficult, this PR fixes that issue by clearly separating the two logs.