test(destination): lock exact proxy, redirect, and freshness bounds - #335
seonghobae wants to merge 2 commits into
Conversation
Destination policy now has executable evidence for the maximum proxy and PAC authority sets, a full walk of the maximum redirect hop budget, and freshness limits that stay fail-closed at the published ceilings.
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. 🧰 Additional context used📚 Code guidelines (1)No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (8)
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthrough프록시/PAC 권한 한도, 프록시 주소 정규화, 리다이렉트 및 해석 유효 기간 경계값에 대한 회귀 테스트를 추가했습니다. 오류 표시 테스트도 보강했습니다. 프로덕션 경로 정책과 네트워크 권한은 변경하지 않았습니다. Changes정책 경계값 테스트
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~12 minutes Change: Other Merge Risk: ⚪ Minimal · up to The added tests cover the stated policy boundaries without changing production behavior. No issue identified here prevents merging. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
📝 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
Test plan
cargo test -p originweave-destination --offline(40 passed)cargo fmt -p originweave-destination -- --checkSummary by CodeRabbit