Skip to content

Upgrade radium to 1.1.1 #5971

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
Jul 14, 2025
Merged

Upgrade radium to 1.1.1 #5971

merged 2 commits into from
Jul 14, 2025

Conversation

youknowone
Copy link
Member

@youknowone youknowone commented Jul 14, 2025

Fix #5768

Summary by CodeRabbit

  • Chores
    • Updated the radium dependency to version 1.1.1 from the official source.
    • Removed custom overrides for the radium crate in multiple project configurations, ensuring all projects now use the standard published version.

Copy link
Contributor

coderabbitai bot commented Jul 14, 2025

Walkthrough

The patch removes custom [patch.crates-io] overrides for the radium crate in multiple Cargo.toml files, which previously pointed to a specific Git repository and branch. Instead, all dependencies now use the published radium crate version 1.1.1 from crates.io. Additionally, an unused import of PyNone is removed in vm/src/vm/mod.rs, replaced by a fully qualified path reference.

Changes

File(s) Change Summary
Cargo.toml Removed [patch.crates-io] for radium; updated dependency to version 1.1.1 from crates.io
example_projects/barebone/Cargo.toml Removed [patch.crates-io] override for radium
example_projects/frozen_stdlib/Cargo.toml Removed [patch.crates-io] override for radium
wasm/wasm-unknown-test/Cargo.toml Removed [patch.crates-io] override for radium
vm/src/vm/mod.rs Removed unused import of PyNone; replaced with fully qualified crate::builtins::PyNone reference

Assessment against linked issues

Objective Addressed Explanation
Remove radium patch override and use compatible crate version to fix nightly build errors (#5768)

Assessment against linked issues: Out-of-scope changes

Code Change Explanation
Removal of unused import and path qualification for PyNone (vm/src/vm/mod.rs) This change is unrelated to the radium patch override issue and the nightly build fix objective.

Poem

A patch removed, a crate set free,
No more overrides for radium, you see!
Nightly builds now run with glee,
Cargo’s path is clear as can be.
🐇✨

Hop, hop, hooray—dependencies fixed today!


📜 Recent review details

Configuration used: .coderabbit.yml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6ba4cc3 and e350a12.

⛔ Files ignored due to path filters (1)
  • Cargo.lock is excluded by !**/*.lock
📒 Files selected for processing (5)
  • Cargo.toml (1 hunks)
  • example_projects/barebone/Cargo.toml (0 hunks)
  • example_projects/frozen_stdlib/Cargo.toml (0 hunks)
  • vm/src/vm/mod.rs (1 hunks)
  • wasm/wasm-unknown-test/Cargo.toml (0 hunks)
💤 Files with no reviewable changes (3)
  • wasm/wasm-unknown-test/Cargo.toml
  • example_projects/barebone/Cargo.toml
  • example_projects/frozen_stdlib/Cargo.toml
🚧 Files skipped from review as they are similar to previous changes (1)
  • Cargo.toml
🧰 Additional context used
📓 Path-based instructions (1)
**/*.rs

Instructions used from:

Sources:
📄 CodeRabbit Inference Engine

  • .github/copilot-instructions.md
🧠 Learnings (1)
vm/src/vm/mod.rs (4)
Learnt from: moreal
PR: RustPython/RustPython#5847
File: vm/src/stdlib/stat.rs:547-567
Timestamp: 2025-06-27T14:47:28.810Z
Learning: In RustPython's stat module implementation, platform-specific constants like SF_SUPPORTED and SF_SYNTHETIC should be conditionally declared only for the platforms where they're available (e.g., macOS), following CPython's approach of optional declaration using #ifdef checks rather than providing fallback values for other platforms.
Learnt from: moreal
PR: RustPython/RustPython#5847
File: vm/src/stdlib/stat.rs:547-567
Timestamp: 2025-06-27T14:47:28.810Z
Learning: In RustPython's stat module implementation, platform-specific constants like SF_SUPPORTED and SF_SYNTHETIC should be conditionally declared only for the platforms where they're available (e.g., macOS), following CPython's approach of optional declaration rather than providing fallback values for other platforms.
Learnt from: CR
PR: RustPython/RustPython#0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-06-30T10:08:48.858Z
Learning: Applies to Lib/**/*.py : Minimize modifications to CPython standard library files in the `Lib/` directory
Learnt from: CR
PR: RustPython/RustPython#0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-06-30T10:08:48.858Z
Learning: Applies to **/*.rs : Use the macro system (`pyclass`, `pymodule`, `pyfunction`, etc.) when implementing Python functionality in Rust
⏰ 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). (11)
  • GitHub Check: Check the WASM package and demo
  • GitHub Check: Run tests under miri
  • GitHub Check: Run snippets and cpython tests (ubuntu-latest)
  • GitHub Check: Check Rust code with rustfmt and clippy
  • GitHub Check: Run rust tests (ubuntu-latest)
  • GitHub Check: Run snippets and cpython tests on wasm-wasi
  • GitHub Check: Run snippets and cpython tests (macos-latest)
  • GitHub Check: Run snippets and cpython tests (windows-latest)
  • GitHub Check: Run rust tests (windows-latest)
  • GitHub Check: Run rust tests (macos-latest)
  • GitHub Check: Ensure compilation on various targets
🔇 Additional comments (1)
vm/src/vm/mod.rs (1)

338-339: LGTM! Good cleanup of unused import.

The change from importing PyNone to using the fully qualified path crate::builtins::PyNone improves code clarity and removes an unused import. This is a good refactoring that makes the code more explicit about where PyNone originates from.

✨ Finishing Touches
  • 📝 Generate Docstrings

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

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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
Cargo.toml (1)

84-87: Empty [patch.crates-io] table can be dropped (optional)

With every override now removed, this table only contains comments. Cargo tolerates an empty table, but deleting it (while keeping the REDOX comments elsewhere) trims a tiny bit of noise and avoids future confusion over whether any patches are active.

📜 Review details

Configuration used: .coderabbit.yml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between eef8890 and 6ba4cc3.

📒 Files selected for processing (4)
  • Cargo.toml (1 hunks)
  • example_projects/barebone/Cargo.toml (0 hunks)
  • example_projects/frozen_stdlib/Cargo.toml (0 hunks)
  • wasm/wasm-unknown-test/Cargo.toml (0 hunks)
💤 Files with no reviewable changes (3)
  • example_projects/barebone/Cargo.toml
  • wasm/wasm-unknown-test/Cargo.toml
  • example_projects/frozen_stdlib/Cargo.toml
🧰 Additional context used
🧠 Learnings (1)
Cargo.toml (1)
Learnt from: CR
PR: RustPython/RustPython#0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-06-30T10:08:48.858Z
Learning: Applies to **/*.rs : Use the macro system (`pyclass`, `pymodule`, `pyfunction`, etc.) when implementing Python functionality in Rust
⏰ 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). (11)
  • GitHub Check: Check the WASM package and demo
  • GitHub Check: Run snippets and cpython tests on wasm-wasi
  • GitHub Check: Run tests under miri
  • GitHub Check: Run rust tests (ubuntu-latest)
  • GitHub Check: Check Rust code with rustfmt and clippy
  • GitHub Check: Ensure compilation on various targets
  • GitHub Check: Run rust tests (macos-latest)
  • GitHub Check: Run snippets and cpython tests (macos-latest)
  • GitHub Check: Run rust tests (windows-latest)
  • GitHub Check: Run snippets and cpython tests (windows-latest)
  • GitHub Check: Run snippets and cpython tests (ubuntu-latest)
🔇 Additional comments (1)
Cargo.toml (1)

190-194: radium bumped to 1.1.1 – looks good

Upgrading to the crates-io release without the git override resolves the nightly-breakage noted in #5768 and keeps the manifest in sync with the rest of the workspace.

@youknowone youknowone merged commit dd4f0c3 into RustPython:main Jul 14, 2025
12 checks passed
@youknowone youknowone deleted the radium-1.1.1 branch July 14, 2025 11:40
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.

nightly build fails due to radium imcompatibility
1 participant