Skip to content

Conversation

ILCSFNO
Copy link
Contributor

@ILCSFNO ILCSFNO commented Oct 3, 2025

Fixes #21717

Copy link
Contributor

Summary of Changes

Hello @ILCSFNO, 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 focuses on enhancing the clarity of the Keras API documentation. Specifically, it addresses an ambiguity in the keras.layers.dot() function by adding a crucial detail to the axes parameter's description. This change aims to guide users more effectively, ensuring they understand the valid range for the axes argument and thereby preventing common errors related to axis specification.

Highlights

  • Documentation Clarity: Improved the docstring for the axes parameter in keras.layers.dot() to explicitly state that 0 should not be included, enhancing user understanding and preventing potential misuse.
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 helpful clarification to the keras.layers.dot function's docstring, indicating that axis 0 cannot be used for the dot product. I've provided a suggestion to improve the wording for better clarity and to provide more context to the user.

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
@codecov-commenter
Copy link

codecov-commenter commented Oct 3, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.60%. Comparing base (3fac66f) to head (be714ad).

Additional details and impacted files
@@           Coverage Diff           @@
##           master   #21718   +/-   ##
=======================================
  Coverage   82.60%   82.60%           
=======================================
  Files         572      572           
  Lines       58326    58326           
  Branches     9134     9134           
=======================================
  Hits        48179    48179           
  Misses       7817     7817           
  Partials     2330     2330           
Flag Coverage Δ
keras 82.40% <ø> (ø)
keras-jax 63.31% <ø> (ø)
keras-numpy 57.66% <ø> (+<0.01%) ⬆️
keras-openvino 34.31% <ø> (ø)
keras-tensorflow 64.05% <ø> (ø)
keras-torch 63.64% <ø> (ø)

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.

Copy link
Collaborator

@hertschuh hertschuh left a comment

Choose a reason for hiding this comment

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

Thanks for the PR!

inputs: A list of input tensors (at least 2).
axes: Integer or tuple of integers,
axis or axes along which to take the dot product.
Note that axis `0` (the batch axis) cannot be included.
Copy link
Collaborator

Choose a reason for hiding this comment

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

Please also add line 229 (class Dot) and line 43 (batch_dot).

@google-ml-butler google-ml-butler bot added kokoro:force-run ready to pull Ready to be merged into the codebase labels Oct 6, 2025
@fchollet
Copy link
Collaborator

fchollet commented Oct 6, 2025

Please also add line 229 (class Dot) and line 43 (batch_dot).

+1

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:XS
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add the description that 0 should not in the arg axes in keras.layers.dot()
6 participants