This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Title: ProactorEventLoop cannot open connection to ::1
Type: Stage: resolved
Components: asyncio Versions: Python 3.5
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: Nosy List: bay, gregory.p.smith, gvanrossum, miss-islington, sebastien.bourdeauducq, vstinner, yselivanov
Priority: high Keywords: patch

Created on 2016-07-12 17:55 by sebastien.bourdeauducq, last changed 2022-04-11 14:58 by admin. This issue is now closed.

Pull Requests
URL Status Linked Edit
PR 7993 merged yselivanov, 2018-06-28 17:01
PR 8000 merged miss-islington, 2018-06-29 02:00
PR 8001 merged miss-islington, 2018-06-29 02:01
Messages (11)
msg270258 - (view) Author: Sebastien Bourdeauducq (sebastien.bourdeauducq) * Date: 2016-07-12 17:55
The following code fails with "OSError: [WinError 10022] An invalid argument was supplied".

import asyncio
loop = asyncio.ProactorEventLoop()
loop.run_until_complete(asyncio.open_connection("::1", 4242))

This is a regression in 3.5.2. 3.5.1 does not have this bug. Connecting to does not cause the problem.
msg270263 - (view) Author: Sebastien Bourdeauducq (sebastien.bourdeauducq) * Date: 2016-07-12 18:46
The first offending commit is this one:

more specifically "return af, type, proto, '', (host, port)". For IPv6, it should be "(host, port, flow info, scope id)" instead of just "(host, port)".
msg288712 - (view) Author: Sebastien Bourdeauducq (sebastien.bourdeauducq) * Date: 2017-02-28 12:35
This is still a problem with Python 3.5.3 and 3.6.0.
msg317997 - (view) Author: Sebastien Bourdeauducq (sebastien.bourdeauducq) * Date: 2018-05-29 09:28
Any chance someone could look into this bug?
msg320660 - (view) Author: bay (bay) Date: 2018-06-28 11:37
The bug is reproducible on Python 3.7. The connect call always fails when I
try to use connect to any IPv6 address with ProactorEventLoop.

The bug can be bypassed by adding "%0" to the IPv6 address. This will cause
to trigger this if construction:

As mentioned by Sebastian, it happen because the _ipaddr_info function returns
only the host and the port for IPv6: return af, type, proto, '', (host, port)

This (host, port) tuple used in ConnectEx call, but it expect 4-element tuple
to connect IPv6:
Instead it tries to connect, using IPv4 and fails.

The bug can be fixed by doing the following:
    if af == socket.AF_INET6:
        return af, type, proto, '', (host, port, 0, 0)
        return af, type, proto, '', (host, port)

instead of
    return af, type, proto, '', (host, port) 

msg320675 - (view) Author: Guido van Rossum (gvanrossum) * (Python committer) Date: 2018-06-28 16:42
Somebody please submit a PR so this can be fixed in 3.7.1 and the fix can
be backported to 3.6.7.
msg320676 - (view) Author: Yury Selivanov (yselivanov) * (Python committer) Date: 2018-06-28 17:05
> Somebody please submit a PR so this can be fixed in 3.7.1 and the fix can
> be backported to 3.6.7.

Somehow I overlooked this one when I was sifting the issues we needed to fix in 3.7.  I've opened a PR.
msg320693 - (view) Author: Yury Selivanov (yselivanov) * (Python committer) Date: 2018-06-29 01:59
New changeset d904c238ca3551750cb97d15d827c3e525970867 by Yury Selivanov in branch 'master':
bpo-27500: Fix static version of getaddrinfo to resolve IPv6 (GH-7993)
msg320694 - (view) Author: miss-islington (miss-islington) Date: 2018-06-29 02:16
New changeset 3ed44141216aa1d2d8dd7d170c2dc216a6e718b6 by Miss Islington (bot) in branch '3.7':
bpo-27500: Fix static version of getaddrinfo to resolve IPv6 (GH-7993)
msg320695 - (view) Author: miss-islington (miss-islington) Date: 2018-06-29 02:22
New changeset c00144cd7741a5060662e85717f6559ad46d02aa by Miss Islington (bot) in branch '3.6':
bpo-27500: Fix static version of getaddrinfo to resolve IPv6 (GH-7993)
msg333692 - (view) Author: Sebastien Bourdeauducq (sebastien.bourdeauducq) * Date: 2019-01-15 12:24
Thank you!
Date User Action Args
2022-04-11 14:58:33adminsetgithub: 71687
2019-01-15 12:24:02sebastien.bourdeauducqsetmessages: + msg333692
2019-01-15 12:13:50vstinnersetstatus: open -> closed
resolution: fixed
stage: patch review -> resolved
2018-06-29 02:22:42miss-islingtonsetmessages: + msg320695
2018-06-29 02:16:50miss-islingtonsetnosy: + miss-islington
messages: + msg320694
2018-06-29 02:01:42miss-islingtonsetpull_requests: + pull_request7608
2018-06-29 02:00:52miss-islingtonsetpull_requests: + pull_request7607
2018-06-29 01:59:43yselivanovsetmessages: + msg320693
2018-06-28 17:05:12yselivanovsetpriority: normal -> high

messages: + msg320676
2018-06-28 17:01:31yselivanovsetkeywords: + patch
stage: patch review
pull_requests: + pull_request7604
2018-06-28 16:42:41gvanrossumsetmessages: + msg320675
2018-06-28 11:37:33baysetnosy: + bay
messages: + msg320660
2018-05-29 09:28:31sebastien.bourdeauducqsetmessages: + msg317997
2017-02-28 12:35:36sebastien.bourdeauducqsetmessages: + msg288712
2017-01-25 22:24:21gregory.p.smithsetnosy: + gregory.p.smith
2016-07-12 18:46:27sebastien.bourdeauducqsetmessages: + msg270263
2016-07-12 17:55:35sebastien.bourdeauducqcreate