Initializing a new Dagger module on an existing Go project fails (DaggerGo SDK)

[analog heart]

Hello.

When running dagger init --name=my-module --sdk=go on an existing Go project I get the error below.

Running dagger init and then dagger develop --sdk=go returns the same error.

Dagger info: dagger v0.11.0 (registry.dagger.io/engine) darwin/amd64

Thanks!

Stdout:
generating go module: fr-cli
writing dagger.gen.go
creating directory internal
creating directory internal/dagger
writing internal/dagger/dagger.gen.go
creating directory internal/querybuilder
writing internal/querybuilder/marshal.go
writing internal/querybuilder/querybuilder.go
creating directory internal/telemetry
writing internal/telemetry/attrs.go
writing internal/telemetry/batch_processor.go
writing internal/telemetry/init.go
writing internal/telemetry/processor.go
writing internal/telemetry/proxy.go
writing internal/telemetry/span.go
writing main.go
running post-command: go mod tidy
needs another pass...
Stderr:
Error: generate code: template: alias.go.tmpl:74:3: executing "_dagger.gen.go/alias.go.tmpl" at <ModuleMainSrc>: error calling ModuleMainSrc: cannot find default codegen DaggerObject interface```

[naive finch]

Hey @analog heart 👋,
In your existing go project, is your go.modset to go 1.22 ?

It's not exactly the same error as yours but there is an issue that has been closed because this issue seems to be specific to the go ecosystem:
https://github.com/dagger/dagger/issues/7087

The reason why this is not related to dagger:
https://github.com/dagger/dagger/issues/7087#issuecomment-2056525531

Let me know if it helps. Thanks

[naive finch]

cc @broken reef: seems to be close to this issue but the error is not exactly the same: https://github.com/dagger/dagger/issues/7087

[lapis merlin]

hey @analog heart seems like the same issue to this one: https://discord.com/channels/707636530424053791/1222623250991943680

not sure if we ever opened a GH issue for this. I'll try to repro and open one.

[analog heart]

Hey folks, thanks for looking into this.
@naive finch My go.mod is set to go 1.22.2
After reading the thread in that GitHub issue I'm not sure how to fix or work around the issue though.

Will dagger init --name=my-module --sdk=go only work with go 1.21 at this stage?

For the record, I have run dagger init --name=my-module --sdk=go in an empty directory and then copied the generated files over the Go repo (v1.22.2) I want to use dagger in. Dagger seems to be working fine so far 👍 If you this approach may cause any issues down the road, please let me know.

It would be great if dagger init worked fine in Golang repos running the latest stable version.

[lapis merlin]

@analog heart is there a way you can help up with a simple repro?

I've tried to repro but I wasn't able. Here's what I did:

130|marcos:tmp/test3 (⎈ |N/A)$ go mod init test3
go: creating new go.mod: module test3
marcos:tmp/test3 (⎈ |N/A)$ de^C
130|marcos:tmp/test3 (⎈ |N/A)$ ls
go.mod
marcos:tmp/test3 (⎈ |N/A)$ de^C
130|marcos:tmp/test3 (⎈ |N/A)$ dagger init --sdk go
10:19:55 WRN no LICENSE file found; generating one for you, feel free to change or remove license=Apache-2.0
Initialized module test3 in .
marcos:tmp/test3 (⎈ |N/A)$ ^C
130|marcos:tmp/test3 (⎈ |N/A)$ dagger functions
Name             Description
container-echo   Returns a container that echoes whatever string argument is provided
grep-dir         Returns lines that match a pattern in the files of the provided Directory
marcos:tmp/test3 (⎈ |N/A)$

^ as you can see, that works!

[broken reef]

@lapis merlin @analog heart this is actually a known issue 😢 https://github.com/dagger/dagger/issues/6706

The answer is that we need to bump the engine to include the tooling for 1.22, see https://github.com/dagger/dagger/pull/7109

[lapis merlin]

@broken reef is the same issue though? My understanding from the GH issue is that if I change the go.mod from the generated module to use a newever version of Go, that'll break. From this thread, IIUC the issue is that somehow doing dagger develop on an existing Go project also raises an issue?

maybe the OP has somehow incorrectly setup his module that it's triggering #6706?

[broken reef]

if go.mod is set higher than 1.21, then yes, this is the same issue

[lapis merlin]

this is the Go SDK module go.mod you're talking about right?

I'm understanding from this thread that there are two go.mod files. One for the "project", and another for the module

[lapis merlin]

this example that I have here generates two go.mod files

one with 1.22 (project) and another with 1.21 (module)

[broken reef]

multiple go.mods aren't relevant for the issue in this thread i don't think

the issue is that you can't have 1.22 being in a go.mod that belongs to a dagger module

you get this specific error from here: https://github.com/dagger/dagger/issues/6706#issuecomment-1959206062

i think this should have been fixed though? we should be erroring out with a neater message, which is confusing