fix(deploy): allow shadow gate OSS readback - #306
Conversation
|
Warning Review limit reached
Next review available in: 42 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe deployment gate now creates per-segment evidence directories with explicit service ownership, and the control-plane test verifies the required ChangesLOB segment ownership enforcement
Estimated code review effort: 2 (Simple) | ~5 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ 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. Comment |
6b75c3b to
ac01363
Compare
Change contract
Create every shadow-gate OSS readback segment directory as
hftcollector:hftcollectorwith mode0750, so the service-userossutilprocess can download immutable manifests, segments, and_SUCCESSmarkers during the production gate.Out of scope
Collector behavior, market-tape schema, gate acceptance thresholds, production cutover, snapshot/cohort construction, and research logic.
Dependency or merge order
Follow-up to #296 and #301. Merge before rerunning issue #224 production shadow gate.
Focused validation
bash deployment/aliyun/test-rust-lob-control-plane.shfailed before the ownership fix.bash deployment/aliyun/test-rust-lob-control-plane.shshellcheck deployment/aliyun/host-rust-lob-shadow-gate.sh deployment/aliyun/test-rust-lob-control-plane.shgit diff --checkt-jpn6rtzvbbnwlj4completed the one-hour collection and uploads, then failed closed with permission denied while downloading the first Spot manifest into a root-owned0750segment directory.Rollout / rollback impact
Rollout: deploy the merged gate bundle with the same collector candidate and rerun the full one-hour shadow gate. Rollback: revert this PR; no production service or stored market data is changed by the patch.
Refs #224
Summary by CodeRabbit
Bug Fixes
Tests