do i have to run dagger install for a module dependency each and every time in ci?

[novel locust]

i'm getting this error message

Error: input: moduleSource.withContextDirectory.asModule resolve: failed to create module: select: failed to update module dependencies: failed to load module dependencies: select: failed to load pre-configured dependencies: failed to create module source from dependency: select: failed to resolve git src to commit: failed to checkout remote https://github.com/Dudesons/daggerverse: git error: exit status 128
stderr:
fatal: unable to read tree (5a0943df5ceca43ab24309e5331f0bac26208a58)

it goes away if i run dagger install github.com/Dudesons/daggerverse/secret-manager@v0.2.0 what is the purpose of the dagger.json if i have to run dagger install github.com/Dudesons/daggerverse/secret-manager@v0.2.0 in each new deployment or am i doing something wrong?

[shrewd dust]

👋what ref do you have in your dagger.json?

@novel locust one thing that I notice is that you seem to have pushed the tag for that commit but haven't pushed the commit to any branch: https://github.com/Dudesons/daggerverse/commit/5a0943df5ceca43ab24309e5331f0bac26208a58

so some git opreations might be failing. When / how are you getting the error shown above?

[novel locust]

https://app.warp.dev/block/G4ixopyZHFihkBQFBxwMyE

i get the error when i have a fresh check of my code, without having run dagger install github.com/Dudesons/daggerverse/secret-manager@v0.2.0

[shrewd dust]

you're doing a dagger call I asume on a newly checked code, correct?

[novel locust]

yes

[shrewd dust]

yeah.. it's what I told you: https://play.dagger.cloud/playground/-pYHga-ubKx

seemd like dagger install is following a different path and checking out the code differently than call

and as I've shared above, seems like you pushed the branch but never actually pushed the branch that contains that reference

even GitHub complains warns about it

[novel locust]

that's not my repo

[shrewd dust]

oh! I thought it was yours

[novel locust]

no.

[shrewd dust]

in any case, seems like an issue that we should fix algo

since dagger install works

silently pinging @nocturne pawn

https://github.com/dagger/dagger/issues/8100

[nocturne pawn]

Hi, ok I will take a look maybe my push failed

[nocturne pawn]

I push a new tag v0.2.1

this one is on master the other one was on a feature branch deleted