-
Notifications
You must be signed in to change notification settings - Fork 363
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
[Fix] Fix error format of log message #508
Conversation
Codecov ReportBase: 78.07% // Head: 77.55% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## main #508 +/- ##
==========================================
- Coverage 78.07% 77.55% -0.53%
==========================================
Files 125 116 -9
Lines 8991 8606 -385
Branches 1845 1774 -71
==========================================
- Hits 7020 6674 -346
+ Misses 1659 1637 -22
+ Partials 312 295 -17
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
Solve #582 |
* Fix error format of log message * Fix unit test * remove unnecessary comment
Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
If the
interval
of LoggerHook is smaller than thewindow_size
ofLogProcessor
,time
anddata_time
in log string are not formatted byLogProcessor
:Modification
LogProcessor
assumestime
,data_time
andeta
will appear at the same time(Generated byIterTimerHook
). However, the previous implementation ofIterTimerHook
will only recordeta
afterwindow_size
iterations, which causestime
,eta
anddata_time
are not caught byLogProcessor
. Therefore,time
anddata_time
are formatted as expected,BC-breaking (Optional)
Does the modification introduce changes that break the backward-compatibility of the downstream repos?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
Use cases (Optional)
If this PR introduces a new feature, it is better to list some use cases here, and update the documentation.
Checklist