This should have no effect on mainnet users, but simplifies testing, where config settings are currently ignored with only a warning. Fix this by making it an error.
Issues:
Tested ACK dddd6f0.
$ cat bitcoin.conf
rpcport=54321
bitcoind -testnet
2019-03-21T14:58:35Z Bitcoin Core version v0.18.99.0-dddd6f0f5 (release build)
2019-03-21T14:58:35Z Error: Config setting for -rpcport only applied on test network when in [test] section.
Error: Config setting for -rpcport only applied on test network when in [test] section.
Deserves a small release note, just to point to if someone reports this behavior change?
Concept ACK
Nice usability improvement!
@MarcoFalke here's a test for your consideration 53469f780a8e2d88337f4efa6eb9ca52c9ce34f8.
72 | @@ -73,9 +73,14 @@ Example item 73 | Low-level changes 74 | ================= 75 | 76 | -Example item 77 | +Configuration 78 | ------------ 79 | 80 | +* An error is issued where previously a warning was issued when a setting in 81 | + the config file was specified in the default section, but not overriden for
Should be "overridden" :-)
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--174a7506f384e20aa4161008e828411d-->
No conflicts as of last run.
utACK fae38c3.