GeezerVisonThe World Wide Web, restored to 800 pixels of glory. |
| Home|About|Gaming cabinet|Archives|How it works|Starter sites |
GeezerVison is showing github.com — Calling SelectorSocketTransport.writelines with a very large payload doesn't get completely written to the socket · Issue #103462 · python/cpython Closed Labels 3.12only security fixesonly security fixestopic-asynciotype-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error DescriptionBug reportAs a consequence of the optimization introduced in #91166, when The following example can be used to reproduce the error: import asyncio async def send_message(chunk_size: int, chunks: int): await asyncio.sleep(1) reader, writer = await asyncio.open_connection("127.0.0.1", 9898) data = [bytes(chunk_size)] * chunks + [b"end"] writer.writelines(data) await writer.drain() writer.close() await writer.wait_closed() async def handle_message(reader, writer): data = await reader.read() print(f"End marker: {data[-3:]!r}") writer.close() await writer.wait_closed() async def run_server(): server = await asyncio.start_server(handle_message, "127.0.0.1", 9898) async with server: await server.serve_forever() async def main(): await asyncio.gather(run_server(), send_message(6500, 100)) asyncio.run(main()) The example above prints Your environment
Linked PRsActivity
MetadataMetadataAssigneesLabels3.12only security fixesonly security fixestopic-asynciotype-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error Projects
MilestoneRelationshipsDevelopmentIssue actions |
| You are visitor 01402503 — GeezerVison does not store the pages you look up. Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required. |