Oleksandr Danshyn

In case you see `{ code: 2, message: "Incomplete response" }` while you expect a properly set *error*, it might mean that the CORS configuration of your gateway/proxy does not...

Bumped into this issue too. The part of the first response's body that was not fully read is remaining in the underlying buffer. The second response reuses that buffer and...

@tomchristie thank you for your reply. let me share some more reasoning: 1. The HTTP 1.1 protocol is a request/response protocol. Unless `httpx` has a way of disabling **HTTP pipelining**...

meanwhile a pretty-bad looking workaround: ```python resp = self._client.patch(...) resp.read() # TODO: remove once https://github.com/encode/httpx/issues/1474 is # fixed resp.stream._stream._httpcore_stream.connection.close() ```

@rdozier-work thank you! it would be great to have a PyPI package for `docker-stubs`. meanwhile ``` docker-stubs @ git+https://github.com/rdozier-work/docker-stubs@9de7906804ae912f1d644c97b617ac77e784fca8 ```