test: [refactor] Use verbosity=0 named arg
What the developer wrote
Authored by MarcoFalke
test: [refactor] Use verbosity=0 named arg
This is less confusing than the verbose=0 alias.
What changed, and why it matters
This is a tiny test-only code cleanup. It changes one argument name from verbose=0 to verbosity=0 inside a test helper function. It does not touch live Bitcoin network code, wallets, consensus rules, or any user-facing behavior. There is no security relevance.
No action needed. This is a benign test refactor.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit modifies test/functional/test_framework/util.py in the dumb_sync_blocks helper. It replaces the deprecated verbose named argument with the current verbosity named argument when calling getblock via the RPC test framework. The change is purely a refactor in the functional test suite and has no runtime effect on Bitcoin Core itself.
Changed components
test/functional/test_framework/util.pyInspect captured patch +1 / −1
diff --git a/test/functional/test_framework/util.py b/test/functional/test_framework/util.py
index 497a6d2d..2eb891cf 100644
--- a/test/functional/test_framework/util.py
+++ b/test/functional/test_framework/util.py
@@ -729,7 +729,7 @@ def dumb_sync_blocks(*, src, dst, height=None):
height = height or src.getblockcount()
for i in range(dst.getblockcount() + 1, height + 1):
block_hash = src.getblockhash(i)
- block = src.getblock(blockhash=block_hash, verbose=0)
+ block = src.getblock(blockhash=block_hash, verbosity=0)
dst.submitblock(block)
assert_equal(dst.getblockcount(), height)
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.