cmd/go: direct dependencies may be marked indirect

[reverse-direction-god]

Go version

go 1.23.2

Output of go env in your module/workspace:

google.golang.org/grpc cloud.google.com/[email protected]
google.golang.org/grpc github.com/client9/[email protected]
google.golang.org/grpc github.com/golang/[email protected]
google.golang.org/grpc github.com/golang/[email protected]
google.golang.org/grpc github.com/golang/[email protected]
google.golang.org/grpc github.com/golang/[email protected]
google.golang.org/grpc github.com/kisielk/[email protected]
google.golang.org/grpc [email protected]
google.golang.org/grpc golang.org/x/[email protected]
google.golang.org/grpc golang.org/x/[email protected]
google.golang.org/grpc golang.org/x/[email protected]
google.golang.org/grpc golang.org/x/[email protected]
google.golang.org/grpc golang.org/x/[email protected]
google.golang.org/grpc golang.org/x/[email protected]
google.golang.org/grpc golang.org/x/[email protected]
google.golang.org/grpc google.golang.org/[email protected]
google.golang.org/grpc google.golang.org/[email protected]
google.golang.org/grpc honnef.co/go/[email protected]

What did you do?

I hope to obtain the dependency tree of the go project using the go mod graph command. You can see some direct dependencies output by this command compared to the information in go.mod. Some of the dependencies in go.mod that have//direct annotations are considered direct dependencies in the output information of the go mod graph command

What did you see happen?

Some indirect dependencies in the go.mod file are considered direct dependencies after the output of the go mod graph

What did you expect to see?

At present, the go mod graph command cannot accurately display the dependency tree

[gabyhelp]

Related Issues

• cmd/go: separate direct and indirect dependencies in go.mod #27887 (closed)
• x/blog:Only direct dependencies are recorded in the go.mod file: needs a recheck. #43153 (closed)
• cmd/go: why go get will add indirect dependency into go.mod #35080 (closed)
• cmd/go: `go mod -graph` erroneously lists edges from the main module to indirect dependencies #26489 (closed)
• about using 'go mod graph' #47262 (closed)
• cmd/go: 1.17 `go mod tidy` produces go.mod files that cannot be used with `go mod graph` to understand the source of dependencies #47648
• cmd/go: go mod graph shows indirect dependencies as requirements of main module #27309 (closed)
• cmd/go: `go list` reports all dependencies as indirect with workspaces #66789 (closed)
• cmd/go: show why indirect dependencies are needed #26620 (closed)
• cmd/go/mod/why: failed to show shortest paths for indirect modules in the import graph #36428 (closed)

_{(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)}

[seankhliao]

please include an actual reproducer.

[gopherbot]

Timed out in state WaitingForInfo. Closing.

(I am just a bot, though. Please speak up if this is a mistake or you have the requested information.)