-
-
Notifications
You must be signed in to change notification settings - Fork 9.7k
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
[Release-2.10] fix: resolve errors caused by blank annotations #4799
[Release-2.10] fix: resolve errors caused by blank annotations #4799
Conversation
Codecov Report
@@ Coverage Diff @@
## release-2.10 #4799 +/- ##
===============================================
Coverage 61.54% 61.54%
Complexity 2797 2797
===============================================
Files 403 403
Lines 14736 14736
Branches 1026 1026
===============================================
Hits 9069 9069
Misses 5172 5172
Partials 495 495 |
d658e70
to
4cf9a79
Compare
经过验证,该问题可能与 在 #4702 中重构了 由于 /hold |
目前已经可以删除报错的重复 key。 |
/unhold |
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.
如果当前修改应用到 main 分支后,不影响功能的话,建议同时应用到 main 分支。
是不是可以修改一下 PR 的标题和描述了。 |
修改过后的可以应用到 main 分支了。 |
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.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ruibaby The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
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
What type of PR is this?
/kind bug
/area console
/milestone 2.10.x
What this PR does / why we need it:
重构去重元数据的逻辑,解决删除元数据后仍旧提示 key 不能重复的问题。
How to test it?
Which issue(s) this PR fixes:
Fixes #4764
Does this PR introduce a user-facing change?