Repository navigation
fix(drive): drop the argument #5798 removed from add_document_for_contract in a proof plan test - #5821
Conversation
…tract in a proof plan test #5774 (ccaa396) added proof_plan_equivalence_tests.rs, whose fixture calls add_document_for_contract with a trailing fee-history argument. #5798 (dd9dc7e), merged just before it, removed that parameter, so drive's tests stopped compiling on v5.1-dev (error[E0061] in `cargo clippy -p drive --all-targets`), failing the Clippy lints step of every PR on v5.1-dev. The call drops the argument; nothing else changes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
|
Waiting for bot review — thepastaclaw not yet. Wait for the missing reviews, or a writer can post |
|
🕓 Review not started yet because the new head is waiting for the 30-minute push debounce.
Commit f4c9ff4. Normal review starts when eligible; priority review starts as soon as a slot is available. |
Basic explanation
What this does: drive's tests compile again on v5.1-dev. One test call passed an argument that a function no longer takes; this PR removes it.
Why it broke: two PRs merged close together and conflict in meaning, not in text.
Drive::add_document_for_contract.packages/rs-drive/src/query/proof_plan_equivalence_tests.rs, whose fixture still passes it.Each PR's CI ran without the other's change.
Value: the Clippy lints step (
cargo clippy -p drive --all-targets) fails on v5.1-dev and on every PR against it until this lands.Risks: none. It changes one test fixture only.
Issue being fixed or feature implemented
What was done?
The fixture's
add_document_for_contract(..)call inproof_plan_equivalence_tests.rsdrops the trailingNonethat #5798 removed from the signature. No other call site passes it.How Has This Been Tested?
On v5.1-dev ccaa396 with this change:
cargo clippy -p drive --all-targets --all-features -- -D warnings: clean.cargo check -p drive-abci --tests: compiles.add_document_for_contract,lookup_cost,from_storage_removal) were left stale.Breaking Changes
None.
Checklist:
structure.rs, regeneratedgrovedb-structure.json, and checked the structure viewer link posted on this pull requestFor repository code-owners and collaborators only
🤖 Generated with Claude Code
PR Hygiene ·
f4c9ff4/skip-botsproceeds without the ones not yet reported/self-reviewedWhen every merge requirement is met, the
PR Hygienecheck passes. Reviewer limits do not block merging; other required GitHub checks and protections still apply.Summary by CodeRabbit