fix: avoid spamming SyncPackage and InstallPackageRevision events#4934
Conversation
982b918 to
5202ef2
Compare
jbw976
left a comment
There was a problem hiding this comment.
is this a regression from previous releases? 🤔
@jbw976 My guess would be no. I suspect using pull: Always is uncommon, which is why we haven't noticed this before. |
Nope, 1.13.2 emits 1 InstallPackageRevision per minute too with packagePullPolicy set to Always. 1.12 will too. I'll set backport labels for both of them. |
Signed-off-by: Philippe Scorsolini <p.scorsolini@gmail.com>
5202ef2 to
37e8ce4
Compare
My personal preference is to not take changes (and churn) this late before the release, esp. if the code is a common/hot path but it isn't affecting a common user scenarios. But the maintainer team can have final say about including in v1.14 or not 🙇 |
|
Successfully created backport PR for |
|
Successfully created backport PR for |
|
Successfully created backport PR for |
Description of your changes
Fixes #4933
I have:
make reviewableto ensure this PR is ready for review.Added or updated unit tests.Added or updated e2e tests.Linked a PR or a docs tracking issue to document this change.backport release-x.ylabels to auto-backport this PR.Need help with this checklist? See the cheat sheet.