godeps | github.com/ToQoz/go-deps reveals go pkg dependencies

The correct solution would be to invoke dep ensure -add package/name yourself and then just start using the package without manually importing it, the IDE will figure out that you want to use that package and will add the import automatically. The current behavior you are experiencing is exactly what's expected from the IDE since goimports is invoked on save and because the import is not used it will be automatically removed.

Your app starts but is getting killed because you don't bind your webserver to the specified port. This is clear from the log message:

2019-07-08T05:03:48.131507+00:00 heroku[web.1]: Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch

On Heroku you have to bind your HTTP server to the port specified by the PORT environment variable. Your app will be publicly available on default HTTP and HTTPS ports with the help of Heroku gateways.

So start your server on the expected port. Instead of this:

You are not displaying the address of the struct, you are displaying the address of the address (address of the pointer). The pointer is passed as a parameter and thus new each time. Remove the & in log.Printf("Whatever.GetNameByReference() memory address: %v", &whatever) to get what you want (and use %p instead of %v).

The problem unrecognized import path (import path does not begin with hostname) problem happens when part of your code imports some packages the travis can not arrive.

In my case, one of my code import errorX,and errorX is my local package,travis can not download from anywhere on the github.

I fix it by import "github.com/fwhezfwhez/errorx"

I remember this issue, quoting from https://github.com/tools/godep/issues/164#issuecomment-101345584

This seems to be caused by this line here: https://github.com/tools/godep/blob/master/update.go#L205

If packages A and B are under the same root, and I try to only update B, the root will be marked for skipping update because A isn't being updated. I'm not sure what the motivation for this feature is, it seems that developers should be able to selectively update sub packages as they desire.

For what it's worth, I fixed my problem by globbing from the root in my godep update command (e.g. godep update github.com/foo/bar/... instead of github.com/foo/bar/pkg/B. A helpful error message would have gone a long way

While you're here, go 1.11 and above has inbuilt module support. Maybe look into shifting into that? https://github.com/golang/go/wiki/Modules

Looks like the Go version you are using in your application is not a supported Cloud Foundry Go buildpack version on IBM Cloud. The same is mentioned in the build error as well. As per the documentation here,

The following Go versions are available in the Go buildpack currently installed in IBM Cloud:

1.6.3 1.6.4 1.7.5 1.7.6 1.8.6 1.8.7 1.9.3 1.9.4 1.10

If your app requires a Go version that is not listed, you can use the external Go buildpack to deploy the application.

To check the latest supported buildpacks, you can always run this command

Make variables can probably do what you want:

I just realized that when I clone the project, I should not do a git clone but rather do:

You've copied outdated code, which won't compile.

code.google.com/p/go.net/context

code.google.com has shut down, this is an old import path which can no longer be used. The error tells you what has gone wrong, that path can't be imported as it doesn't exist (try visiting it in a browser).

You could try to spend a lot of time fixing up the old imports, only to find that the packages have changed anyway and will no longer compile, so I'd recommend starting with the latest version and contacting the authors of github.com/ipfs/go-ipfs on github, or choosing another package to work with.