fix: skip duplicate namespace updates - #21
Merged
Merged
Conversation
ianlewis
reviewed
Apr 21, 2026
ianlewis
left a comment
ianlewis
left a comment
Contributor
There was a problem hiding this comment.
My understanding is that the log message appeared because we received a namespace update that had an identical list of namespace names. That should be fixed by your use of Swap.
Was there a separate issue with the timer?
Contributor
|
BTW, this should fix #20 |
Co-authored-by: Ian Lewis <ian@ianlewis.org>
Ladicle
commented
Apr 22, 2026
Co-authored-by: Aya Igarashi <Ladiclexxx@gmail.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
why
The reloader could repeatedly show
Namespace update received; scheduling restartlogs even when namespace label events did not change the watched namespace set.Fix
#20