#dang-sdk loading
1 messages · Page 1 of 1 (latest)
nothing weird, no
https://dagger.cloud/kpenfound/traces/c25ee4170479d04fac17e5957795ebf7
here's some engine logs (split up because no nitro)
time=2026-02-11T02:13:37.491Z level=WARN msg="process did not complete successfully" process=/runtime
error="exit code: 2\ngithub.com/dagger/dagger/internal/buildkit/util/stack.Enable\n\t/app/internal/bui
ldkit/util/stack/stack.go:82\ngithub.com/dagger/dagger/engine/buildkit.exitError\n\t/app/engine/buildk
it/executor.go:440\ngithub.com/dagger/dagger/engine/buildkit.(*Worker).runContainer\n\t/app/engine/bui
ldkit/executor_spec.go:1402\ngithub.com/dagger/dagger/engine/buildkit.(*Worker).run\n\t/app/engine/bui
ldkit/executor.go:222\ngithub.com/dagger/dagger/engine/buildkit.(*Worker).Run\n\t/app/engine/buildkit/
executor.go:174\ngithub.com/dagger/dagger/core.(*Container).WithExec\n\t/app/core/container_exec.go:48
1\ngithub.com/dagger/dagger/core/schema.(*containerSchema).withExec\n\t/app/core/schema/container.go:1
106\ngithub.com/dagger/dagger/dagql.NodeFuncWithCacheKey[...].func1\n\t/app/dagql/objects.go:930\ngith
ub.com/dagger/dagger/dagql.Class[...].Call\n\t/app/dagql/objects.go:302\ngithub.com/dagger/dagger/dagq
l.ObjectResult[...].call.func2\n\t/app/dagql/objects.go:763\ngithub.com/dagger/dagger/engine/cache.(*c
ache[...]).GetOrInitializeWithCallbacks.func3\n\t/app/engine/cache/cache.go:496\nruntime.goexit\n\t/us
r/lib/go/src/runtime/asm_arm64.s:1268"
[buildkit] [client=hctee7ijdqv8epgikarrybm3h] #65 ERROR: exit code: 2
time="2026-02-11T02:13:37Z" level=error msg="solve error: exit code: 2" client_hostname=Mac.belt clien
t_id=hctee7ijdqv8epgikarrybm3h function= module=dang-sdk object=DangSdk session_id=36jn3l7r694k8vncuow
12nxwa span=47c47aacc1689191 spanID=fe7fa7099cfc8045 trace=c25ee4170479d04fac17e5957795ebf7 traceID=c2
5ee4170479d04fac17e5957795ebf7
time="2026-02-11T02:13:37Z" level=debug msg="ReadSnapshotPath: failed to stat file: lstat error: no su
ch file or directory" client_hostname=Mac.belt client_id=hctee7ijdqv8epgikarrybm3h function= module=da
ng-sdk object=DangSdk session_id=36jn3l7r694k8vncuow12nxwa span=47c47aacc1689191 spanID=fe7fa7099cfc80
45 trace=c25ee4170479d04fac17e5957795ebf7 traceID=c25ee4170479d04fac17e5957795ebf7
time="2026-02-11T02:13:37Z" level=debug msg="function call done" client_hostname=Mac.belt client_id=hc
tee7ijdqv8epgikarrybm3h function= module=dang-sdk object=DangSdk session_id=36jn3l7r694k8vncuow12nxwa
span=47c47aacc1689191 spanID=fe7fa7099cfc8045 trace=c25ee4170479d04fac17e5957795ebf7 traceID=c25ee4170
479d04fac17e5957795ebf7
time="2026-02-11T02:13:37Z" level=error msg="function call errored" client_hostname=Mac.belt client_id
=hctee7ijdqv8epgikarrybm3h error="exit code: 2 [traceparent:c25ee4170479d04fac17e5957795ebf7-fe7fa7099
cfc8045]" function= module=dang-sdk object=DangSdk session_id=36jn3l7r694k8vncuow12nxwa span=47c47aacc
1689191 spanID=fe7fa7099cfc8045 trace=c25ee4170479d04fac17e5957795ebf7 traceID=c25ee4170479d04fac17e59
57795ebf7
maybe there's some weird issue with the engine's cache?
nuked the dev engine cache and still got it, so ruled that out at least
are you able to run dagger -m github.com/vito/dang/dagger-sdk@7e250fd9ab63b01ae80e5db37c2d2baf3303472a functions?
yes
🙃
yeah i'm lost. Here's the error I got from my demo repo using the same build
Error: failed to resolve toolchain to source: failed to load git dep: failed to resolve dep to source: failed to load git dep: failed to load sdk for git module source: invalid SDK: "github.com/vito/dang/dagger-sdk" [traceparent:551e82895c8fe0960f429e92d53b1136-a3bd5793e4330201]
failed to resolve toolchain to source: failed to load git dep: failed to resolve dep to source: failed to load git dep: failed to load sdk for git module source: invalid SDK: "github.com/vito/dang/dagger-sdk" [traceparent:551e82895c8fe0960f429e92d53b1136-a3bd5793e4330201]
failed to resolve toolchain to source: failed to load git dep: failed to resolve dep to source: failed to load git dep: failed to load sdk for git module source: invalid SDK: "github.com/vito/dang/dagger-sdk" [traceparent:551e82895c8fe0960f429e92d53b1136-a3bd5793e4330201]
Those refs to the dang-sdk are unpinned because the toolchains i have dont have the sdk pinned right now
What specific command are you running? I did a dev engine build off main and then ran some stuff and don't hit it
also I could look at a trace too to see exactly where it's happening, which might have a hint
@hardy perch I'm spying on your traces: https://dagger.cloud/kpenfound/traces/9acb19d8aa647d7c26a8754c9d1f269f?listen=40405bda80224fe9#bb47e98464217eec it looks like the engine it's trying to connect to crashed
I have an extremely strong hunch this is the boltdb corruption issue
which explains this crash and the other thing you hit where the engine restarts constantly
nice! I'm running a few claude sessions on the side so there's a lot of other traces in there, but I was running check -l to trigger the dang issue
some of the engine crashes i'm hitting with the dev engine at the moment are because i have one session trying to make the version module work with worktrees 🤞
check -l on the dagger repo?
yes as well as my demo-react-app repo
Yeah when I do docker rm -fv dagger-engine.dev; docker volume rm dagger-engine.dev; ./hack/dev on latest main and then ./hack/with-dev dagger checks -l on the dagger repo, it works fine for me
did you double check your on latest main and don't have any local changes that would modify this somehow?
I definitely had local changes but I dont think they're related. Doing a build on main now to be sure
ok the build on main works, but there's no way my local changes caused this so i'm trying again on my other branch
have you rebased them lately?
oh i guess you would be if you're seeing that sha in the first place 
haha yeah i went through that same thing a few times
rebuilding my branch is broken again. So I guess I really did break it.. but I'm not seeing how its related
man, my changes were just to the graphql AsExecErr, but there was just a subtle bug in the http handler that happened to be exactly the same issue we had on main earlier 😭
Oh it triggered the error message of "invalid sdk"? I feel like I see that in way too many circumstances