go: do not use sumdb when running go build during pacmak
- Dominant language
- TypeScript
- Stars
- 2.9k
- Forks
- 267
- Avg merge
- 1d 25m
- Merged PRs (30d)
- 14
Description
## :bug: Bug Report
### Affected Languages
- [x] `Golang`
- [ ] `TypeScript` or `Javascript`
- [ ] `Python`
- [ ] `Java`
- [ ] .NET (`C#`, `F#`, ...)
### General Information
* **JSII Version:** 1.20.0
* **Platform:** _any_
### What is the problem?
By default, `go get` (and `go build`) uses go sumdb when resolving dependencies, but since sumdb takes some time to cache the module from GitHub, it makes sense that when we run `go build` during `pacmak`, we will disable sumdb by setting `GOSUMDB=off`.
Contributor guide
Research direction
Start by tracing the pacmak path that invokes `go build` while resolving Go dependencies. Check how that invocation handles `GOSUMDB`, then verify that the build runs with `GOSUMDB=off` and that dependency resolution no longer waits for sumdb caching.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, typescript
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100