1A teammate resolves a merge conflict by deleting go.sum, and the next build stops with missing go.sum entry for module providing package .... Did deleting it change which versions the project builds?Easy
2The Makefile line go get github.com/golang/mock/mockgen stopped producing a binary when the team moved to Go 1.18, and go generate ./... now dies with mockgen: command not found. What replaced it?Easy
3After go mod tidy your go.mod went from 6 requires to 40, most of them marked // indirect, and the reviewer wants to know whether the dependency set actually grew. What does the marker mean?Easy
4go build ./... prints import cycle not allowed for internal/service -> internal/store -> internal/service. What is the idiomatic fix, and why does the compiler refuse instead of resolving it?Easy
5You run go get github.com/acme/kit@v1.4.0 and a colleague coming from npm asks why that did not also pull the newest golang.org/x/net, and where the lock file is. What rule is the go command following?Medium
6You tag v2.0.0 on your library and nobody gets it: go get -u keeps returning v1.9.3, and a consumer who hardcodes the tag is told the go.mod has a different module path. What did you skip?Medium
7Your library works around a broken upstream with replace old => fork in its own go.mod, its tests pass, you tag it — and the first service that imports the library gets the broken upstream back. Why?Medium
8CI on a Go 1.22 image happily builds a module whose go.mod says go 1.23.4, while a colleague sees go.mod requires go >= 1.23.4 (running go 1.22.5; GOTOOLCHAIN=local). What is the go directive actually doing?Medium
9Adding an internal module git.corp.example/team/lib fails in CI with a 410 Gone from sum.golang.org and a proxy fetch that times out. Which setting is missing, and what would make the build work with no network at all?Medium
10A scanner flags github.com/foo/bits v0.0.0-20220331121500-1a2b3c4d5e6f in your build, yet no source file imports it and no hand-written require mentions it. How do you find who pulls it in, and what is that version string?Medium
11The files behind //go:build integration stopped compiling three weeks ago and nobody noticed until the nightly job ran — go build ./..., go vet ./... and every editor stayed green. What is the mechanism, and what do you change?Medium
12//go:embed web/dist is right there above the variable and the site works locally, but in the container every request for /_app/entry.js and /.vite/manifest.json returns file does not exist. What is being skipped?Medium
13The same commit builds on every developer's machine and fails in CI with no required module provides package example.com/lib. The repo root has a git-ignored go.work. What is the mechanism, and how should the two modules be developed?Hard
14A binary cross-compiled on a macOS laptop runs fine in the golang image; copied into FROM scratch it fails on the first outbound HTTPS call with x509: certificate signed by unknown authority and on time.LoadLocation with unknown time zone. What is missing?Hard
15Two CI runs on the same commit produce binaries with different sha256, and release engineering also wants myapp version to print the commit. What makes the build byte-identical, and where does the version come from?Hard
16A dependency scanner opens thirty PRs a week for CVEs in transitive modules your code never calls, while a fmt.Printf("%d", user.Name) shipped to production. How do you set the tooling up so the signal inverts?Hard