| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The issue is that ``os.read`` does not always read the expected number of
bytes, and thus we are moving to the next frame too early causing drift
in the byte stream. When the reading drifts, it starts reading garbage
as the next frame size. The some examples of frame sizes were
4032897957 bytes, etc. Values this large were causing the exceptions
from ``os.read``.
fixes #1211
Signed-off-by: Michael Merickel <michael@merickel.org>
|
|
|
|
|
|
|
|
|
| |
- Fix _get_raw_response_socket to always return the NpipeSocket object
- Override NpipeHTTPConnectionPool._get_conn to avoid crash in urllib3
- Fix NpipeSocket.recv_into for Python 2
- Do not call select() on NpipeSocket objects
Signed-off-by: Joffrey F <joffrey@docker.com>
|
|
|
|
|
|
|
| |
read_socket() is now just read(), because its behaviour is consistent
with `os.read` et al.
Signed-off-by: Aanand Prasad <aanand.prasad@gmail.com>
|
|
|
|
|
|
|
| |
This makes it more clearly high-level and distinct from the raw
data-reading functions
Signed-off-by: Aanand Prasad <aanand.prasad@gmail.com>
|
|
|
|
| |
Signed-off-by: Aanand Prasad <aanand.prasad@gmail.com>
|
|
|
|
| |
Signed-off-by: Aanand Prasad <aanand.prasad@gmail.com>
|
|
|
|
| |
Signed-off-by: Aanand Prasad <aanand.prasad@gmail.com>
|
|
|
|
|
|
|
|
| |
- `read_data()` raises an exception instead of asserting `False`
- `next_packet_size()` uses `read_data()`
- Renamed `packet_size` arg to `n` for consistency
Signed-off-by: Aanand Prasad <aanand.prasad@gmail.com>
|
|
|
|
| |
Signed-off-by: Aanand Prasad <aanand.prasad@gmail.com>
|
|
Signed-off-by: Aanand Prasad <aanand.prasad@gmail.com>
|