#Dagger Cloud

1 messages · Page 1 of 1 (latest)

viscid spade
#

That's not the error that was getting hit consistently before https://github.com/dagger/dagger/pull/10209

If you revert the commit in 10209 locally and re-run the TestClientGenerator tests you'll see the error. It's about go.mod requiring go 1.23.8. Have an explanation of why it was getting hit in that PR

GitHub

A bunch of TestClientGenerator tests started consistently failing out of band, turns out this is because:

gqlgen did a release 19h ago where their go.mod specifies go 1.23.8
dagger's go to...

frigid vortex
viscid spade
# frigid vortex Hmmm so I should add some logic in the test client gen to pin a specific go mod ...

IMO it would be better to fix this in the client generator code since otherwise users could very easily hit this.

There's logic for normal modules that adds dep versions that match the go sdk's versions: https://github.com/dagger/dagger/blob/97b3ef86a3c56472f57f62ff46201be11d2f5d08/cmd/codegen/generator/go/generator.go#L305-L305

So I imagine it might be possible to just re-use that (with some adjustments) maybe.

cc @analog sand if that makes sense to you too

GitHub

An open-source runtime for composable workflows. Great for AI agents and CI/CD. - dagger/dagger