-
-
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
resolver.py/ThreadResolver: address[3] does not exist #5901
Comments
Lines 27 to 39 in 60f5727
From the Python doc, the
The behavior is strange, not as stated in the doc. 😕 Ref: https://docs.python.org/3.8/library/socket.html#socket.getaddrinfo |
IIRC, it returns the structure from the underlying kernel syscall. FWIW I think this has been fixed by #5176 on |
Duplicate of #5156. Please post any other observations or/and a reproducer there. |
Describe the bug
As outlined at pimutils/vdirsyncer#916, I use python 3.8 with aiohttp 3.8 branch (v3.7.4.post0-209-g22f8be99) . In aiohttp/resolver.py:ThreadedResolver the line
fails, as address has only two elements and address[3] is out of range.
The values of adress are:
The system is not connected to IPv6, no routes, no iPv6 addressese etc, but the kernel understands IPv6. I fixed it locally with:
To Reproduce
See above.
Expected behavior
Shall not read address[3], when address[3] does not exist.
Logs/tracebacks
Python Version
aiohttp Version
multidict Version
yarl Version
OS
Linux from Scratch, python 3.8.8+
Related component
Client
Additional context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: