fix: s2c script ignoring Apple Silicon's cpu other than M1

[rafaeltonholo]

Summary by CodeRabbit

• New Features
  • Updated platform identification logic to support all Apple Silicon devices, enhancing compatibility.
• Bug Fixes
  • Increased robustness of platform detection by broadening the criteria for recognizing Apple Silicon.
• Chores
  • Updated version number to 1.3.2 to reflect minor enhancements and fixes.

[coderabbitai]

Walkthrough

The recent changes involve updating the version number in the app.properties file from 1.3.1 to 1.3.2, indicating a minor release. Additionally, the platform identification logic in a script has been refined for macOS on Apple Silicon. The variable PLATFORM_MAC_M1 has been renamed to PLATFORM_MAC_APPLE_SILICON, and the detection logic has been broadened to support all Apple Silicon devices, enhancing compatibility and robustness.

Changes

Files	Change Summary
app.properties	Version updated from 1.3.1 to 1.3.2, indicating a minor release.
.../script.sh	Renamed variable from PLATFORM_MAC_M1 to PLATFORM_MAC_APPLE_SILICON and updated platform detection logic to check for any Apple Silicon.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Script
    participant System

    User->>Script: Run script
    Script->>System: Check system architecture
    System-->>Script: Return architecture (e.g., "arm64")
    Script->>Script: Determine if Apple Silicon
    alt Apple Silicon detected
        Script->>User: Notify compatible platform
    else Not Apple Silicon
        Script->>User: Notify incompatible platform
    end

Loading

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 6b93f42 and be4f209.

Files selected for processing (2)

• app.properties (1 hunks)
• s2c (2 hunks)

Files skipped from review due to trivial changes (1)

• app.properties

Additional comments not posted (2)

s2c (2)

11-11: Renaming variable for clarity.

The variable PLATFORM_MAC_M1 has been renamed to PLATFORM_MAC_APPLE_SILICON, which enhances clarity regarding the platform it represents.

---

75-76: Broadening platform detection for Apple Silicon.

The detection logic has been updated to use uname -m to check for the arm64 architecture, broadening the platform detection to include any Apple Silicon device. This improves the script's robustness.