Open daniel-sanche opened 3 months ago
Most rpc calls support passing in a retry and timeout value to configure retry parameters (example: WriteBatch.commit)
But when timeout=None, that means it uses the api default, meaning there is no way to truly disable timeouts
timeout=None
That said, fixing this would likely be a breaking change, and timeout can always be set arbitrarily high, so this is a low-priority fix
Most rpc calls support passing in a retry and timeout value to configure retry parameters (example: WriteBatch.commit)
But when
timeout=None, that means it uses the api default, meaning there is no way to truly disable timeoutsThat said, fixing this would likely be a breaking change, and timeout can always be set arbitrarily high, so this is a low-priority fix