Skip to content
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

adding rust to docs #8937

Merged
merged 1 commit into from
Jan 30, 2025
Merged

adding rust to docs #8937

merged 1 commit into from
Jan 30, 2025

Conversation

Eldies
Copy link
Contributor

@Eldies Eldies commented Jan 13, 2025

Motivation and context

Rust is now among dependencies due to #8923
Adding it to docs

How has this been tested?

Checklist

  • I submit my changes into the develop branch
  • I have created a changelog fragment
  • I have updated the documentation accordingly
  • I have added tests to cover my changes
  • I have linked related issues (see GitHub docs)
  • I have increased versions of npm packages if it is necessary
    (cvat-canvas,
    cvat-core,
    cvat-data and
    cvat-ui)

License

  • I submit my code changes under the same MIT License that covers the project.
    Feel free to contact the maintainers if that's a concern.

Summary by CodeRabbit

  • Documentation
    • Updated development environment setup instructions for Ubuntu, MacOS, and Arch Linux
    • Added cargo and rust packages to installation dependencies for improved development environment configuration

Copy link
Contributor

coderabbitai bot commented Jan 13, 2025

Walkthrough

The pull request updates the development environment setup instructions for multiple operating systems. The changes focus on adding cargo and rust packages to the installation dependencies for Ubuntu, MacOS, and Arch Linux. These modifications aim to ensure developers have the necessary tools and runtime for the project's development environment across different platforms.

Changes

File Change Summary
site/content/en/docs/contributing/development-environment.md Updated package lists for Ubuntu, MacOS, and Arch Linux to include cargo and rust

Poem

🐰 A Rusty Development Tale 🦀

With Cargo and Rust now in sight,
Our dev setup shines ever so bright
Ubuntu, MacOS, Arch align
Tools ready, code will now shine
A rabbit's guide to coding delight!


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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.
    • Generate unit testing code for this file.
    • 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 generate unit testing code for this file.
    • @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 generate unit testing code.
    • @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.

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. (Beta)
  • @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.

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

🔭 Outside diff range comments (1)
site/content/en/docs/contributing/development-environment.md (1)

Line range hint 15-41: Add Rust version requirements and setup verification steps

Since Rust is being added as a requirement, it would be helpful to:

  1. Specify the minimum required Rust version
  2. Add verification steps for the Rust installation

Consider adding the following section after the package installation steps:

- Verify Rust installation:
  ```bash
  rustc --version  # Should be 1.x.x or higher
  cargo --version

</blockquote></details>

</blockquote></details>

<details>
<summary>🧹 Nitpick comments (3)</summary><blockquote>

<details>
<summary>site/content/en/docs/contributing/development-environment.md (3)</summary><blockquote>

`15-15`: **Consider adding rustup for better Rust toolchain management**

While `cargo` is included, consider recommending `rustup` for better Rust toolchain management. This would align with Rust's official installation recommendations.

```diff
- sudo apt-get update && sudo apt-get --no-install-recommends install -y build-essential curl git redis-server python3-dev python3-pip python3-venv python3-tk libldap2-dev libsasl2-dev cargo
+ sudo apt-get update && sudo apt-get --no-install-recommends install -y build-essential curl git redis-server python3-dev python3-pip python3-venv python3-tk libldap2-dev libsasl2-dev
+ curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh

28-28: Ensure consistent Rust installation approach across OS

MacOS uses rust from Homebrew while Ubuntu uses cargo. Consider using rustup for MacOS as well for consistency.

- brew install git python pyenv redis curl openssl node sqlite3 geos rust
+ brew install git python pyenv redis curl openssl node sqlite3 geos
+ curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh

41-41: Align Rust installation with other OS instructions

Arch Linux uses the system package manager for Rust. Consider using rustup here as well for consistency across all platforms.

- sudo pacman -S base-devel curl git redis cmake gcc python python-pip tk libldap libsasl pkgconf ffmpeg geos openldap rust
+ sudo pacman -S base-devel curl git redis cmake gcc python python-pip tk libldap libsasl pkgconf ffmpeg geos openldap
+ curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between af8bfe3 and 23a78b8.

📒 Files selected for processing (1)
  • site/content/en/docs/contributing/development-environment.md (3 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (4)
  • GitHub Check: generate_github_pages
  • GitHub Check: Analyze (python)
  • GitHub Check: Analyze (javascript)
  • GitHub Check: Linter

@zhiltsov-max zhiltsov-max merged commit dcbe07e into develop Jan 30, 2025
16 checks passed
@zhiltsov-max zhiltsov-max deleted the dl/cargo-docs branch January 30, 2025 10:21
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