#could not load module :: Daggerverse

1 messages · Page 1 of 1 (latest)

glossy lodge
#

Hm.. something funky is going on. @dusk lake can you please update the Daggerverse engine to 11.5 seems like its still on the old one.

I am trying to publish a new module made with dagger init and it runs into major issues

https://daggerverse.dev/mod/github.com/levlaz/daggerverse/containerd@643c2d87b1a9af3ab61281db751aca1ff7d740aa

Really feels like this is somethign we need to be able to test out locally before running publish, because when you have an automated release flow its very frustrating when things break even though they work locally.

dusk lake
glossy lodge
#

In any case I am seeing this error again

Stderr:
# dagger/containerd/internal/telemetry
internal/telemetry/proxy.go:50:14: cannot use proxySpan{…} (value of type proxySpan) as "go.opentelemetry.io/otel/trace".Span value in return statement: proxySpan does not implement "go.opentelemetry.io/otel/trace".Span (missing method AddLink)
internal/telemetry/proxy.go:59:20: cannot use proxySpan{} (value of type proxySpan) as "go.opentelemetry.io/otel/trace".Span value in variable declaration: proxySpan does not implement "go.opentelemetry.io/otel/trace".Span (missing method AddLink)

Don't recall what it means -- any pointers?

#

@dusk lake makes sense -- is there any way to do whatever is happening there locally to make sure there are no issues before hitting publish?

dusk lake
#

it's running asModule()

#

on your directory

glossy lodge
#

Do you have a min to pair?

#

In lounge

glossy lodge
dusk lake
#

waiting for you to call me...:D

glossy lodge
#

Oh sorry I am in the lounge already!