gh-135862: fix asyncio socket partial writes of non-1d-binary arrays #135974
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
asyncio
code is writing binary data to asocket.socket
, and advancing through the buffer after a partial write by doingmemoryview(data)[n:]
, wheren
is the number of bytes written.This assumes the
memoryview
is a one dimensional buffer of bytes, which is not the case e.g. for amemoryview
of anarray.array
of non-bytes, or anndarray
with more than one dimension. Partial writes of suchmemoryview
s will corrupt the stream, repeating or omitting some data.When creating a
memoryview
from amemoryview
, first convert it to a one-dimensional array of bytes before taking the remaining slice, thus avoiding these issues.Add an assertion that the remaining data is bytes, to guard against possible regressions if additional types of data are allowed in the future.