< bitcoin-git>
bitcoin/master 72a18a7 practicalswift: tests: Add information on how to add Vulture suppressions
< bitcoin-git>
bitcoin/master 0432149 fanquake: Merge #16921: tests: Add information on how to add Vulture suppressions
< bitcoin-git>
[bitcoin] fanquake merged pull request #16921: tests: Add information on how to add Vulture suppressions (master...vulture-suppressions) https://github.com/bitcoin/bitcoin/pull/16921
< instagibbs>
can someone point me to where the "Config setting for %s only applied on %s network when in [%s] section." stuff is actually enforced?
< instagibbs>
Having trouble tracing it
< instagibbs>
that line is just where an init warning is thrown then it continue
< ryanofsky>
instagibbs, you can check the two UseDefaultSection calls. if it returns false the settings get thrown away
< instagibbs>
ah-hah thanks
< instagibbs>
ryanofsky, oh I was getting thrown off that network-specific args are fine in default area *when read by -cli*
< bitcoin-git>
[bitcoin] luke-jr closed pull request #16228: Bugfix: make check: Only run tests that were compiled (master...bugfix_raii_check_fail) https://github.com/bitcoin/bitcoin/pull/16228
< achow101>
any particular reason that we use CAutoFile in a lot of places instead of CBufferedFile?
< sipa>
CAutoFile is older
< sipa>
we needed CBufferedFile for rescanning block files as it supports rewinding
< lightlike>
sipa: maybe you are interested to have a look at #16577, which fixes a bug after which it should actually support rewinding