-
Notifications
You must be signed in to change notification settings - Fork 1.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
Fix tagger regression behavior with SIX #3767
Conversation
c3a1b17
to
e3e97c9
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.
Purrrfect 😸
Thanks for the fix!
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.
could you add a releasenote ?
@hush-hush release note added |
releasenotes/notes/Fix-tagger-regression-behavior-with-SIX-d1994c01432ff815.yaml
Outdated
Show resolved
Hide resolved
a7fe2f2
to
9bd399e
Compare
You got conflicts because we renamed six to rtloader (sorry, I really thought this had been merged earlier!). Can you rebase and ping me so I give you a ✅ again? |
8b61380
to
1384c6d
Compare
Previously in a python check, a call to the tagger.tag function, always return a list (empty or not). With the introduction of rtloader , in case of the absence of associated tag stored in the tagger, the function returns "NONE" that can break some checks (Kubelet check of instance).
1384c6d
to
39c4c6a
Compare
@albertvaka rebased done :) |
🙇 (and btw, this also makes me realize that the extension should raise a python error instead of returning |
@clamoriniere Should we merge this? |
@albertvaka Yes we can now merge it. |
What does this PR do?
Previously in a python check, a call to the tagger.tag function, always
return a list (empty or not). With the introduction of SIX, in case of
the absence of associated tag stored in the tagger, the function returns
"NONE" that can break some checks (Kubelet check of instance).
This fix restores the previous behavior.
Motivation
What inspired you to submit this pull request?
Additional Notes
Anything else we should know when reviewing?