Fix probe-rs audit follow-ups#1005
Conversation
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (4)
📝 WalkthroughWalkthroughThis PR adds a Changesno_probe_rs MCP flag and probe-rs install hardening
Estimated code review effort: 3 (Moderate) | ~25 minutes Possibly related PRs
✨ Finishing Touches📝 Generate docstrings
🧪 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. Comment |
Summary
no_probe_rson the MCPtrigger_deployschema and forward it into deploy requestsprobe-rsinstalls through a sibling temp file before renameprobe-rsstaging directory after install attemptsCloses #1002
Local validation
soldr cargo test -p fbuild-deploy probe_rs-> 9 passedsoldr cargo test -p fbuild-deploy lpc-> 33 passedsoldr --no-cache cargo test -p fbuild-cli trigger_deploy_exposes_probe_rs_opt_out-> 1 passedsoldr --no-cache cargo test -p fbuild-cli bool_arg_reads_boolean_or_default-> 1 passedsoldr cargo fmt --all --checkgit diff --checksoldr --no-cache cargo build -p fbuild-cli -p fbuild-daemonwith isolated tempCARGO_TARGET_DIRHardware validation
fbuild port scansaw COM10 as1FC9:0132/ NXP LPC-Link2 CMSIS-DAP, serial0B03400AFBUILD_DEV_MODE=1 <temp-target>\fbuild.exe deploy tests/platform/lpc845brk -e lpc845brk --port COM10 --verbose->deploy succeeded (full flash)attempting SWD flash via probe-rs ... probe=1fc9:0132fbuild port scanstill saw COM10 as1FC9:0132Remote Actions wait intentionally skipped per maintainer instruction; this PR was locally built and hardware-validated on this machine.
Summary by CodeRabbit
New Features
Bug Fixes
probe-rsinstalls safer by cleaning up temporary staging files more reliably.