#the case of the disappearing blob
vague karma
this left my engine pretty much hosed (at least for those modules), did a docker rename to quarantine it and make a new engine, that one's working
@clear trail lemme know if there's anything you want me to look for
(this was breaking ./hack/dev so the engine in question is the v0.19.6 outer one)
the case of the disappearing blob
clear trail
mysterious, if you grep for 7ed8bf4612e08c914cf4649cb94180b12fe87078898c14fdf6f252268a5d14bd in the engine logs, what shows up? particularly wondering about remove content since if it was removed and never added again, that would begin to explain this
vague karma
ah crap, apparently the engine got removed when the new one was created, thought renaming it would protect it 😭
i did grep for that before, didn't see anything obvious, not that that's worth much (kinda expected to be able to check again...)
https://dagger.cloud/dagger/traces/cf531f355b8d92d205771cc5d8553d48
this is the last trace from when i was troubleshooting, got it down to just the 3 modules
i'll revive the thread if it comes up again
clear trail
i'll revive the thread if it comes up again
sg ty, I imagine there's probably some permutation of cache hits + misses in the right places that somehow result in us skipping the step where the schema json file (the missing blob in question) is loaded but not skipping the step where sdk modules try to use it. But nothing immediately obvious yet
vague karma
@clear trail it's baaaaack:
- from a
./hack/dev: https://dagger.cloud/dagger/traces/cd1a9c9b84f12b9689365642dae004be - from an LLM session, which is where I first saw it happen for an LLM's tool calls: https://dagger.cloud/dagger/traces/ad13e8122445ef4a5e8e27db13f6b2b5?span=2525be65ada9ea44
docker logs dagger-engine-v0.19.7 2>&1 | grep 0989ca382178d27956640483de17279dc67deb2496b1244b8573f7a9c813fc3a > matches.log
hopefully that's enough, nuking the container to get unblocked