fs: Adjust to new mkfs.exfat behaviour in exfatprogs >= 1.4.0#1199
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
🚧 Files skipped from review as they are similar to previous changes (3)
📝 WalkthroughWalkthroughDeclare exFAT partition-table capability, add a version-aware mkfs.exfat check for exfatprogs >= 1.4.0 to conditionally append ChangesexFAT Partition Table Support
🎯 3 (Moderate) | ⏱️ ~20 minutes Suggested reviewers:
🚥 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)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 Infer (1.2.0)src/plugins/fs/exfat.csrc/plugins/fs/exfat.c:20:10: fatal error: 'blockdev/utils.h' file not found ... [truncated 701 characters] ... /infer-linux-x86_64-v1.2.0/lib/infer/facebook-clang-plugins/clang/install/lib/clang/18/include" src/plugins/fs/generic.csrc/plugins/fs/generic.c:20:10: fatal error: 'glib.h' file not found ... [truncated 677 characters] ... nfer-linux-x86_64-v1.2.0/lib/infer/facebook-clang-plugins/clang/install/lib/clang/18/include" 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. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@tests/fs_tests/exfat_test.py`:
- Around line 15-24: Module-level exfatprogs version detection
(_get_exfatprogs_version and EXFATPROGS_VERSION) runs at import time and can
crash import if mkfs.exfat is missing; change it to lazy initialization so tests
can be skipped in ExfatTestCase.setUp. Remove the module-level call to
_get_exfatprogs_version and instead call it inside ExfatTestCase.setUp (or wrap
it in a helper that returns None on error), catch exceptions from
_get_exfatprogs_version there, set a per-instance flag or attribute (e.g.,
self.exfatprogs_version or self.exfat_available), and use that flag in setUp to
call self.skipTest when mkfs.exfat isn't available so import-time failures are
avoided.
🪄 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: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: fffb570a-b599-4fe8-acb4-cfc07e50e706
📒 Files selected for processing (3)
src/plugins/fs/exfat.csrc/plugins/fs/generic.ctests/fs_tests/exfat_test.py
mkfs.exfat now also creates a partition table, similarly to how mkfs.vfat does it.
cdb5504 to
636abf0
Compare
mkfs.exfat now also creates a partition table, similarly to how mkfs.vfat does it.
Summary by CodeRabbit