diff options
author | Wladimir J. van der Laan <laanwj@protonmail.com> | 2019-10-16 16:00:39 +0200 |
---|---|---|
committer | Wladimir J. van der Laan <laanwj@protonmail.com> | 2019-10-16 16:00:49 +0200 |
commit | 5a3dd93594551efdc4059126b061b8c751ec3f29 (patch) | |
tree | 108203b4af6f3acc3d28fd7d4265cdd69d1fa9e9 /build_msvc | |
parent | 1f6638630ef8e196e9a7dd6a3e417c186e2cc7b9 (diff) | |
parent | b3b26e149c34fee9c7ae8548c6e547ec6254b441 (diff) | |
download | bitcoin-5a3dd93594551efdc4059126b061b8c751ec3f29.tar.xz |
Merge #17131: rpc: fix -rpcclienttimeout 0 option
b3b26e149c34fee9c7ae8548c6e547ec6254b441 rpc: fix -rpcclienttimeout 0 option (Fabian Jahr)
Pull request description:
fixes #17117
I understood the bug as the help string being wrong, rather than that this feature is missing and should be added. Let me know if it should be the other way around.
It is notable that if 0 is given as an argument, the fallback that is being used is the libevent default of 50 seconds, rather than `DEFAULT_HTTP_CLIENT_TIMEOUT` (900 seconds). This is not intuitive for the user. I could handle this in this PR but I am unsure which would be the better solution then: Actually adding the feature as described in the help string or falling back to `DEFAULT_HTTP_CLIENT_TIMEOUT`? Happy to hear opinions.
ACKs for top commit:
MarcoFalke:
unsigned ACK b3b26e149c34fee9c7ae8548c6e547ec6254b441
Tree-SHA512: 65e526a652c0adcdb4f895e8d78d60c7caa5904c9915b165a3ae95725c87d13af1f916359f80302452a2fcac1a80f4c58cd805ec8c28720fa4b91b3c8baa4155
Diffstat (limited to 'build_msvc')
0 files changed, 0 insertions, 0 deletions