bugfix: remove max-size >=2 condition #2958
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: zhangyue <zy675793960@yeah.net>
Codecov Report
|
|
@ZYecho could you please repush it again? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: zhangyue zy675793960@yeah.net
Ⅰ. Describe what this PR did
no need this condition， because we can still do logrotate when max-file = 1
Ⅱ. Does this pull request fix one issue?
NONE
Ⅲ. Why don't you add test cases (unit test/integration test)? (你真的觉得不需要加测试吗？)
NONE
Ⅳ. Describe how to verify it
step1. launch pouchd with max-size and max-file flags
pouchd --log-opt max-size=10kstep2. run a container which could write stdout to its log
pouch run docker.io/library/busybox:latest topstep3. check container log is rotated
Ⅴ. Special notes for reviews
none