Skip to content

Conversation

@Camila-B
Copy link
Contributor

@Camila-B Camila-B commented Jan 26, 2026

  • 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.
  • Needed by chore: bump sigs.k8s.io/controller-runtime from 0.22.4 to 0.23.0 #2008

@google-oss-prow
Copy link

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from camila-b. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@gemini-code-assist
Copy link

Summary of Changes

Hello @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 fake.Cache and MemoryStorage components, which are instrumental for testing and simulating Kubernetes client-go behaviors. The changes address a critical locking bug, enhance cache synchronization logic for better reliability, and introduce comprehensive support for SendInitialEvents in watch operations, aligning the fake storage more closely with Kubernetes API server watch semantics. Additionally, it bolsters watcher robustness by handling edge cases like empty resource versions and ensuring that bookmark events are correctly processed without being inadvertently filtered.

Highlights

  • Cache Locking Fix: Corrected a critical locking issue in the fake.Cache.Start method by changing a defer c.mux.RLock() to defer c.mux.RUnlock(), preventing potential deadlocks.
  • Improved Cache Synchronization: Enhanced fake.Cache.WaitForCacheSync to leverage k8scache.WaitForCacheSync, ensuring more robust and standard synchronization for informers.
  • WatchList Support with Initial Events: Implemented SendInitialEvents support in MemoryStorage.Watch, allowing it to asynchronously send synthetic ADDED events for existing objects and conclude with a Bookmark event annotated with k8s.io/initial-events-end: true.
  • Watcher Robustness for ResourceVersion: Improved Watcher.handleEvents to gracefully handle empty ResourceVersion strings, preventing errors when objects might not have this field set.
  • Bookmark Event Filter Bypass: Modified Watcher.sendEvent to allow Bookmark events to bypass list filter validation, ensuring these crucial synchronization markers are always processed.

🧠 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 Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

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

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a 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.

Comment on lines 1082 to 1084
if err != nil {
return

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

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
            }

Comment on lines 1086 to 1089
if err != nil {
return

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

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
            }

Comment on lines +257 to +258
rvStr := obj.GetResourceVersion()
if rvStr != "" {

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

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.

Suggested change
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 {

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

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.

Suggested change
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.
@Camila-B Camila-B changed the title test: Update fake.cache test: syncertest/fake enhancements Jan 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant