mlsmaycon f4d2b56420 [infrastructure] Resolve the module directory in readonly mode and thread ctx ...

Two problems with the lookup that finds this module's source for a suite in
another module.

A caller that vendors its dependencies puts the go command in automatic vendor
mode, where `go list -m -f {{.Dir}}` succeeds and reports an EMPTY directory —
vendor/ holds packages, not module source, so there is nothing for it to report.
The harness took that for a missing module and told the caller to run `go mod
download` for a dependency that was already there. Ask in readonly mode instead,
which resolves against the module graph and answers for both a cached module and
a local replacement, without writing to go.mod.

The lookup also ran on context.Background(), so a StartCombined, StartClient or
StartProxy whose context was cancelled could not stop it. repoRoot and moduleDir
now take the caller's context.

The vendor-mode case has a regression test, which needs no network: a temporary
main module with a local replacement, vendored. It fails without the flag with
the misleading "run `go mod download`" error. moduleDir takes the module path as
a parameter so that test can name its own.

The assertions move to testify, matching the repository's guidelines.

2026-08-12 05:58:39 +00:00

..

agentnetwork

[management] Rework Agent Network endpoint identity and settings bootstrap (#7085)

2026-08-10 19:06:55 +02:00

harness

[infrastructure] Resolve the module directory in readonly mode and thread ctx

2026-08-12 05:58:39 +00:00