fix rpyc calls timing out after 30 seconds#2268
Conversation
added --timeout to manager arguments (default 1 hour) pass this setting through to rpyc.utils.factory.connect_channel()
|
Why 1 hour? |
Absolutely no reason and a completely arbitrary time that I'm in no way attched too - more then happy to change to whatever people feel is appropriate |
|
I think maybe something like 5 minutes? I'm not too sure what the consequence of this timeout is though. |
As far as I've seen locally, it just interupt's execution if, for example you run I'll update it to 5 minutes, It doesn't seem unreasonable - and there's a cli flag there anyway if the default isn't long enough for some insanely complex config. |
|
Cool. Thanks. |
|
where would the timeout flag be called? like this? edit: found the syntax from |
Motivation for changes:
rpyc started actually timing out sync requests in 4.0.0 tomerfiliba-org/rpyc#264
Detailed changes:
--timeoutargument to Managersync_request_timeoutto signature ofIPCClient.__init__()timeoutthrough toIPCClientinManager.start()Addressed issues:
Log and/or tests output (preferably both):