Repository navigation
Conversation
…est helper #5712 added broadcast_exact_registration_lock, which calls broadcast_funded_asset_lock_with_operation with seven arguments. #5476, merged right after it, added the eighth (on_built). Each PR passed on its own base, but together they leave the platform-wallet test target uncompilable, so v5.1-dev's all-targets clippy fails with E0061. Pass None, as the other test call sites do. Test would have caught this in CI: cargo clippy -p platform-wallet --all-targets --all-features fails with E0061 before this change and passes after; the 48 asset_lock::build tests pass. 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 |
|
✅ Final review complete — no blockers (commit 9fd84ec) · triage: low |
thepastaclaw
left a comment
There was a problem hiding this comment.
Final validation — Phase 1 + Phase 2
Verified the one-line change at head 9fd84ec: passing None correctly supplies the optional on_built argument without bypassing operation tracking or persistence, and the change is confined to test code. No actionable defects were found. Validation was static only; current GitHub checks show wallet runner selection still pending and no failed code checks, so the supplied claim that wallet CI has passed is not established.
Review provenance
Source: reviewer 1: glm-5.3-flash (agent: phase1-reviewer, role: general); reviewer 2: glm-5.3-flash (agent: phase1-reviewer, role: rust-quality); reviewer 3: gpt-6.1-sol (agent: phase2-reviewer, role: general); reviewer 4: gpt-6.1-sol (agent: phase2-reviewer, role: architecture-layering); reviewer 5: gpt-6.1-sol (agent: phase2-reviewer, role: rust-quality); final verifier: gpt-6.1-sol (agent: sol-verifier, role: final-verifier)
- Triage:
lowbygpt-6.1-sol(effort low) — The diff adds a single missing None argument to a Rust test helper, restoring compatibility with the updated method signature without changing production behavior. - Phase 1 reviewers:
glm-5.3-flash— general (completed, effort high); agentphase1-reviewer,glm-5.3-flash— rust-quality (completed, effort high); agentphase1-reviewer - Phase 1 model:
glm-5.3-flash— zai quota: 5h 77% left, weekly 83% left; passed overgemini-3.8-flash-high(antigravity quota lookup failed) - Fresh verifier:
gpt-6.1-sol— final-verifier; agentsol-verifier - Phase 2 reviewers:
gpt-6.1-sol— general (completed, effort medium); agentphase2-reviewer,gpt-6.1-sol— architecture-layering (completed, effort medium); agentphase2-reviewer,gpt-6.1-sol— rust-quality (completed, effort medium); agentphase2-reviewer
|
Bots are done — your move: post |
|
Closing as a duplicate: #5734 fixed the same E0061 in the same test helper and is merged into |
Issue being fixed or feature implemented
v5.1-devno longer compiles theplatform-wallettest target, so the push run's all-targets clippy fails withE0061(latest: run 41594542638 on40039c9244). Two PRs merged back to back each passed on their own base:broadcast_exact_registration_lock, which callsbroadcast_funded_asset_lock_with_operationwith seven arguments;on_built.What was done?
Pass
Noneforon_builtin that helper, as the other test call sites do. Test code only.How Has This Been Tested?
cargo clippy -p platform-wallet --all-targets --all-features --locked -- --no-deps -D warnings: fails withE0061(2 errors) without this change, passes with it.cargo test -p platform-wallet --lib --all-features asset_lock::build: 48 passed.Breaking Changes
None.
Checklist:
For repository code-owners and collaborators only
🤖 Generated with Claude Code
PR Hygiene ·
9fd84ec/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