goenv | Golang Version Management | GCP library

I solved the issue, though I'm still unclear on why that particular error message was showing up. Here's what I did:

I thought I might find answers in Heroku error logs on my computer. I couldn't use the heroku logs command, but I could search manually. Heroku's website says that these are located here ~/Library/Caches/heroku/error.log on macOS. But this directory didn't exist. There was no heroku folder in ~/Library/Caches/. I still had Heroku - which heroku correctly returned the path /usr/local/bin/heroku.

At this point I wondered whether the CleanMyMac X software I had used to clear storage space before updating my OS might have deleted the Heroku folder along with old error logs, and this might have prevented the program from opening?

Solution: I uninstalled the Heroku CLI based on instructions from Heroku's website:

I found an answer here and it worked for me. The location of properties file matters.

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.

A Go string and a C string are entirely unrelated (except in that both are called strings, which is a lie for at least one of them).

Here Python is sending a C string because you've told it to, but Go expects a Go string, which has a completely diffrent layout so it blows up. And if it didn't blow up at the callsite it'd probably blow up when the GC tries to handle the string, which it can't, because it's not a Go string.

You want to look at the magical "C" pseudo-package: you need to take in a *C.char and copy that to a Go string using C.GoString before you can pass it to anything expecting a go String. Or something along those lines, my experience with cgo (especially calling into it) is limited to avoiding this as a bad idea.

Regardless you probably want to at the very least read the cgo documentation in full, FFI is tricky at the best of time, and FFI between two managed languages much more so.

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 :

Two things to try:

• Use Go 1.16 (which is the version currently used to build/run Fabric).
• Use Go installed to /usr/local/go with the official installer rather than installed with Homebrew.

If there really is something wrong with the imports in those files, which there shouldn't be unless they have been modified locally, use the goimports -l -w command for each of the files listed to correct them.

For reference, I am also using a Macbook Pro, running MacOS Monterey but previously with Big Sur, and make basic-checks runs cleanly for me with Go 1.16.9 on the latest main branch code.

Flag -l is used to indicate libraries that the linker is supposed to use to build your application. If it's a new laptop, it's possible that the libraries are not installed. You should be able to install the libraries needed using the following commands: