go-diff | Unified diff parser and printer for Go | Code Quality library

Because in Go 1.17 the module graph has been changed to enable pruning and lazy loading. The second require block contains indirect dependencies.

https://golang.org/doc/go1.17#go-command

If a module specifies go 1.17 or higher, the module graph includes only the immediate dependencies of other go 1.17 modules, not their full transitive dependencies. [...]

[...] If a module specifies go 1.17 or higher in its go.mod file, its go.mod file now contains an explicit require directive for every module that provides a transitively-imported package. (In previous versions, the go.mod file typically only included explicit requirements for directly-imported packages.)

Because the number of explicit requirements may be substantially larger in an expanded Go 1.17 go.mod file, the newly-added requirements on indirect dependencies in a go 1.17 module are maintained in a separate require block from the block containing direct dependencies.

Note: the go.mod file that you posted in your question has //indirect dependencies in the first require block. I suspect, inferring from the quoted docs "newly-added" term, that this is because those //indirect dependencies were already listed there and go mod tidy doesn't rearrange them. If you:

• manually delete one of those
• and/or recreate the go.mod file with Go version set to 1.17 or higher
• and/or run go mod tidy -go=1.17

then it will properly separate direct and //indirect dependencies in the two blocks. At least this is what I see empirically in my projects. Still looking for a more explicit mention in the docs.

Check this

You have at least 2 solutions :

1. Use cloud.google.com/go/logging
2. Use a generic logging framework (like logrus) and a special Stackdriver adapter to have logs with the right format and right level in Stackdriver logging

This is the default solution I think :

You are probably using Go 1.13 to develop your application.

In this case, whenever you run a Go command, like go build, go list, go test, go mod tidy and others, the go.mod file will be modified to have some formatting included, and add missing directives, like the Go version that's compatible with that module.

So, go 1.13 is added to the file automatically, not by the IDE. You can reproduce this by running any of the commands that I listed above.

The App Engine Standard Go environnement sets a number of environment variables automatically. You can have a look at the list here.

You can check if they are set and if they aren't, then your code is running locally (or at least not deployed). Or you can set the NODE_ENV environment variable to development on your machine (in your shell where you run your app locally, not in the app.yaml file) and check for its value. It'll be set to production when running on App Engine.