Skip to content

Pass the shape when creating a tf.Variable.#22460

Open
hertschuh wants to merge 1 commit intokeras-team:masterfrom
hertschuh:tf_var_shape
Open

Pass the shape when creating a tf.Variable.#22460
hertschuh wants to merge 1 commit intokeras-team:masterfrom
hertschuh:tf_var_shape

Conversation

@hertschuh
Copy link
Collaborator

The value passed can be an initializer and the calling of the initializer may be delayed. Passing the shape immediately when creating the Variable helps in some scenarios, for instance when UninitializedVariable instances are used.

Note that this also works when self._shape is None.

The `value` passed can be an initializer and the calling of the initializer may be delayed. Passing the shape immediately when creating the `Variable` helps in some scenarios, for instance when `UninitializedVariable` instances are used.

Note that this also works when `self._shape` is `None`.
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello, 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 of tf.Variable creation within the Keras TensorFlow backend by ensuring that the variable's shape is immediately available upon instantiation. This is particularly beneficial for handling delayed initializers and UninitializedVariable instances, leading to more predictable and stable variable management.

Highlights

  • TensorFlow Variable Initialization: The tf.Variable constructor now explicitly receives the shape argument during initialization. This change addresses scenarios where the value provided might be an initializer whose execution is delayed, or when dealing with UninitializedVariable instances.

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

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 updates the TensorFlow backend's Variable class to explicitly pass the shape when creating a tf.Variable. This is a good improvement as it helps with scenarios involving deferred initialization, such as with UninitializedVariable instances, by providing the shape information upfront. The implementation correctly handles cases where self._shape is None, relying on TensorFlow's default behavior to infer the shape from the initial value. The change is correct and beneficial.

@codecov-commenter
Copy link

codecov-commenter commented Mar 20, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.08%. Comparing base (88b3c08) to head (6c25c5f).
⚠️ Report is 2 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master   #22460   +/-   ##
=======================================
  Coverage   83.08%   83.08%           
=======================================
  Files         596      596           
  Lines       67337    67337           
  Branches    10491    10491           
=======================================
  Hits        55945    55945           
  Misses       8687     8687           
  Partials     2705     2705           
Flag Coverage Δ
keras 82.91% <ø> (ø)
keras-jax 60.02% <ø> (ø)
keras-numpy 54.30% <ø> (ø)
keras-openvino 50.86% <ø> (ø)
keras-tensorflow 61.26% <ø> (+<0.01%) ⬆️
keras-torch 60.09% <ø> (ø)

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.

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.

4 participants