goldmark | markdown parser written in Go

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.

Wow I finally can answer this! It turns out that having my working directory in a google drive was the issue. Since it worked for hugo-lithium, I didn't think of it. I don't know enough to say why hugo-lithuim works while others don't though. Hopefully this helps others who may come across the same issue.

Please refer to this answer https://stackoverflow.com/a/63206852. If you use a config.yaml, it should include:

Since you didn't mention it above: did you instrument a Go application? The Elastic APM Go "Agent" is a package which you use to instrument your application source code. It is not an independent process, but runs within your application.

So, first (if you haven't already) instrument your application. See https://www.elastic.co/guide/en/apm/agent/go/current/getting-started.html#instrumenting-source

Here's an example web server using Echo, and the apmechov4 instrumentation module: