Skip to content
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: Do not log warnings about log cleanup when logs_max=0 #6271

Merged
merged 1 commit into from
Mar 22, 2023

Conversation

jmealo
Copy link
Contributor

@jmealo jmealo commented Mar 17, 2023

This PR disables logging warnings for failures to cleanup log files when log files are disabled.

References

Fixes #6270

@jmealo jmealo requested a review from a team as a code owner March 17, 2023 15:25
@jmealo jmealo requested review from nlf and removed request for a team March 17, 2023 15:25
@wraithgar
Copy link
Member

Can you clean up the linting error and add a test?

@jmealo
Copy link
Contributor Author

jmealo commented Mar 22, 2023

@wraithgar: Sure, no problem! The CI was delayed in running for some reason.

@wraithgar
Copy link
Member

CI has to be manually run on PRs from forks. You can run npm install then npm test to run tests locally and if they pass linting will also run.

@jmealo
Copy link
Contributor Author

jmealo commented Mar 22, 2023

@wraithgar: Test added and lint fixed.

@wraithgar wraithgar changed the title Fix #6270: Do not log warnings about log cleanup when logs_max=0 fix: Do not log warnings about log cleanup when logs_max=0 Mar 22, 2023
@jmealo
Copy link
Contributor Author

jmealo commented Mar 22, 2023

@wraithgar: thanks for reviewing. I squashed my commits because of commit lint. 👍

@github-actions github-actions bot mentioned this pull request Mar 22, 2023
@wraithgar
Copy link
Member

@jmealo that's fine, we usually squash when landing PRs like this anyways, and use the PR title. This is what I ended up doing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[BUG] log cleanup procedure runs when logs-max=0 and throws error on permissions but not missing directory
2 participants