Skip to content

memcache - feat: (breaking) moving to nodes based on memcache options#1849

Merged
jaredwray merged 6 commits intomainfrom
memcache---feat-(breaking)-moving-to-nodes-based-on-memcache-options
Feb 17, 2026
Merged

memcache - feat: (breaking) moving to nodes based on memcache options#1849
jaredwray merged 6 commits intomainfrom
memcache---feat-(breaking)-moving-to-nodes-based-on-memcache-options

Conversation

@jaredwray
Copy link
Owner

@jaredwray jaredwray commented Feb 17, 2026

Please check if the PR fulfills these requirements

  • Followed the Contributing and Code of Conduct guidelines.
  • Tests for the changes have been added (for bug fixes/features) with 100% code coverage.

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
memcache - feat: (breaking) moving to nodes based on memcache options

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @jaredwray, 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 introduces a breaking change to the KeyvMemcache adapter by refactoring its configuration to align with the underlying memcache client library. The primary change involves moving from url and uri based server configuration to a nodes array, simplifying how Memcache server addresses and other client options are passed. This update enhances flexibility and consistency in configuring the Memcache store.

Highlights

  • Type Definition Refactor: The KeyvMemcacheOptions type was updated to directly extend MemcacheOptions, removing url and expires properties and introducing a namespace property. This is a breaking change.
  • Connection Configuration Logic: The KeyvMemcache constructor now uses the nodes property from MemcacheOptions for server addresses, providing a more direct and flexible way to configure Memcache connections.
  • Memcache Client Initialization: The underlying Memcache client is now initialized by directly passing all memcacheOptions, allowing full utilization of the memcache library's configuration capabilities.
Changelog
  • storage/memcache/src/index.ts
    • Refactored KeyvMemcacheOptions type to extend MemcacheOptions directly and removed url and expires properties.
    • Updated the KeyvMemcache constructor to process nodes from MemcacheOptions for server connections.
    • Simplified Memcache client instantiation to pass memcacheOptions directly.
  • storage/memcache/test/test.ts
    • Modified the default connection test to assert on nodes instead of url.
    • Added comprehensive tests for various KeyvMemcache constructor scenarios, including string URIs, nodes arrays, and passing timeout, keepAlive, and retries options.
Activity
  • No specific activity (comments, reviews, progress) was provided in the context.
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 significantly improves the KeyvMemcache adapter by aligning its options with the underlying memcache library, moving from url/uri to nodes based configuration. While this change makes the adapter more intuitive and includes thorough tests, a critical security-relevant logic bug was identified in the constructor. The namespace option is ignored, potentially leading to data isolation failures between different namespaces sharing the same Memcached server. Additionally, there's a suggestion to make the constructor logic even more concise and readable.

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1c5756e6b5

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@codecov
Copy link

codecov bot commented Feb 17, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.95%. Comparing base (4ea0e3e) to head (b0fbb98).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1849      +/-   ##
==========================================
- Coverage   99.95%   99.95%   -0.01%     
==========================================
  Files          32       32              
  Lines        2437     2434       -3     
  Branches      440      440              
==========================================
- Hits         2436     2433       -3     
  Misses          1        1              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@jaredwray jaredwray merged commit 8159300 into main Feb 17, 2026
8 of 9 checks passed
@jaredwray jaredwray deleted the memcache---feat-(breaking)-moving-to-nodes-based-on-memcache-options branch February 17, 2026 08:36
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.

1 participant