Lock retained evidence crosswalk - #618
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughAdds a single regression test file change: new imports, a Retained Ref Crosswalk Regression Test
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ 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 |
Code Lawyer update
Validation highlights:
|
Summary
BlobHash,SemanticBlobCoordinate,RetainedEvidenceRef, WALRetainedMaterialRecord, andReadingRefRecord.Closes #569.
Validation
cargo fmt --checkcargo clippy -p warp-core --test retained_evidence_ref_tests -- -D warningscargo test -p warp-core --test retained_evidence_ref_testscargo test -p warp-core --test optic_retention_testscargo clippy -p warp-core --libcargo check -p warp-corecargo test -p warp-core --test retained_evidence_ref_testsTest-loop note
I kept the release witness focused on
retained_evidence_ref_tests; the new crosswalk assertion lives in the named #569 witness instead of broadening the suite.Summary by CodeRabbit