-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
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
NotImplementedError from aiohttp/server.py L268 #1537
Comments
Without the code, the likelihood of someone will help you is zero. |
The server-side code is at https://github.com/lablup/sorna-manager. It basically uses aiohttp.web and a SSL certificate -- you could check the initialization/shutdown process here. This exception happens in purely aiohttp, not in the request handlers I have written (between finish of my handlers and beginning of my handlers). Though, the tested request handler is here. The problem is, installing/configuring them is a non-trivial work. |
seems like asyncio bug |
@achimnol could you consistently reproduce this bug? |
@fafhrd91 Yes, I'm using uvloop. I could not reilably reproduce this bug though. |
Do you see it without uvloop? |
@1st1 I haven't tested this without uvloop. Further, I have not seen this bug after reporting this issue even using uvloop. |
@achimnol please re-open if you get more information |
@fafhrd91 I'm experiencing same issue with python 3.4
Code:
I use Python 3.4.3 (venv) and aiohttp 1.3.3. UPD: some request cause the exception, others are not. I tried to find a req that reproduces the problem, but havent found yet. Setting |
Issue reproduces every time request comes from Telegram when using webhook to get bot updates, but i cant recreate the request using |
I can reliably reproduce this when uploading a file (of more than about 50 KiB) through an HTTPS connection, and responding to it without reading the full request, e.g. like this:
|
Long story short
In my aiohttp-based API server logs, I could see the below exception very rarely (only once so far).
The line 117 in asyncio/transports.py is part of an abstract class
WriteTransport
.I think this suggests that the exception might be a bug.
Steps to reproduce
I don't know how to reproduce this exactly, but this happened during repeated API query authentication tests where the client was a NodeJS program using "fetch" API via a https (SSL) connection.
Your environment
Server: Python 3.6.0 + aiohttp 1.2
Client: Atom 1.12.9 (a custom plugin that uses
fetch()
API)The text was updated successfully, but these errors were encountered: