-
Notifications
You must be signed in to change notification settings - Fork 218
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
Add a log-file-max-size flag to fix large logfile (>1.8GB) truncation. #56
Conversation
e2e05a0
to
e025e58
Compare
/assign @dims |
a77a608
to
651f8e7
Compare
/assign @DirectXMan12 |
Solly, currently when someone uses |
0744b8e
to
f4fdf5e
Compare
@tallclair Refactored the code to precompute the max number. PTAL |
@yuwenma can you please look at the lint error in the CI? |
When did |
(FWIW, I agree that having no limit is probably the expected behavior, but in case anyone is accidentally depending on this behavior, it's probably good to give them at least a release's worth of heads-up) |
@DirectXMan12 Updated the default to be 1800MB. 😃 |
/approve leaving |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dims, tallclair, yuwenma The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What this PR does / why we need it:
Allows klog users to disable the max-size limitation (cleanup log-file when exceeds 1.8GB) when flag log-file is applied.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #55
Special notes for your reviewer:
Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.
Release note: