-
-
Notifications
You must be signed in to change notification settings - Fork 745
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
Rework IPv6 support #837
Rework IPv6 support #837
Conversation
6636fb7
to
08a92c0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me @florimondmanca , I just left minor comments
Co-authored-by: euri10 <euri10@users.noreply.github.com>
@euri10 Thanks for your comment on #837 (comment) — good point, just updated the PR to remove un,ecessary changes. |
no idea if github has an issue with their workflow at the moment but I had
to cancel the CI which was locked on Run tests after 13min, then pressed
re-run all jobs and it seems stuck again...you see this also on other
projects ?
…On Mon, Oct 26, 2020 at 3:08 PM Florimond Manca ***@***.***> wrote:
@euri10 <https://github.com/euri10> Thanks for your comment on #837
(comment)
<#837 (comment)> — good
point, just updated the PR to remove un,ecessary changes.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#837 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAINSPRVB5RM3BMKIO34YXDSMV7E5ANCNFSM4S5W2RFQ>
.
--
benoit barthelet
http://pgp.mit.edu/pks/lookup?op=get&search=0xF150E01A72F6D2EE
|
nah actually @florimondmanca I think you went too far in diff reduction, you need to revert last commit 01ffc58 because it's on the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
last commit breaks CI
@euri10 Yup, thanks — should be fixed now, CI should pass but let's see. :-) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lgtm 😎
Prompted by #836 (comment)
It looks like IPv6 support as added (or most likely fixed? I found #383 dating back from June 2019) into
0.12.2
to resolve #553. This was done via #803, which glossed over a small edge case leading tohost="localhost"
not working anymore, leading to issue #825, and then a fix via #827.But @euri10 mentioned in #827 that the fix wasn't the prettiest, so I went ahead and started this whole thing all over — here's what I did in this PR…
test_run()
test so that it tests all three cases: default case (127.0.0.1
), DNS hostname (localhost
), and IPv6 ([::]
).--host
now supports IPv6 addresses, with an example.It might be easy to review commit-by-commit, since the overall diff conflates reverts and the actual re-implementation. :-)
Note: for the changelog, we'll probably want to not mention #827, and mention this PR instead (if we decide to merge it).