docs(drive): document trusted-state rationale for bincode NoLimit#3370
Conversation
GroveDB state is always trusted — if storage is corrupted, the problem is at the storage layer, not the deserialization layer. Adding artificial size limits would mask real issues without meaningful protection. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
Caution Review failedPull request was closed or merged during review No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughAdded SAFETY documentation comments to the Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches
🧪 Generate unit tests (beta)
📝 Coding Plan
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 |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## v3.1-dev #3370 +/- ##
=========================================
Coverage 75.87% 75.87%
=========================================
Files 2912 2912
Lines 283860 283932 +72
=========================================
+ Hits 215375 215438 +63
- Misses 68485 68494 +9
🚀 New features to boost your workflow:
|
Summary
CompactedNullifiers::bincode_config()andNullifierExpirationRanges::bincode_config()explaining whywith_no_limit()is intentionalContext
Security audit flagged
with_no_limit()as a potential DoS vector (L7). After review, this was determined to be a false positive: this data is only deserialized from GroveDB's own trusted state, never from untrusted external input. Adding this comment to prevent future auditors from re-investigating.Test plan
🤖 Generated with Claude Code
Summary by CodeRabbit