#Hey everyone! 👋 Before I file an
humble breach
Configuration (dagger.json):
{
"name": "ci",
"engineVersion": "v0.19.8",
"sdk": {
"source": "go",
"config": {
"goprivate": "github.com/<org>/private/libs"
}
}
}
Environment :
- sdk.config.goprivate is correctly set.
- Host has url."git@github.com:".insteadOf "https://github.com/" configured.
- SSH agent is healthy; ssh -T git@github.com succeeds.
- Command used: dagger call -m . --socket=$SSH_AUTH_SOCK
The Error:
INFO writing path=internal/dagger/dagger.gen.go
INFO needs another pass...
go: github.com/<org>/private/libs@v0.0.0...: invalid version:
fatal: could not read Username for 'https://github.com': terminal prompts disabled
Error: ensure dagger package: failed to get dagger.io/dagger@: exit status 1
Suspected Changes in v0.20.4:
- #11826: Pinning the Go package in module generation. This adds the go get dagger.io/dagger@<sha> step, which seems to trigger the transitive resolution failing here.
- #11962: Generating dependencies in separate files. This introduces the needs another pass... logic where the crash occurs.
teal relic
fwiw, I use https based private git repo access and dagger still works fine even in 0.20.6. So this seems related to SSH_AUTH_SOCK. @brisk wyvern
lean otter
It's definitely worth filing the issue. 0.20.4 carries a first chunk of the modules v2 refactor. It was supposed to be neutral but we've had a few other issues
humble breach
Will make a proper bug report
For reference https://github.com/dagger/dagger/issues/13056
brisk wyvern
For reference https://github.com/dagger/dagger/issues/13056
thank you, will try to take a look this week, just assigned it to myself 🙏