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

✏️ Update references to ARM being unsupported #72

Merged
merged 1 commit into from
Jun 13, 2024

Conversation

sinclairpaul
Copy link
Member

@sinclairpaul sinclairpaul commented Jun 12, 2024

Proposed Changes

Folding@Home looks to have supported ARM towards the end of 2020 (post addon setup), remove the statement saying it isn't supported.

Related Issues

Closes #71

Summary by CodeRabbit

  • Documentation
    • Updated supported platforms information for the Folding@home add-on, removing the mention that ARM devices like Raspberry Pi are not supported.

Copy link

coderabbitai bot commented Jun 12, 2024

Walkthrough

The primary change involves updating the DOCS.md file for the Folding@home add-on to reflect that it now supports ARM devices, including Raspberry Pi. This update removes the previous limitation that indicated ARM devices were not supported.

Changes

Files Change Summary
foldingathome/DOCS.md Updated platform support information to include ARM devices.

Assessment against linked issues

Objective Addressed Explanation
Update documentation to reflect ARM support (#71)
Correct the statement about Folding@home not supporting ARM devices (#71)

Poem

🐇 In the world of code and bytes,
ARM devices join the heights.
Folding@home now does embrace,
Raspberry Pi in the race.
Proteins fold with might and grace,
In every corner, every place.
🖥️ Let's compute and save the face! 🌟


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

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

@sinclairpaul sinclairpaul added the documentation Solely about the documentation of the project. label Jun 12, 2024
Copy link

@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: 1

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 2ce2df5 and 937a0d3.

Files selected for processing (1)
  • foldingathome/DOCS.md (1 hunks)
Additional context used
LanguageTool
foldingathome/DOCS.md

[uncategorized] ~53-~53: Loose punctuation mark. (UNLIKELY_OPENING_PUNCTUATION)
Context: ...n issue. Possible values are: - trace: Show every detail, like all called inte...


[uncategorized] ~54-~54: Loose punctuation mark. (UNLIKELY_OPENING_PUNCTUATION)
Context: ...all called internal functions. - debug: Shows detailed debug information. - `in...


[uncategorized] ~55-~55: Loose punctuation mark. (UNLIKELY_OPENING_PUNCTUATION)
Context: ...ows detailed debug information. - info: Normal (usually) interesting events. - ...


[uncategorized] ~56-~56: Loose punctuation mark. (UNLIKELY_OPENING_PUNCTUATION)
Context: ...usually) interesting events. - warning: Exceptional occurrences that are not er...


[uncategorized] ~57-~57: Loose punctuation mark. (UNLIKELY_OPENING_PUNCTUATION)
Context: ...currences that are not errors. - error: Runtime errors that do not require imme...


[uncategorized] ~58-~58: Loose punctuation mark. (UNLIKELY_OPENING_PUNCTUATION)
Context: ... not require immediate action. - fatal: Something went terribly wrong. Add-on b...


[uncategorized] ~95-~95: Loose punctuation mark. (UNLIKELY_OPENING_PUNCTUATION)
Context: ...ented based on the following: - MAJOR: Incompatible or major changes. - `MINOR...


[uncategorized] ~96-~96: Loose punctuation mark. (UNLIKELY_OPENING_PUNCTUATION)
Context: ...Incompatible or major changes. - MINOR: Backwards-compatible new features and e...


[uncategorized] ~97-~97: Loose punctuation mark. (UNLIKELY_OPENING_PUNCTUATION)
Context: ...new features and enhancements. - PATCH: Backwards-compatible bugfixes and packa...

foldingathome/DOCS.md Show resolved Hide resolved
Copy link
Member

@frenck frenck left a comment

Choose a reason for hiding this comment

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

Thanks, @sinclairpaul 👍

../Frenck

@frenck frenck merged commit ab0a691 into hassio-addons:main Jun 13, 2024
10 checks passed
@sinclairpaul sinclairpaul deleted the update-docs branch June 13, 2024 13:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Solely about the documentation of the project.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

F@H indeed does run on arm
2 participants