[hmdsefi]

Adds a FAQ entry for the error people hit when they add a nested module (harness/etcdraft, shims/grpcsim, runner/toolexec) at an explicit version, and points to it from llms.txt so agents find it.

go: module github.com/hmdsefi/faultline@v0.2.0 found, but does not contain package github.com/hmdsefi/faultline/harness/etcdraft

The entry says when it shows up (go.mod already requires the root module, and the module cache does not hold the nested module yet), and gives two fixes: leave the version off, or go mod download the nested module before the versioned go get. For the wrapper, it downloads runner/toolexec and then runs go get -tool.

How it was checked, with go1.27.1 in new modules with an empty GOMODCACHE:

• With the root at v0.2.0 required, go get .../harness/etcdraft@v0.2.0, .../shims/grpcsim@v0.2.0 and go get -tool .../faultline-toolexec@v0.2.0 all fail with the message above. go get -x shows no request to the module proxy for the nested module.
• With the root at v0.1.2 required, go get .../harness/etcdraft@v0.2.0 fails the same way.
• The unversioned go get and both go mod download sequences add v0.2.0, with the root at v0.2.0 or v0.1.2. The tool line lands in go.mod.
• Two forms that work with a warm cache fail from an empty one, so the entry does not suggest them: one go get that names the root and the nested module, and go mod edit -require followed by go get.
• The page's blocks, run in order from an empty cache, give the output shown, byte for byte.

Docs only. Nothing in the code changes.

[coderabbitai]

Important

• Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

Run configuration

• Source mode: Auto
• Repository: hmdsefi/faultline
• Branch: docs/go-get-nested-version
• File: .coderabbit.yaml
• Commit: ea70d9c
• Layers: Repository YAML
• Review profile: CHILL
• Plan: Advanced
• Run ID: 52e2c99d-fa9c-4e90-b625-aa8e182921fb

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

• X
• Mastodon
• Reddit
• LinkedIn