check for Inet before trying to fetch newest develop Arduino

[Jason2866]

Description:

Fix crash when no Internet is available

Checklist:

• The pull request is done against the latest develop branch
• Only relevant files were touched
• Only one feature/fix was added per PR, more changes are allowed when changing boards.json
• I accept the CLA

Summary by CodeRabbit

• New Features

  • Added automatic detection of internet connectivity before attempting to update Arduino ESP32 libraries.

• Bug Fixes

  • Improved error handling and fallback behavior when internet access is unavailable during library updates.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

A new function for checking internet connectivity was added. The logic in the Espressif32Platform.configure_default_packages method was updated to use this check before attempting to fetch the latest Arduino ESP32 libraries URL from GitHub. Error handling for network and JSON parsing issues was also introduced, with fallback messaging for offline scenarios.

Changes

File(s)	Change Summary
platform.py	Added is_internet_available() function; updated package configuration to check connectivity and handle network/JSON errors.

Poem

A bunny hopped to check the net,
Before it fetched its code-set.
If online, it grabs the latest ware,
If not, it simply waits with care.
With sockets and with gentle paws,
It handles errors without a pause!
🐇💻🌐

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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>, please review it.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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.

[Jason2866]

@coderabbitai full review

[coderabbitai]

✅ Actions performed

Full review triggered.

[coderabbitai]

Actionable comments posted: 2

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 381a557 and 30f7bec.

📒 Files selected for processing (1)

• platform.py (3 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (20)

• GitHub Check: build (macos-15, examples/espidf-blink)
• GitHub Check: build (macos-15, examples/espidf-ulp)
• GitHub Check: build (windows-latest, examples/espidf-peripherals-uart)
• GitHub Check: build (windows-latest, examples/espidf-ulp-lp)
• GitHub Check: build (windows-latest, examples/espidf-peripherals-usb)
• GitHub Check: build (ubuntu-24.04, examples/espidf-hello-world)
• GitHub Check: build (windows-latest, examples/espidf-arduino-blink)
• GitHub Check: build (windows-latest, examples/arduino-wifiscan)
• GitHub Check: build (windows-latest, examples/arduino-rmt-blink)
• GitHub Check: build (windows-latest, examples/arduino-zigbee-light)
• GitHub Check: build (windows-latest, examples/espidf-blink)
• GitHub Check: build (ubuntu-24.04, examples/tasmota)
• GitHub Check: build (windows-latest, examples/espidf-hello-world)
• GitHub Check: build (windows-latest, examples/arduino-NimBLE-ext_client)
• GitHub Check: build (windows-latest, examples/espidf-arduino-matter-light)
• GitHub Check: build (ubuntu-24.04, examples/espidf-arduino-matter-light)
• GitHub Check: build (windows-latest, examples/espidf-http-request)
• GitHub Check: build (windows-latest, examples/arduino-zigbee-switch)
• GitHub Check: build (windows-latest, examples/arduino-usb-keyboard)
• GitHub Check: build (ubuntu-24.04, examples/arduino-blink)

🔇 Additional comments (1)

platform.py (1)

16-16: socket import looks correct

Importing socket is required for the new connectivity helper. No concerns here.