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

doc: clarify protoc requirements #114

Merged
merged 1 commit into from
Nov 27, 2024
Merged

doc: clarify protoc requirements #114

merged 1 commit into from
Nov 27, 2024

Conversation

lklimek
Copy link
Collaborator

@lklimek lklimek commented Nov 27, 2024

Issue being fixed or feature implemented

protoc must be installed from the github releases page. People try to use protoc from Ubuntu, and fail. Refs #108 #109

What was done?

Clarified docs

How Has This Been Tested?

N/A

Breaking Changes

None

Checklist:

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have added or updated relevant unit/integration/functional/e2e tests
  • I have made corresponding changes to the documentation

For repository code-owners and collaborators only

  • I have assigned this pull request to a milestone

Summary by CodeRabbit

  • Documentation
    • Updated the "Quick start" section in the README to clarify the installation of protoc from official releases and its inclusion in the user's $PATH.

@lklimek lklimek added this to the 1.4 milestone Nov 27, 2024
Copy link
Contributor

coderabbitai bot commented Nov 27, 2024

Walkthrough

The changes consist of an update to the README.md file, specifically adding a bullet point in the "Quick start" section. This new point clarifies the necessity of installing protoc from the official Protocol Buffers releases and highlights that versions provided by user distributions are unsupported. No other modifications were made to the document's content, structure, or formatting.

Changes

File Change Summary
README.md Added a bullet point in the "Quick start" section regarding protoc installation requirements.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant README
    User->>README: Check Quick Start
    README-->>User: Display installation instructions
    User->>README: Note `protoc` installation requirement
    README-->>User: Clarify unsupported versions
Loading

🐇 "In the README, a note so bright,
About protoc, it shines a light.
Install it right from the official place,
To keep your code at a steady pace!
No more worries, just hop along,
With clear instructions, you can't go wrong!" 🐇


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 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 and nitpick comments (1)
README.md (1)

33-34: Enhance the protoc installation instructions

While the warning about distribution packages is clear, we could make these instructions more helpful by:

  1. Specifying the minimum required version of protoc
  2. Providing direct installation steps

Consider expanding the bullet point like this:

-   * Ensure to install `protoc` from <https://github.com/protocolbuffers/protobuf/releases> and place it in your `$PATH`, as we
-   **don't support protoc shipped with your distribution** (like Ubuntu).
+   * Install `protoc` (Protocol Buffer Compiler):
+     1. Download the latest release from <https://github.com/protocolbuffers/protobuf/releases>
+     2. Extract the archive and add the `bin` directory to your `$PATH`
+     3. Verify installation: `protoc --version`
+     
+     **Note:** Do not use package manager versions (apt, brew, etc.) as they are unsupported.
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between af9983d and fefb1a1.

📒 Files selected for processing (1)
  • README.md (1 hunks)
🔇 Additional comments (1)
README.md (1)

33-34: Documentation change looks good!

The added warning about protoc installation:

  • Clearly addresses the reported issue with distribution packages
  • Is well-placed in the dependencies section
  • Correctly emphasizes the PATH requirement
  • References the official source for installation

@shumkov shumkov merged commit 9745cf3 into develop Nov 27, 2024
10 checks passed
@lklimek lklimek deleted the doc/protoc-requirement branch November 27, 2024 13:31
@lklimek lklimek modified the milestones: 1.4, 1.2, 1.3 Nov 28, 2024
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