TCP listener handler does not disconnect on EOF (netcat -N) about anyio HOT 7 CLOSED

Ok, I figured it out. Strange that this hasn't come up before. What happens here is that AnyIO's stream protocol signals about the EOF simply by setting the receive event, but if there's also data in the buffer, the receive() call just reads the data and clears the flag, thus erasing any evidence of the EOF condition.

from anyio.

Could you review the PR that fixes it? That would help.

from anyio.

For reference, what does the synchronous Python server implementation look like?

from anyio.

Curiously, this works fine with the trio backend.

from anyio.

I now have a regression test that fails on asyncio and passes on trio.

from anyio.

Thanks @agronholm, that was way too fast for me to answer or provide more code :) I think it is not relevant anymore, but before I was using a more basic example without the TextReceiveStream wrapper, like in the documentation. It had the same issue.

from anyio.

Could you review the PR that fixes it? That would help.

Did that, and adjusted the example in case somebody does copy-paste, because TextReceiveStream does iterate lines.

from anyio.