FWIW I'm hitting the cache issues with

[blissful smelt]

It's not specific to cu terminal. I wonder if there's some dagger GC running in the background.

[rigid swift]

at least historically there's no gc, it's more likely 2 engines

im gonna poke at this today

could also be cache misses bc we've moved more and more things to session-level caching

[rigid swift]

got way too sidetracked on mcp roots today, didn't get to this. tomorrow!

[rigid swift]

confirm this is caused by 2 engines. in my particular case it's 18.11 and 18.12, and cu terminal upgrades the engine if your dagger cli is a higher version than the one in the container-use go.mod

for now i can upgrade dagger.io/dagger in the go.mod, but we're gonna need a longer term fix. i feel like there were some other threads in discord related to that longer term fix, but i don't know how to find them

[echo pilot]

short-term, maybe injecting the LEAVE_OLD_ENGINE env var ? (or whatever it is)

[rigid swift]

lol that's a thing?

if that's a thing it sounds perfect

[echo pilot]

DAGGER_LEAVE_OLD_ENGINE sorry ahah

[blissful smelt]

#container-use message

Solomon mentioned something about the fact that dagger needs to be more stable

[rigid swift]

wait so this is fixed? why's it in draft?

[echo pilot]

oh maybe there's another edge case of cache miss ?

[rigid swift]

@timid tartan 's comment reads to me as making the perfect the enemy of the good, but i'm probably missing something?

[echo pilot]

actually you're right 👍

That's a funny edge case of sdk / cli conflict