Conversation
Signed-off-by: LogicalShark <maralder@google.com>
|
This issue is currently awaiting triage. If the repository mantainers determine this is a relevant issue, they will accept it by applying the The DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
Hi @LogicalShark. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: LogicalShark The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
| } | ||
| } | ||
|
|
||
| func (ca *cloudCIDRAllocator) processNextItem(ctx context.Context) bool { |
There was a problem hiding this comment.
we should not remove this, it can also be used for context logging
|
too much risk for small ROI IMHO |
|
/ok-to-test Are there any external references? I think this is ok if it is contained entirely within the package. |
|
@LogicalShark: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
|
||
| func (ca *cloudCIDRAllocator) runWorker(ctx context.Context) { | ||
| for ca.processNextItem(ctx) { | ||
| for ca.processNextItem() { |
There was a problem hiding this comment.
I would prefer to make the parameter unamed in processNextItem but keep the context.Context parameter. It is best practice to propagate the Context and we should keep this in case there is a future change that will use it.
InvalidCacheFile is covered by test case cacheFileIsMalformed
nodeReadyPredicate is unused likely due to stableNodeSetPredicates