forked from M-Labs/artiq
1
0
Fork 0

protocols: better workaround for asyncio issue 263

This commit is contained in:
Sebastien Bourdeauducq 2015-10-20 00:35:33 +08:00
parent 71d2e3a69f
commit 1bc4061620
3 changed files with 10 additions and 9 deletions

View File

@ -2,7 +2,7 @@ import asyncio
import logging
from artiq.protocols.asyncio_server import AsyncioServer
from artiq.tools import TaskObject
from artiq.tools import TaskObject, workaround_asyncio263
logger = logging.getLogger(__name__)
@ -119,19 +119,12 @@ class LogForwarder(logging.Handler, TaskObject):
try:
reader, writer = await asyncio.open_connection(self.host,
self.port)
detect_close = asyncio.ensure_future(reader.read(1))
writer.write(_init_string)
while True:
message = await self._queue.get() + "\n"
writer.write(message.encode())
await workaround_asyncio263()
await writer.drain()
# HACK: detect connection termination through the completion
# of a read operation. For some reason, write/drain operations
# on a closed socket do not raise exceptions, but print
# "asyncio:socket.send() raised exception."
if detect_close.done():
await asyncio.sleep(self.reconnect_timer)
break
except asyncio.CancelledError:
return
except:

View File

@ -16,6 +16,7 @@ from functools import partial
from artiq.protocols import pyon
from artiq.protocols.asyncio_server import AsyncioServer
from artiq.tools import workaround_asyncio263
_init_string = b"ARTIQ sync_struct\n"
@ -233,6 +234,7 @@ class Publisher(AsyncioServer):
line = await queue.get()
writer.write(line)
# raise exception on connection error
await workaround_asyncio263()
await writer.drain()
finally:
self._recipients[notifier_name].remove(queue)

View File

@ -175,3 +175,9 @@ class Condition:
for fut in self._waiters:
if not fut.done():
fut.set_result(False)
# See: https://github.com/python/asyncio/issues/263
@asyncio.coroutine
def workaround_asyncio263():
yield