It is confusing to use a list of arguments such as False, False, 16, ... where it is unclear what each of them means.
Run some scripted diffs to put meaning to them.
It is confusing to use a list of arguments such as False, False, 16, ... where it is unclear what each of them means.
Run some scripted diffs to put meaning to them.
-BEGIN VERIFY SCRIPT-
sed -i --regexp-extended -e 's/(test_witness_block|test_transaction_acceptance)\((self\.nodes\[.\])\.rpc/\1(\2/g' test/functional/p2p_segwit.py
-END VERIFY SCRIPT-
-BEGIN VERIFY SCRIPT-
sed -i --regexp-extended -e "s/sync_blocks\((.*?), (True|False), (1.?), /sync_blocks(\1, success=\2, reject_code=\3, reject_reason=/g" ./test/functional/feature_block.py
-END VERIFY SCRIPT-
<!--e57a25ab6845829454e8d69fc972939a-->Note to reviewers: This pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.
utACK fa782a3.
nit, could rename the following rpc arguments to node:
Concept ACK
Clearly improves code readability
utACK fa782a308dbe7bc579c122f63c1c65666fc85e91