test: Make sure we actually test the python timeouts (#175)

During the test, I also discovered that we have to force
`Retry(read=0)`, otherwise it will fail trying to rewind the zstd
stream.

Author: Swatinem

clients/python/src/objectstore_client/client.py

@@ -51,7 +51,7 @@ def __init__(
         self._usecase = usecase
 
         # We only retry connection problems, as we cannot rewind our compression stream.
-        self._retries = retries or urllib3.Retry(connect=3, redirect=5)
+        self._retries = retries or urllib3.Retry(connect=3, redirect=5, read=0)
         # The read timeout is defined to be "between consecutive read operations",
         # which should mean one chunk of the response, with a large response being
         # split into multiple chunks.

clients/python/tests/test_e2e.py

@@ -105,3 +105,17 @@ def test_full_cycle(server_url: str) -> None:
 
     with pytest.raises(ClientError, check=lambda e: e.status == 404):
         client.get(object_key)
+
+
+def test_connect_timeout() -> None:
+    # this server accepts the connection
+    # (even though the backlog is 0 and we never call `accept`),
+    # but will never reply with anything, thus causing a read timeout
+    s = socket.create_server(("127.0.0.1", 0), backlog=0)
+    addr = s.getsockname()
+    url = f"http://127.0.0.1:{addr[1]}"
+
+    timeout = urllib3.Timeout(connect=0.05, read=0.05)  # 50ms
+    client = ClientBuilder(url, "test-usecase", timeout=timeout).for_organization(12345)
+    with pytest.raises(urllib3.exceptions.MaxRetryError):
+        client.put(b"foo")