cc-s | 一个基于spring boot、druid、mybatis、mysql的后端基础 | Object-Relational Mapping library

for device, info in fetch_hostnames().items():

This for loop is unnecessary, as this is already performing the action to each one of the hosts:

results = exe.map(run_verification_commands, hosts)

Every time run_verification_commands is called, regardless of what was being passed to it, because the for loop is going against the original data, it will always grab the first host.

This can be resolved by instead passing in the data when you set up the concurrent futures:

This package requires go v1.16, please upgrade your go version or use the appropriate docker builder.

I've actually had the same problem and came up with the following solution.

I tried the installation steps on an ubuntu docker container and gitlab runs with no problem. in case someone is interested:

The answer to the wasm question (as you posted) talks about cgo. cgo invokes platform compiler with platform specific headers/libs (on Mac, with framework too). When you cross-compile with CC, you also need cross-compile compiler + headers/libs + frameworks. It is not easy: you may need tools like xgo. But still cross-compile may fail.

Go is different, Go re-implements a HAL in go or plan9 ASM on each OS/arch. So when you cross-compile cgo + go for am64 on arm64 together, go build will try to blend "cgo+arm64" with "go+amd64". Sadly, it is an empty set for the built-in go build tool.

Refer to the @fperson's own answer.

Only go install can work outside of any project (without a local .go.mod$

Since Go 1.16, if the arguments have version suffixes (like @latest or @v1.0.0), go install builds packages in module-aware mode, ignoring the go.mod file in the current directory or any parent directory if there is one.

This is useful for installing executables without affecting the dependencies of the main module.

go build is meant to be used within a local project, with its go.mod dependencies list. It compiles, but does not install, a package.

Finally, I figure it out and everything is working as expected, so it's nothing to do with net/http2.

For more details, please refer to this issue: https://github.com/golang/go/issues/50000.

Okay I solved my problem.

First, my WORKDIR wasn't pointing at the right directory : WORKDIR /go/src/github.com/rosmo/gcs2bq instead of WORKDIR /work/src/github.com/rosmo/gcs2bq but it's only because of me using /work instead of /go for the installed packages.

Then I added the follwing after the COPY main.go . command :

proxy_pass is allowed in a location context