diff options
| author | MarcoFalke <falke.marco@gmail.com> | 2019-08-09 09:46:46 -0400 |
|---|---|---|
| committer | MarcoFalke <falke.marco@gmail.com> | 2019-08-09 09:47:35 -0400 |
| commit | 9ab9d6356938ffe069ffc005a371d5405976823e (patch) | |
| tree | d9b74c68f911c04de7800f643c5a977b3a1778de /src/crypto | |
| parent | 32776276ef070e06f10dbcbe56ff2fba402293ad (diff) | |
| parent | b7b9f6e4cee262004643e2fe03d56cb47fdbf5c2 (diff) | |
| download | bitcoin-9ab9d6356938ffe069ffc005a371d5405976823e.tar.xz | |
Merge #16503: Remove p2pEnabled from Chain interface
b7b9f6e4cee262004643e2fe03d56cb47fdbf5c2 Remove p2pEnabled from Chain interface (Antoine Riard)
Pull request description:
RPC server starts in warmup mode, it can't process yet calls, then follows connection manager initialization and finally RPC server get out of warmup mode. RPC calls shouldn't be able to get P2P disabled errors because once we initialize g_connman it's not unset until shutdown, after RPC server has been stopped.
@mzumsande comment in #15713 let me thought that `p2pEnabled` was maybe useless, `g_connman` is always initialized before RPC server is getting out of warmup. These checks against P2P state were introduced in https://github.com/bitcoin/bitcoin/pull/8085/commits/5b446dd5b11d4f403554bc2dd5a7a94c7d20422a.
ACKs for top commit:
promag:
ACK b7b9f6e4cee262004643e2fe03d56cb47fdbf5c2
jnewbery:
ACK b7b9f6e4cee262004643e2fe03d56cb47fdbf5c2
Tree-SHA512: 4de2b9fc496bf8347ff5cc645848a5a44c8ca7596cd134f17f3088f5f8262d1d88b8e2a052df93e309ec9a81956a808df17a9eb9f10d4f4d693c95d607fe3561
Diffstat (limited to 'src/crypto')
0 files changed, 0 insertions, 0 deletions