We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
in naz.Client.shutdown we call client.writer.close We need to call client.writer.drain before calling close.
naz.Client.shutdown
client.writer.close
client.writer.drain
And it also should probably call client.writer._transport.set_write_buffer_limits(0) before calling client.writer.drain
client.writer._transport.set_write_buffer_limits(0)
aio-libs/aiohttp#1369
The text was updated successfully, but these errors were encountered:
Issues/67 (#113)
5f34f83
What: - Introduce a configurable timeout when trying to connect to SMSC - Try and detect when the connection to SMSC is disconnected and attempt to re-connect & re-bind - bugfix; `asyncio.streams.StreamWriter.drain` should not be called concurrently by multiple coroutines[1] - when shutting down, `naz` now tries to make sure that write buffers are properly flushed[2][3] Why: - Make `naz` more failure tolerant - Fixes: #67 - Fixes: #114 - Fixes: #116 - Fixes: #117 - Fixes: #120 References: 1. https://bugs.python.org/issue29930 2. https://vorpus.org/blog/some-thoughts-on-asynchronous-api-design-in-a-post-asyncawait-world/ 3. aio-libs/aiohttp#1369
Successfully merging a pull request may close this issue.
in
naz.Client.shutdown
we callclient.writer.close
We need to call
client.writer.drain
before calling close.And it also should probably call
client.writer._transport.set_write_buffer_limits(0)
before callingclient.writer.drain
aio-libs/aiohttp#1369
The text was updated successfully, but these errors were encountered: