IEP-1758 GH #1451: On Windows the ESP-IDF Manager is not compatible with latest version of EIM#1452
IEP-1758 GH #1451: On Windows the ESP-IDF Manager is not compatible with latest version of EIM#1452kolipakakondal merged 2 commits intomasterfrom
Conversation
|
Warning Rate limit exceeded
To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe EIM JSON version constant is updated from "1.0" to "2.0", and the validation logic in the parser is modified to use numeric threshold comparison instead of exact string equality, allowing versions greater than or equal to the valid version to pass. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Review rate limit: 0/1 reviews remaining, refill in 21 minutes and 1 second.Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In
`@bundles/com.espressif.idf.core/src/com/espressif/idf/core/tools/EimConstants.java`:
- Line 30: The change raised the minimum accepted EIM JSON version to 2.0 which
breaks backward compatibility; revert EIM_JSON_VALID_VERSION in EimConstants
(the String constant EIM_JSON_VALID_VERSION in class EimConstants) to the
previous compatible baseline (e.g., "1.0" or the prior value used before this
change) or implement a version-acceptance check that permits 1.x versions, so
existing eim_idf.json files continue to validate.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: fefa0044-7320-41a4-ac25-7fd20e848e21
📒 Files selected for processing (2)
bundles/com.espressif.idf.core/src/com/espressif/idf/core/tools/EimConstants.javabundles/com.espressif.idf.core/src/com/espressif/idf/core/tools/EimIdfConfiguratinParser.java
|
@sigmaaa hi Tested under: LGTM 👍 |
Description
We can safely parse version 2.0 using the existing code and allow users to activate their ESP-IDF in the IDE. The new changes introduced in eim_idf.json 2.0 can be handled separately at a later stage.
Fixes # (IEP-1758)
Type of change
Please delete options that are not relevant.
How has this been tested?
Install some esp-idf with latest eim manager and make sure that eim_idf.json version is 2.0. Try to activate and use esp-idf via Espressif-IDE
Test Configuration:
Dependent components impacted by this PR:
Checklist
Summary by CodeRabbit