-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
Correctly initialize kv store if storage key missing #3958
Conversation
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
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
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
It looks like this commit might have introduced a bug (I'm new to the code, so I might be wrong): e4bb506#diff-89592b0a96bd24ccd41291548f9a07a3 On line 88, keyExists will return an error ErrKeyNotFound if the key does not exists, because keyExists seems to not check if a key exists, but if a key is empty.
Great, thanks for the quick review and merge! What is the usual timeframe between path review (like 1.7.2 which will have the fix)? Going to use the containous/traefik image in the meantime to continue my tests. |
What does this PR do?
It looks like this commit might have introduced a bug
(I'm new to the code, so I might be wrong):
e4bb506#diff-89592b0a96bd24ccd41291548f9a07a3
On line 88, keyExists will return an error ErrKeyNotFound if the key does not exists,
because keyExists seems to not check if a key exists, but if a key is empty.
Motivation
More
Additional Notes