golang.org/x/textaffected/package:

[prr123]

What version of Go are you using (go version)?

$ go version
1.21.3

Does this issue reproduce with the latest release?

yes

What operating system and processor architecture are you using (go env)?

ubuntu 22.04

go env Output

$ go env

can provide, but seems irrelevant

What did you do?

downloaded golang.org/x/net/http2

What did you expect to see?

a complete download

What did you see instead?

go: found golang.org/x/net/http2 in golang.org/x/net v0.17.0
go: downloading golang.org/x/text v0.13.0
go: client/http/http2simple imports
golang.org/x/net/http2 imports
golang.org/x/net/idna imports
golang.org/x/text/secure/bidirule: golang.org/x/[email protected]: read "https:/proxy.golang.org/@v/v0.13.0.zip": stream error: stream ID 19; INTERNAL_ERROR; received from peer
go: client/http/http2simple imports
golang.org/x/net/http2 imports
golang.org/x/net/idna imports
golang.org/x/text/unicode/bidi: golang.org/x/[email protected]: read "https:/proxy.golang.org/@v/v0.13.0.zip": stream error: stream ID 19; INTERNAL_ERROR; received from peer
go: client/http/http2simple imports
golang.org/x/net/http2 imports
golang.org/x/net/idna imports
golang.org/x/text/unicode/norm: golang.org/x/[email protected]: read "https:/proxy.golang.org/@v/v0.13.0.zip": stream error: stream ID 19; INTERNAL_ERROR; received from peer

[prr123]

I don't understand your answer. Are you saying that you are not maintaining golang.org/x/net/http2/h2c any longer?
If I was not clear: I am wrote a go program that links using the h2c libary. The h2c library relies on golang.org/x/text v0.13.0.

today golang.org/x/net was upgraded from v0.17.0 to v0.18.0 and relies on golang.org/x/net/http/httpguts which in turn requires golang.org/x/net/idna. The latter imports golang.org/x/text v0.14.0.
golang.org/x/text v0.14.0. download results in a stream error.
I can resubmit the bug report with the new versions, if you like.,

[seankhliao]

this looks more like a problem with your internet connection rather than something with the go project.

[prr123]

Here are some more facts and a proposed solution:

1. I can download the module with curl http1, but downloading with curl does not execute the other steps (calculating the hash) in the golang build system.
2. I was able to download sith go get to one of my servers
   It is very convenient to brush the problem aside by blaming the problem on the internet connection. But the issue is that the problem is connected with http2.
   My proposed solution is to offer an option in the go build system to fall back to http1 if a http2 download fails. That would be solution.