Skip to content

Conversation

@ohmayr
Copy link
Contributor

@ohmayr ohmayr commented Jan 21, 2026

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

  • Make sure to open an issue as a bug/issue before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
  • Ensure the tests and linter pass
  • Code coverage does not decrease (if any source code was changed)
  • Appropriate docs were updated (if necessary)

Fixes #<issue_number_goes_here> 🦕

@product-auto-label product-auto-label bot added the size: m Pull request size is medium. label Jan 21, 2026
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @ohmayr, 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 implements a significant performance optimization by introducing a caching mechanism for context-aware schema objects. By passing a shared context_cache through the with_context methods, the system can avoid recomputing identical object derivatives, especially those involved in resolving naming collisions. This change aims to reduce processing time and improve the overall efficiency of the GAPIC generator.

Highlights

  • Introduced Context Caching: A context_cache dictionary is now passed through various with_context methods across api.py, metadata.py, and wrappers.py to store and reuse previously computed context-aware objects, preventing redundant calculations.
  • Optimized with_context Calls: The with_context methods in Address, Metadata, Field, MessageType, EnumType, ExtendedOperationInfo, OperationInfo, Method, and Service now check the context_cache before performing computations, returning cached results if available.
  • Early Exit for MessageType: An optimization was added to MessageType.with_context to return the current instance early if the collisions set has not changed, further reducing redundant processing.
  • Global Collisions as Frozenset: In api.py, naive.names is now converted to a frozenset (global_collisions) once and reused, improving efficiency when passed to multiple with_context calls.

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

@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

This pull request introduces a caching mechanism to optimize with_context calls, which is a good idea for performance. However, the implementation has a few issues that need to be addressed: a critical bug in api.py that will cause a runtime error, and several issues with the caching implementation itself regarding type safety, potential cache corruption, and code duplication. My detailed comments point out these issues with suggestions for fixes.

collisions=v.names,
visited_messages=visited_messages,
collisions=global_collisions,
visited_messages=frozenset(v.names),
Copy link
Contributor

Choose a reason for hiding this comment

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

critical

There's a type mismatch here. The visited_messages parameter in with_context expects a Set[wrappers.MessageType], but you are passing frozenset(v.names), which is a frozenset[str]. This will likely lead to a TypeError at runtime inside MessageType.with_context when set operations are performed. The original code passed an empty set of MessageType. To fix this, you should pass an empty set.

Suggested change
visited_messages=frozenset(v.names),
visited_messages=set(),

return selector

def with_context(self, *, collisions: Set[str]) -> "Address":
def with_context(self, *, collisions: Set[str], context_cache: Optional[Dict[tuple, "MessageType"]] = None,) -> "Address":
Copy link
Contributor

Choose a reason for hiding this comment

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

high

The type hint for context_cache is incorrect. It's specified as Optional[Dict[tuple, "MessageType"]], but this method caches and returns an Address object. This same issue exists across all the modified with_context methods in this pull request (in both metadata.py and wrappers.py), where each method caches objects of its own class type. This can lead to type confusion and bugs.

A more accurate type hint would be Optional[Dict[tuple, Any]] to reflect that the cache holds various types. Note that this would require importing Any from typing on line 31.

Suggested change
def with_context(self, *, collisions: Set[str], context_cache: Optional[Dict[tuple, "MessageType"]] = None,) -> "Address":
def with_context(self, *, collisions: Set[str], context_cache: Optional[Dict[tuple, Any]] = None,) -> "Address":

"""
return (
context_cache = context_cache if context_cache is not None else {}
cache_key = (id(self), id(collisions))
Copy link
Contributor

Choose a reason for hiding this comment

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

high

Using id(collisions) as part of the cache key is unsafe because collisions is a mutable Set. If the set is modified elsewhere, its ID remains the same, but its contents change. This can lead to incorrect cache hits, as the logic of with_context depends on the contents of the collisions set. To make caching robust, the cache key should be based on the content of the set, for example by using a frozenset. This issue is present in all with_context methods that have been modified in this PR.

Suggested change
cache_key = (id(self), id(collisions))
cache_key = (id(self), frozenset(collisions))

Comment on lines 369 to 381
context_cache = context_cache if context_cache is not None else {}
cache_key = (id(self), id(collisions))
if cache_key in context_cache:
return context_cache[cache_key]

updated_msg = (
dataclasses.replace(self, collisions=collisions)
if collisions and collisions != self.collisions
else self
)

context_cache[cache_key] = updated_msg
return updated_msg
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

The caching logic here is repeated in many with_context methods across metadata.py and wrappers.py. To improve maintainability and adhere to the DRY (Don't Repeat Yourself) principle, consider refactoring this logic into a reusable decorator. A decorator could encapsulate the caching mechanism, making the with_context methods cleaner and less prone to copy-paste errors.

@ohmayr ohmayr force-pushed the cache-api-context branch from 68e453e to 8e7e903 Compare January 22, 2026 01:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size: m Pull request size is medium.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant