-
Notifications
You must be signed in to change notification settings - Fork 35
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: multiple filters #173
Conversation
bbd072a
to
3b148ac
Compare
3b148ac
to
6d74436
Compare
a014101
to
fa3872d
Compare
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.
LGTM, I added one comment just to check I'm understanding the error chain well.
fa3872d
to
a1ad992
Compare
a1ad992
to
310563f
Compare
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.
LGTM; just a suggestion in the docs
Thanks!
310563f
to
ecfe940
Compare
Fix multiple filters which was only applying the removal of the last iterated set. Add tests to validate that: * Multiple filters are correctly processed * Duplicate filters are correctly ignored * Immediate shutdown occurs if no clients This increasing code coverage to 89.4%. Use best effort in removal if resource changes are detected after a shutdown has been signalled to allow as much to be cleaned up as possible. This includes a new setting ChangesRetryInterval exposed by the env variable RYUK_CHANGES_RETRY_INTERVAL and defaults to 1 second which is used to control the interval between retries if resource changes are detected.
ecfe940
to
37c3a18
Compare
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.
LGTM, thanks!
Fix multiple filters which was only applying the removal of the last iterated set.
Add tests to validate that:
This increasing code coverage to 89.4%.
Use best effort in removal if resource changes are detected after a shutdown has been signalled to allow as much to be cleaned up as possible.
This includes a new setting
ChangesRetryInterval
exposed by the env variableRYUK_CHANGES_RETRY_INTERVAL
and defaults to 1 second which is used to control the interval between retries if resource changes are detected.