Skip to content

Update README.md - Bug in Espressif Arduino 3.2.0 #163

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

Closed
wants to merge 1 commit into from

Conversation

sylque
Copy link

@sylque sylque commented May 3, 2025

Espressif Arduino 3.2.0 has a terrible bug (asserts are ignored). I think it's worth warning users about that, and show them how to stick with version 3.1.3 if they want to.

Summary by CodeRabbit

  • Documentation
    • Updated the README to warn about a critical bug in espressif Arduino version 3.2.0 and recommend using version 3.1.3 instead.
    • Added an example configuration snippet for selecting Arduino version 3.1.3.
    • Made a minor punctuation correction in the stable Arduino section.

Espressif Arduino 3.2.0 has a terrible bug (asserts are ignored), so users might prefer to stick with version 3.1.3 for now.
Copy link

coderabbitai bot commented May 3, 2025

Walkthrough

The README file was updated to include a warning about a critical bug in espressif Arduino version 3.2.0, where asserts are ignored. Users are advised to consider using version 3.1.3 instead. An example configuration snippet for platformio.ini was added to demonstrate how to specify version 3.1.3 directly. Additionally, a minor punctuation correction was made in the stable Arduino section.

Changes

File Change Summary
README.md Added warning about espressif Arduino 3.2.0 bug, suggested using 3.1.3, provided config example, fixed punctuation.

Poem

A README note, a warning clear,
About a bug that’s lurking near.
Version 3.2.0, asserts ignored—oh dear!
Try 3.1.3, the fix is here.
With snippets and dots, the path is bright,
For coders and bunnies coding through the night!
🐇✨


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

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.

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

🧹 Nitpick comments (2)
README.md (2)

23-23: Nit: Capitalization and clarity.

The sentence

currently espressif Arduino 3.2.0 and IDF 5.4.1. 

starts with a lowercase letter and reads as a fragment. Consider rewriting to a full sentence, for example:

Currently using espressif Arduino 3.2.0 with IDF 5.4.1.

32-33: Enhance visibility of the bug warning.

Instead of a plain paragraph, use a markdown blockquote or admonition to highlight the issue. For example:

> **⚠️ Warning:** espressif Arduino 3.2.0 has a [known bug](https://github.com/espressif/arduino-esp32/issues/11166) that causes `assert()` to be ignored. Consider using version 3.1.3:

This will make it stand out more clearly in the docs.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 6cf33bf and 3badfb6.

📒 Files selected for processing (1)
  • README.md (2 hunks)

Comment on lines +34 to +38
[env:stable]
platform = https://github.com/pioarduino/platform-espressif32/releases/download/53.03.13+github/platform-espressif32.zip
board = ...
...
```
Copy link

Choose a reason for hiding this comment

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

💡 Verification agent

🧩 Analysis chain

Verify the workaround URL and version string.

Please confirm that the platform URL and version tag actually correspond to the intended 3.1.3 release. You can run a simple HTTP check to ensure the ZIP is reachable:

This ensures users won’t hit a broken link when pinning to the older version.


🏁 Script executed:

#!/bin/bash
# Check that the fallback platform ZIP returns HTTP 200
URL="https://github.com/pioarduino/platform-espressif32/releases/download/53.03.13+github/platform-espressif32.zip"
STATUS=$(curl -o /dev/null -s -w "%{http_code}" "$URL")
if [ "$STATUS" -ne 200 ]; then
  echo "Error: Expected HTTP 200, got $STATUS for $URL"
  exit 1
fi
echo "URL is valid and reachable."

Length of output: 616


Follow redirects when verifying the fallback platform ZIP

The GitHub “releases/download” endpoint will issue a 302 redirect to the actual asset host, so your check needs to follow redirects before asserting HTTP 200. For example:

#!/bin/bash
URL="https://github.com/pioarduino/platform-espressif32/releases/download/53.03.13+github/platform-espressif32.zip"

# Follow redirects and verify final status is 200
STATUS=$(curl -L -o /dev/null -s -w "%{http_code}" "$URL")
if [ "$STATUS" -ne 200 ]; then
  echo "Error: Expected HTTP 200, got $STATUS for $URL"
  exit 1
fi
echo "URL is valid and reachable."

– This ensures you’re actually pulling down the ZIP asset for version 3.1.3 rather than only seeing the redirect.

@Jason2866
Copy link

Jason2866 commented May 4, 2025

All PRs please only against branch develop. Furthermore won't merge. Issues in core won't be mentioned in the general pioarduino Readme. This is a Arduino core issue and not related or caused by pioarduino

@Jason2866 Jason2866 closed this May 4, 2025
@Jason2866
Copy link

Added info in release. Thx for heads up

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