#Is there any way to disable caching?
maiden bolt
taking a look at your issue @crimson river if you have a dagger cloud link, please drop it here so Dagger staff can compare 🙏
crimson river
Sure, just triggered this run: https://v3.dagger.cloud/Leyman/traces/9d832d9670aea0e0e076e0a25946485d
lime geode
@crimson river I could be wrong, but at first glance this looks like a possible infinite loop? Your code seems to run the same dagger functions again and again
You may have a runaway recursion problem
crimson river
That was my original thought, since both UIs showed a lot of duplicate function calls
I was actually able to recreate that in a smaller repo https://github.com/dagger/dagger/issues/9494
A hackier version of debugging is to attach some random string to every call. And the logs show the same string multiple times, so it just double-reports
The same functions do get called multiple times, but with updated contexts (it iterates over each project)
I'm pretty sure I've ruled out the infinite loop. I've even done attempts at shortcutting every meaningful dagger call
if 0 < 1 {
return dag.Directory()
}
and it does successfully succeed (although obviously skipping the valuable parts of dagger)
lime geode
@crimson river ah I think you may have hit an issue that was just fixed in main... https://github.com/dagger/dagger/pull/9483
If you want to try testing with a dev build of the engine:
dagger shell <<EOF
github.com/dagger/dagger@main | engine | service dev | up
EOF
Then in another terminal
_EXPERIMENTAL_DAGGER_RUNNER_HOST=tcp://localhost:4242 <YOUR DAGGER COMMAND HERE>
Awesome will check on that later today and report back!