Repository navigation
test(platform-wallet): pass the built-lock observer in the input-cap test helper - #5734
Conversation
…test helper #5712 added `broadcast_exact_registration_lock`, calling `broadcast_funded_asset_lock_with_operation` with 7 arguments, and #5476, merged after it from a branch last tested before #5712 existed, gave that method an 8th parameter (`on_built`). v5.1-dev's platform-wallet tests stopped compiling (E0061 at asset_lock/build.rs:4741), failing "Rust workspace tests" on every pull request into it. The helper passes `None`, as #5476's own test calls do. Co-Authored-By: Claude Opus 5.5 <[email protected]>
|
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 c220cb6. Normal review starts when eligible; priority review starts as soon as a slot is available. |
Brings in #5734, which fixes the platform-wallet test helper that two earlier base merges left calling broadcast_funded_asset_lock_with_operation without its new observer argument (the Clippy lints failure here). Co-Authored-By: Claude Opus 5.5 <[email protected]>
Basic explanation
v5.1-dev does not compile its
platform-wallettests, so "Rust workspace tests" fails on every pull request into it. Two pull requests crossed: #5712 added a test helper callingbroadcast_funded_asset_lock_with_operationwith 7 arguments, and #5476, merged after it from a branch last tested before #5712 existed, gave that method an 8th parameter (on_built). This passesNonethere, as #5476's own test calls do.Before (v5.1-dev at b0ccf7b and later):
After: the crate's tests compile, and the four input-cap tests that use the helper run.
Issue being fixed or feature implemented
fix(platform-wallet): refuse a fixed-amount asset lock over the input cap before broadcast, merged 2026-11-02 21:53 UTC) addedbroadcast_exact_registration_lock, a test helper inasset_lock/build.rs.feat(platform-wallet)!: report a freshly built asset lock's outpoint to the caller, merged 2026-11-03 06:09 UTC) addedon_built: Option<&AssetLockBuiltObserver<'_>>tobroadcast_funded_asset_lock_with_operationand updated every call that existed when its branch was last tested (2026-10-29).Each passed CI alone; together they leave the helper one argument short. Failing runs include https://github.com/dashpay/platform/actions/runs/41598837399/job/125794341548.
What was done?
broadcast_exact_registration_lockpassesNoneforon_built: the input-cap tests that call it check what is refused, broadcast and handed back, not the observer.How Has This Been Tested?
cargo clippy -p platform-wallet --all-targets --all-features --locked -- --no-deps -D warnings(the CI clippy command, on this crate): clean.cargo test -p platform-wallet --all-features --locked --lib -- asset_lock::build: 48 passed, among them the four input-cap tests that call the helper.Breaking Changes
None. Test code only.
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 ·
c220cb6/skip-botsproceeds without the ones not yet reported/self-reviewedrs-platform-wallet(packages/rs-platform-wallet/src/wallet/asset_lock/build.rs) — HashEngineering or ZocoLini or llbartekll or romchornyiWhen 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
None.