Skip to content

Version bump 3.11.2 and nnx fix #21565 #21570

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

Merged
merged 2 commits into from
Aug 11, 2025

Conversation

laxmareddyp
Copy link
Collaborator

No description provided.

divyashreepathihalli and others added 2 commits August 11, 2025 18:41
* Update operation.py

* Update actions.yml

* Update operation.py

* Update actions.yml

* Update operation.py

* Update operation.py

* Update operation.py

* fix test

* code reformat
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.

Summary of Changes

Hello @laxmareddyp, 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 primarily focuses on updating the Keras project version to 3.11.2. It also includes an important fix for the JAX backend, specifically addressing how state is initialized when NNX is enabled, ensuring better compatibility and stability. Additionally, a minor syntax error in an example within the operation.py file has been corrected.

Highlights

  • Version Update: The Keras project version has been updated from 3.11.1 to 3.11.2, reflecting recent changes and preparing for new releases.
  • JAX/NNX Integration Fix: A fix has been implemented in keras/src/ops/operation.py to improve compatibility with the JAX backend when NNX (Neural Networks eXtensions for JAX/Flax) is enabled. This involves a more resilient state initialization mechanism.
  • Syntax Correction: A small syntax correction was made in keras/src/ops/operation.py to fix an extraneous set of curly braces in a get_config method example.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 bumps the package version to 3.11.2 and includes a fix for compatibility with different versions of flax.nnx. My review focuses on improving the robustness of the nnx fix and correcting a formatting issue in an error message.

Specifically, I've suggested replacing a try-except block with hasattr checks for more explicit and safer version handling of the flax dependency. I also pointed out and suggested a fix for incorrect indentation in an example code snippet within an error message to improve its readability.

Comment on lines +126 to +129
try:
vars(instance)["_pytree__state"] = nnx.pytreelib.PytreeState()
except AttributeError:
vars(instance)["_object__state"] = nnx.object.ObjectState()
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 use of a broad try...except AttributeError block can be brittle. It might catch an AttributeError from an unexpected source within the PytreeState() call, potentially masking other issues. A more explicit check for the existence of nnx.pytreelib.PytreeState using hasattr would be more robust and clearer about the intent, which is to handle different versions of the flax library.

Suggested change
try:
vars(instance)["_pytree__state"] = nnx.pytreelib.PytreeState()
except AttributeError:
vars(instance)["_object__state"] = nnx.object.ObjectState()
if hasattr(nnx, "pytreelib") and hasattr(nnx.pytreelib, "PytreeState"):
vars(instance)["_pytree__state"] = nnx.pytreelib.PytreeState()
else:
vars(instance)["_object__state"] = nnx.object.ObjectState()

@codecov-commenter
Copy link

codecov-commenter commented Aug 11, 2025

Codecov Report

❌ Patch coverage is 20.00000% with 4 lines in your changes missing coverage. Please review.
✅ Project coverage is 82.71%. Comparing base (0e11071) to head (5fdfe07).

Files with missing lines Patch % Lines
keras/src/ops/operation.py 0.00% 4 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##            r3.11   #21570      +/-   ##
==========================================
- Coverage   82.72%   82.71%   -0.01%     
==========================================
  Files         567      567              
  Lines       56264    56267       +3     
  Branches     8797     8797              
==========================================
  Hits        46544    46544              
- Misses       7562     7565       +3     
  Partials     2158     2158              
Flag Coverage Δ
keras 82.52% <20.00%> (-0.01%) ⬇️
keras-jax 63.93% <20.00%> (-0.01%) ⬇️
keras-numpy 58.40% <20.00%> (-0.01%) ⬇️
keras-openvino 34.56% <20.00%> (-0.01%) ⬇️
keras-tensorflow 64.35% <20.00%> (-0.01%) ⬇️
keras-torch 63.98% <20.00%> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ 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.

@google-ml-butler google-ml-butler bot added kokoro:force-run ready to pull Ready to be merged into the codebase labels Aug 11, 2025
@sachinprasadhs sachinprasadhs merged commit 251ac34 into keras-team:r3.11 Aug 11, 2025
11 of 12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready to pull Ready to be merged into the codebase size:S
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants