Too high GOMAXPROCS triggers "module [...] appears multiple times in workspace" error
Open
Nobody has claimed this yet.
bug
- Dominant language
- Go
- Stars
- 183
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Description
Bug description
context: https://github.com/gitpod-io/gitpod-next/pull/9019
tl;dr:
- when removing preexisting GOMAXPROCS limitations we ran into a build issue stating
go: module github.com/gitpod-io/gitpod-next/backend appears multiple times in workspace - it seems to be a race (not reproduceable with lower core count/different cache state), and probably in leeway
Steps to reproduce
- take recent main from gitpod-io/gitpod-next
- undo these changes: https://github.com/gitpod-io/gitpod-next/pull/9019
- make a change to
backendand push - see the CI failing with
[backend:app] go: module github.com/gitpod-io/gitpod-next/backend appears multiple times in workspace
Expected behavior
No response
Example repository
No response
Anything else?
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with Leeway's build and workspace handling, using the backend change and CI failure described in the issue as the reproduction. Compare behavior after undoing PR 9019 under higher GOMAXPROCS values and different cache states. Done means the backend build no longer reports that its Go module appears multiple times in the workspace.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100