-
Notifications
You must be signed in to change notification settings - Fork 38.6k
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
refactor: rename SchedulerCache to Cache in Scheduler #108269
refactor: rename SchedulerCache to Cache in Scheduler #108269
Conversation
@kerthcet: This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The Instructions 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/test-infra repository. |
/sig scheduling |
can you also change schedulerCache to cacheImpl? |
1a40fde
to
edbe104
Compare
/retest |
return &framework.ImageStateSummary{ | ||
Size: state.size, | ||
NumNodes: len(state.nodes), | ||
} | ||
} | ||
|
||
func newSchedulerCache(ttl, period time.Duration, stop <-chan struct{}) *schedulerCache { | ||
return &schedulerCache{ | ||
func newSchedulerCache(ttl, period time.Duration, stop <-chan struct{}) *cacheImpl { |
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.
newSchedulerCache
--> newCacheImpl
or just newCache
?
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.
At first, I renamed this to newCacheImpl
, but then I realized it's just one implementation, so I changed back. newCache
seems good to me.
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
Signed-off-by: kerthcet <kerthcet@gmail.com>
Signed-off-by: kerthcet <kerthcet@gmail.com>
f773676
to
eafbaad
Compare
As this pr promoted faster, I'd like to merge this first. cc @ruquanzhao , you may have to rebase your pr then. |
/retest |
Squash ? |
I'd like to keep two commits here as they are independent. Make sense? |
All good /lgtm |
Approve is also needed. 😄 |
I already approved. You are missing one from test owners |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alculquicondor, aojea, kerthcet 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 |
/retest |
Signed-off-by: kerthcet kerthcet@gmail.com
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Refactoring for idiomatic Go code
Which issue(s) this PR fixes:
Fixes #108240
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: