fix: make provider runtime help successful and bounded - #216
Conversation
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: trueNo actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthrough두 CLI가 커버리지 빌드에서도 실제 실행 경로를 유지합니다. 인자 중복, 범위, 비-UTF-8 값, 도움말 동작을 검증합니다. 클라우드 인벤토리는 하위 경로를 검증합니다. Provider client-runtime은 출력 경로의 권한과 심볼릭 링크를 검증합니다. ChangesCLI 경계 계약
Estimated code review effort: 4 (Complex) | ~60 minutes Merge Risk: 🟡 Moderate · up to The change makes both operational CLI paths bounded and fail closed, but the current commit is not merge-ready because required release verification is failing. Concurrent filesystem mutation could still redirect publication or inventory traversal, and an interrupted provider write could leave a partial artifact that prevents retry, so owner follow-up is required before merging. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches 💡 2📝 Generate docstrings 💡
🛠️ Fix failing CI checks 💡
🧪 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 |
|
@coderabbitai review |
|
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
…r sidecar pin fix The previous noema/strix/opencode-review failures used the pre-fix sidecar pin (b2164511). .github main now vendors the fixed commit, so re-running should populate the review verdicts. Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Purpose
Provide bounded, fail-closed operational CLI contracts for
disksage-provider-client-runtimeanddisksage-cloud-local-inventorywithout weakening provider, filesystem, or publication authority.Exact current state
70168b9c3a0c978f03b1b887f866a65611eedb66.main:79067c1160ddedf7fc962cbf8067ce7e83c4564a.main.3659198bec439ab288091787be0f835914473053failed Test run33170377504because resolving every output-parent symlink contradicted the existing arbitrary-symlink fail-closed contract while trying to support macOS/var.Current repair
The provider-runtime output boundary preserves both contracts:
/var,/tmp, and/etcmay be remapped, and only when the live alias canonicalizes to its expected/private/...target;symlink_metadata, so a nested or attacker-controlled symlink remains rejected;0600remain unchanged;--outputis intentionally rejected before reading/probing a second parent, while the first accepted output remains fully resolved and validated;write_create_newre-runs output-path authority validation immediately beforecreate_new, preserving the parse-to-write fail-closed boundary.Exact-head evidence
For unchanged exact head
70168b9c3a0c978f03b1b887f866a65611eedb66:33179007406— SUCCESS.33179007401— SUCCESS.33179007442— SUCCESS.33179007431— FAILURE only indownload-artifact-pr-compatjob98879035034, stepVerify downloaded release artifact contract; Linux/macOS/Windows builds, operational CLI staging, artifact upload, and exact v8 artifact download all succeeded. This shared verifier boundary is not repaired locally in this owner.Ownership / non-duplication
This line owns only provider-runtime/cloud-local-inventory CLI behavior and focused tests. It does not absorb provider/cloud follow-up semantics, repository-wide exact coverage #156, canonical acquisition documentation #149, or shared release-verifier ownership #264.
Merge rule
Do not merge unless one unchanged exact head satisfies the live inherited ruleset and every applicable required CI/security/coverage/package/SBOM/provenance/release gate, all valid current findings are resolved, and a qualifying independent formal approval exists where required. Pending, queued, skipped-required, cancelled, failed, stale, predecessor, synthetic, diagnostic-only, status-only, model-only, author-only, no-source, or infrastructure-only evidence is not passing.