-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
Update golang.org/x/net/idna to handle hostname started with numeric #18039
Conversation
Hi @outsideris! Thanks for looking into this. From looking at the history of I assume that the behavior change here is coming from the unicode tables update in that second commit. Given that switching from Unicode 9 to Unicode 10 may have other implications beyond this change, for safety I'd like to hold this update until our next major release, which has work in progress right now. This will allow us to mark the change as a compatibility note. Since everything under I'm going to label this as a breaking change (even though in practice it might not necessarily be) just to remind us to look at it again before the next release. Thanks again for working on this! |
It looks like |
Hi @outsideris, We are indeed now using Go modules to manage the The following commands should get the dependency updated, and then your new test can be cherry-picked onto it:
I expect this will update some transitive dependencies as well; that's okay since we can use the 0.12 prereleases cycle to reduce the risk of unexpected changes. |
Signed-off-by: Outsider <outsideris@gmail.com>
52ef88e
to
a2cb579
Compare
It looks like $ make test TEST=./svchost/
==> Checking that code complies with gofmt requirements...
go generate ./...
2018/10/26 05:10:56 Generated command/internal_plugin_list.go
go list ./svchost/ | xargs -t -n4 go test -timeout=2m -parallel=4
go test -timeout=2m -parallel=4 github.com/hashicorp/terraform/svchost
ok github.com/hashicorp/terraform/svchost (cached) |
Thanks for adding a test, @outsideris! I'll update this PR and merge it - thanks again for adding the test, that's fantastic. |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
When I try to use terraform module with a custom private registry, I found terraform doesn't handle correctly hostname started with a numeric character like
123.example.com
or1example.com
So, I updated
idna
and added a new test case.Previously, it throws an error like: