Skip to content

Conversation

@keyuchen21
Copy link
Contributor

Summary

Fixes #735

This PR adds a null check for the session_key argument in KvawareRouter.__init__().

Problem

When users run kvaware routing without specifying --session-key, the router fails with an unclear error because session_key is accessed without validation.

Solution

Added a null check that raises a clear ValueError if session_key is None, matching the existing behavior in SessionRouter:

if session_key is None:
    raise ValueError("KvawareRouter must be initialized with a session_key")

Testing

  • Verified syntax is correct
  • The fix follows the same pattern used in SessionRouter (line 191-192)

Fixes vllm-project#735

When users run kvaware routing without specifying --session-key,
the router would fail with an unclear error. This adds a null check
with a descriptive error message, matching the behavior of SessionRouter.

Signed-off-by: Keyu Chen <54015474+keyuchen21@users.noreply.github.com>
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @keyuchen21, 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 enhances the robustness and user experience of the KvawareRouter by addressing a potential runtime issue. Previously, the router would fail with an unclear error if the session_key was not provided during initialization. This change introduces explicit validation, ensuring that users receive an immediate and informative ValueError when session_key is missing, aligning its behavior with similar components like SessionRouter.

Highlights

  • Null Check Implementation: Implemented a null check for the session_key argument within the KvawareRouter.__init__() method.
  • Improved Error Handling: If session_key is None, a ValueError is now raised with a clear message, preventing obscure errors and aligning with SessionRouter's behavior.

🧠 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 adds a necessary null check for the session_key in KvawareRouter.__init__, preventing potential runtime errors when it's not provided. The change is consistent with the validation already present in SessionRouter. I've suggested also adding a similar check for lmcache_controller_port to further improve the robustness of the initializer, as it seems to be susceptible to the same issue.

@zerofishnoodles
Copy link
Collaborator

zerofishnoodles commented Jan 22, 2026

Hi, Can you confirm this error still exists?

@keyuchen21
Copy link
Contributor Author

keyuchen21 commented Jan 24, 2026

@zerofishnoodles

image

@zerofishnoodles
Copy link
Collaborator

Thanks for the screenshot. I meant will there be an error without this PR. Because kvaware router doesn't have to have a session key.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bug: session_key args has no null check

2 participants