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

fix: use arduino/setup-protocol #1370

Closed
wants to merge 1 commit into from
Closed

fix: use arduino/setup-protocol #1370

wants to merge 1 commit into from

Conversation

neo773
Copy link
Contributor

@neo773 neo773 commented Mar 10, 2024

Summary:
Briefly describe the changes made in this PR.

Issue Reference(s):
Fixes #1360

Build & Testing:

  • I ran cargo test successfully.
  • I have run ./lint.sh --mode=fix to fix all linting issues raised by ./lint.sh --mode=check.

/claim #1360

Copy link
Contributor

coderabbitai bot commented Mar 10, 2024

Walkthrough

The update involves modifying continuous integration (CI) workflows by adopting arduino/setup-protoc@v3 for Protoc installation. This change affects the build, testing, and toolchain setup processes within the workflow, streamlining development practices and potentially improving efficiency and compatibility across projects.

Changes

Files Change Summary
.github/workflows/ci.yml,
.github/workflows/lint.yml
Updated to use arduino/setup-protoc@v3 for Protoc installation, impacting CI workflow build, testing, and toolchain setup.

🐇✨
In the realm of code, where the bits align,
A change was made, oh so fine.
With arduino/setup-protoc@v3 in its place,
Our workflows run with newfound grace.
So hop along, let's embrace the change,
For in this digital burrow, we roam and range.
🚀🌟

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>.
    • Generate unit-tests 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 tests 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit tests.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • The JSON schema for the configuration file is available here.
  • 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

@github-actions github-actions bot added the type: fix Iterations on existing features or infrastructure. label Mar 10, 2024
Copy link

codecov bot commented Mar 10, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.36%. Comparing base (310d7cb) to head (828fbb8).
Report is 18 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1370      +/-   ##
==========================================
+ Coverage   88.21%   88.36%   +0.14%     
==========================================
  Files         128      128              
  Lines       13407    13385      -22     
==========================================
  Hits        11827    11827              
+ Misses       1580     1558      -22     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

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.

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits Files that changed from the base of the PR and between b10014f and 828fbb8.
Files selected for processing (2)
  • .github/workflows/ci.yml (3 hunks)
  • .github/workflows/lint.yml (1 hunks)
Additional comments: 4
.github/workflows/lint.yml (1)
  • 36-37: The switch to arduino/setup-protoc@v3 for installing Protoc is a significant change aimed at improving the toolchain setup. Please ensure that this version is fully compatible with the project's requirements and does not introduce any performance regressions or breaking changes.

Consider adding a step to verify the compatibility of arduino/setup-protoc@v3 with the project's Protobuf files to ensure smooth integration.

.github/workflows/ci.yml (3)
  • 58-59: Switching to arduino/setup-protoc@v3 for the AWS Lambda build process is a notable update. Ensure compatibility with the project's Protobuf files and assess any impact on the build performance.

Consider adding a verification step for arduino/setup-protoc@v3 compatibility with the project's Protobuf files, especially for AWS Lambda builds.

  • 103-104: The update to use arduino/setup-protoc@v3 in the general test job is crucial for maintaining a consistent toolchain across the project. As with other changes, verify this version's compatibility and performance impact on the testing process.

Adding a step to confirm the compatibility of arduino/setup-protoc@v3 with the project's Protobuf files in the testing context is recommended.

  • 135-136: Implementing arduino/setup-protoc@v3 for the examples check job is a strategic move to ensure the toolchain's uniformity. Confirm that this version aligns with the project's Protobuf requirements and does not negatively affect the build or check process.

It's advisable to verify the compatibility of arduino/setup-protoc@v3 with the Protobuf files used in examples to ensure a seamless integration.

Copy link

Action required: PR inactive for 2 days.
Status update or closure in 5 days.

@github-actions github-actions bot added state: inactive No current action needed/possible; issue fixed, out of scope, or superseded. and removed state: inactive No current action needed/possible; issue fixed, out of scope, or superseded. labels Mar 12, 2024
@tusharmath
Copy link
Contributor

@neo closing this PR because the build does not work in Windows env.

@tusharmath tusharmath closed this Mar 13, 2024
@tusharmath
Copy link
Contributor

More insights about the issues can be found here #1380

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🙋 Bounty claim type: fix Iterations on existing features or infrastructure.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

chore: install protobuf-compiler
2 participants