-
Notifications
You must be signed in to change notification settings - Fork 51
test: syncertest/fake enhancements #2023
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
base: main
Are you sure you want to change the base?
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: 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 |
Summary of ChangesHello @Camila-B, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request significantly refines the Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
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.
Code Review
The pull request introduces significant improvements to the fake cache and watch mechanisms, primarily focusing on enhancing robustness and supporting initial event synchronization. Key changes include correcting a mutex unlock in fake.Cache.Start, refactoring WaitForCacheSync for better modularity, and implementing SendInitialEvents in MemoryStorage.Watch. Additionally, Watcher.handleEvents now gracefully handles empty ResourceVersion strings, and Watcher.sendEvent bypasses list filter validation for Bookmark events. These changes collectively contribute to a more reliable and feature-complete fake client for testing purposes.
| if err != nil { | ||
| return |
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.
In a goroutine, return statements silently discard errors. It's generally better to log errors that occur within goroutines, especially when they indicate a potential issue like failing to create a bookmark object. This ensures that such failures are visible and can be debugged.
Consider logging the error before returning.
bookmarkObj, err := kinds.NewObjectForGVK(gvk, ms.scheme)
if err != nil {
klog.Errorf("Failed to create bookmark object for initial watch events: %v", err)
return
}| if err != nil { | ||
| return |
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.
Similar to the previous comment, silently returning from a goroutine on error can hide important issues. Logging the error here would provide better visibility into potential problems during object conversion.
Consider logging the error before returning.
cObj, err := kinds.ObjectAsClientObject(bookmarkObj)
if err != nil {
klog.Errorf("Failed to convert bookmark object to client object for initial watch events: %v", err)
return
}| rvStr := obj.GetResourceVersion() | ||
| if rvStr != "" { |
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.
Adding a check for an empty ResourceVersion string before attempting to parse it is a good defensive programming practice. This prevents strconv.Atoi from returning an error for valid empty strings, improving the robustness of the watcher.
| rvStr := obj.GetResourceVersion() | |
| if rvStr != "" { | |
| rvStr := obj.GetResourceVersion() | |
| if rvStr != "" { |
| return | ||
| // Check if input object matches list option filters. | ||
| // Skip for Bookmark events, as they may not match filters. | ||
| if event.Type != watch.Bookmark { |
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.
Skipping list filter validation for watch.Bookmark events is a necessary adjustment. Bookmark events often carry metadata rather than full object specifications, and forcing them through object filters could lead to incorrect filtering or errors. This change ensures that Bookmark events are handled appropriately without unintended side effects.
| if event.Type != watch.Bookmark { | |
| if event.Type != watch.Bookmark { |
- Fixed `fake.Cache`: Corrected the Start method's locking logic and updated WaitForCacheSync to properly wait for all informers to synchronize using k8scache.WaitForCacheSync. - Implemented `WatchList` Support: Modified MemoryStorage.Watch to support SendInitialEvents by asynchronously sending synthetic ADDED events for existing objects, followed by a Bookmark event with the k8s.io/initial-events-end: true annotation. - Improved Watcher Robustness: Updated Watcher.handleEvents to gracefully handle empty ResourceVersion strings and modified Watcher.sendEvent to allow Bookmark events to bypass list filter validation.
5ef76b7 to
3696b90
Compare
fake.Cache: Corrected the Start method's locking logic and updated WaitForCacheSync to properly wait for all informers to synchronize using k8scache.WaitForCacheSync.WatchListSupport: Modified MemoryStorage.Watch to support SendInitialEvents by asynchronously sending synthetic ADDED events for existing objects, followed by a Bookmark event with the k8s.io/initial-events-end: true annotation.