Skip to content

Conversation

@njzjz
Copy link
Member

@njzjz njzjz commented Jul 31, 2025

Remove version >=a.b.crc0 from dependencies. The stable version should be preferred.
This prevents the installation of TensorFlow 2.20.0rc0, which breaks the CI. However, the incompatibility should still be fixed in the future. TensorFlow 2.20.0rc0 removes the version information from the header files.

Summary by CodeRabbit

  • Chores
    • Updated version requirements for TensorFlow and myst-nb packages to use stable releases instead of release candidate versions in build and documentation workflows.
    • Adjusted dependency handling for TensorFlow CPU to ensure stable versions are used during build processes.

Remove version `>=a.b.crc0` from dependencies. The stable version should be preferred.
This prevents the installation of TensorFlow 2.20.0rc0 which breaks the CI. However, the incompatibility should still be fixed in the future.

Signed-off-by: Jinzhe Zeng <jinzhe.zeng@ustc.edu.cn>
Copilot AI review requested due to automatic review settings July 31, 2025 12:19
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR removes release candidate (rc0) version specifiers from dependency declarations to prevent installation of unstable pre-release versions. The change addresses a CI breakage caused by TensorFlow 2.20.0rc0 which removed version information from header files.

  • Remove rc0 suffixes from version constraints in dependency specifications
  • Update TensorFlow CPU version requirements to use stable releases only
  • Modify documentation dependency to use stable myst-nb version

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File Description
pyproject.toml Updates myst-nb dependency to use stable version >=1.0.0 instead of >=1.0.0rc0
backend/find_tensorflow.py Removes rc0 from TensorFlow CPU version constraints for both CUDA 12.x and 11.x configurations
.github/workflows/package_c.yml Updates TensorFlow version constraint in CI workflow to exclude release candidates

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jul 31, 2025

📝 Walkthrough

Walkthrough

This change updates version constraints by removing "rc0" (release candidate) suffixes from TensorFlow and myst-nb dependencies in the CI workflow, backend environment checks, and documentation requirements. No logic or control flow is altered, and no public interfaces are changed.

Changes

Cohort / File(s) Change Summary
CI Workflow TensorFlow Version Constraint
.github/workflows/package_c.yml
Updated TensorFlow version constraint in build matrix from ">=2.5.0rc0" to ">=2.5.0".
Backend TensorFlow CPU Requirement
backend/find_tensorflow.py
Removed "rc0" suffix from TensorFlow CPU requirements for CUDA 12.2 and 11.x in environment detection.
Docs Dependency Version
pyproject.toml
Changed "myst-nb" docs dependency from ">=1.0.0rc0" to ">=1.0.0".

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~6 minutes

Possibly related PRs

Suggested reviewers

  • wanghan-iapcm

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 43504d3 and 11df4cd.

📒 Files selected for processing (3)
  • .github/workflows/package_c.yml (1 hunks)
  • backend/find_tensorflow.py (1 hunks)
  • pyproject.toml (1 hunks)
🧰 Additional context used
🧠 Learnings (1)
📓 Common learnings
Learnt from: njzjz
PR: deepmodeling/deepmd-kit#4144
File: source/api_cc/tests/test_deeppot_dpa_pt.cc:166-246
Timestamp: 2024-09-19T04:25:12.408Z
Learning: Refactoring between test classes `TestInferDeepPotDpaPt` and `TestInferDeepPotDpaPtNopbc` is addressed in PR #3905.
Learnt from: njzjz
PR: deepmodeling/deepmd-kit#4144
File: source/api_cc/tests/test_deeppot_dpa_pt.cc:166-246
Timestamp: 2024-10-08T15:32:11.479Z
Learning: Refactoring between test classes `TestInferDeepPotDpaPt` and `TestInferDeepPotDpaPtNopbc` is addressed in PR #3905.
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (29)
  • GitHub Check: Test Python (6, 3.12)
  • GitHub Check: Test Python (6, 3.9)
  • GitHub Check: Test Python (4, 3.12)
  • GitHub Check: Test Python (5, 3.9)
  • GitHub Check: Test Python (5, 3.12)
  • GitHub Check: Build wheels for cp311-manylinux_x86_64
  • GitHub Check: Build wheels for cp311-macosx_x86_64
  • GitHub Check: Test Python (2, 3.9)
  • GitHub Check: Test Python (3, 3.9)
  • GitHub Check: Test Python (1, 3.9)
  • GitHub Check: Test Python (2, 3.12)
  • GitHub Check: Test Python (4, 3.9)
  • GitHub Check: Test Python (3, 3.12)
  • GitHub Check: Test Python (1, 3.12)
  • GitHub Check: Build wheels for cp310-manylinux_aarch64
  • GitHub Check: Build wheels for cp311-win_amd64
  • GitHub Check: Build wheels for cp311-macosx_arm64
  • GitHub Check: Build wheels for cp311-manylinux_x86_64
  • GitHub Check: Analyze (c-cpp)
  • GitHub Check: Analyze (python)
  • GitHub Check: Build C++ (clang, clang)
  • GitHub Check: Build C++ (cuda120, cuda)
  • GitHub Check: Build C++ (cuda, cuda)
  • GitHub Check: Build C++ (cpu, cpu)
  • GitHub Check: Build C++ (rocm, rocm)
  • GitHub Check: Build C library (2.14, >=2.5.0,<2.15, libdeepmd_c_cu11.tar.gz)
  • GitHub Check: Test C++ (false)
  • GitHub Check: Test C++ (true)
  • GitHub Check: Build C library (2.18, libdeepmd_c.tar.gz)
🔇 Additional comments (4)
pyproject.toml (1)

93-93: LGTM! Correctly removes release candidate suffix.

The change from myst-nb>=1.0.0rc0 to myst-nb>=1.0.0 properly ensures that only stable versions are preferred, aligning with the PR objective to avoid release candidate versions that could break CI.

backend/find_tensorflow.py (2)

91-91: LGTM! Correctly removes TensorFlow release candidate suffix for CUDA 12.2.

The change from tensorflow-cpu>=2.18.0rc0 to tensorflow-cpu>=2.18.0 ensures stable TensorFlow versions are used, preventing issues with release candidates like TensorFlow 2.20.0rc0 that break CI.


98-98: LGTM! Correctly removes TensorFlow release candidate suffix for CUDA 11.x.

The change from tensorflow-cpu>=2.5.0rc0,<2.15 to tensorflow-cpu>=2.5.0,<2.15 maintains the upper bound constraint while ensuring only stable versions are preferred, consistent with the PR's goal to avoid problematic release candidates.

.github/workflows/package_c.yml (1)

25-25: LGTM! Maintains consistency with backend TensorFlow detection.

The change from >=2.5.0rc0,<2.15 to >=2.5.0,<2.15 correctly removes the release candidate suffix and aligns with the corresponding change in backend/find_tensorflow.py line 98, ensuring consistent TensorFlow version requirements across the build environment detection and CI workflow.

✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@njzjz njzjz requested a review from wanghan-iapcm July 31, 2025 12:26
@codecov
Copy link

codecov bot commented Jul 31, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 84.77%. Comparing base (43504d3) to head (11df4cd).
⚠️ Report is 79 commits behind head on devel.

Additional details and impacted files
@@           Coverage Diff           @@
##            devel    #4857   +/-   ##
=======================================
  Coverage   84.76%   84.77%           
=======================================
  Files         699      699           
  Lines       68077    68077           
  Branches     3541     3542    +1     
=======================================
+ Hits        57708    57709    +1     
  Misses       9235     9235           
+ Partials     1134     1133    -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.

@njzjz njzjz added this pull request to the merge queue Aug 1, 2025
Merged via the queue into deepmodeling:devel with commit dbc6d7b Aug 1, 2025
60 checks passed
@njzjz njzjz deleted the install_stabe branch August 1, 2025 12:17
ChiahsinChu pushed a commit to ChiahsinChu/deepmd-kit that referenced this pull request Dec 17, 2025
Remove version `>=a.b.crc0` from dependencies. The stable version should
be preferred.
This prevents the installation of TensorFlow 2.20.0rc0, which breaks the
CI. However, the incompatibility should still be fixed in the future.
TensorFlow 2.20.0rc0 removes the version information from the header
files.

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **Chores**
* Updated version requirements for TensorFlow and myst-nb packages to
use stable releases instead of release candidate versions in build and
documentation workflows.
* Adjusted dependency handling for TensorFlow CPU to ensure stable
versions are used during build processes.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

Signed-off-by: Jinzhe Zeng <jinzhe.zeng@ustc.edu.cn>
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.

2 participants