#Debug `cannot define methods on objects
1 messages · Page 1 of 1 (latest)
@grim thicket what the heck is this failure about ? You can use dagger trace ba579d7829c670ee37f0be627f1697f3
I’ll pull the trace and check the failing step.
The failure is core/integration → TestGo/TestExtendCore, specifically in_different_mod_name and in_same_mod_name.
The test creates a Go module, writes internal/dagger/more.go with a method on *Container, then runs dagger query. That still fails, but the error text changed.
Expected substring:
type "Container" is already defined by module "daggercore"
Actual error:
Error: generate code: template: module.go.tmpl:93:3: executing "_dagger.gen.go/module.go.tmpl" at <ModuleMainSrc>: error calling ModuleMainSrc: cannot define methods on objects from outside this module
So this looks like a regression in error reporting / wrapping, or a test expectation that needs updating if the new error is intentional. Not a random infra failure; 436 tests passed and only these 2 Go extend-core cases failed.
it's from PR 12957 but i never changed anything for Container.