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
see: https://bugs.python.org/issue29930
naz/naz/client.py
Line 1312 in 5ebeffe
The text was updated successfully, but these errors were encountered:
I think we also need to acquire an asyncio.Lock for the code to re-establish connection:
Line 1206 in ae4bae4
Sorry, something went wrong.
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.
see: https://bugs.python.org/issue29930
naz/naz/client.py
Line 1312 in 5ebeffe
We need to acquire an asyncio.Lock around that code.
The text was updated successfully, but these errors were encountered: