#Dagger Cloud
remote yarrow
it seems like the engine you hit (I'm guessing a cloud one) didn't have anything cached and needed to do a full sync, so that file in particular (goreleaser.nightly.yml, was highlighted in your link) would just have to be included as part of that afaict
stray vapor
it seems like the engine you hit (I'm guessing a cloud one) didn't have anything...
Yes but I see files being uploaded that I carefully ignored in my module's contextual argument.
So I don't know if 1) my ignore filter is not wrong, 2) it's not being applied, 3) that filesync is for an entirely different argument, and if so which
remote yarrow
I see, yeah the parent span shows that there's no exclude filters: https://dagger.cloud/dagger/traces/5978b321aca25bec9cc69b0dbf43beac?listen=fef5fdc00ca876f2#93fab4647d90534d
it's a good question why those spans for the context dir just show up on the top level not seemingly attached to anything, which makes it hard to track down where it's coming from obviously
Actually it might be because the context dir gets loaded during the cache key step for the about to be called function (in this case DaggerDev.engineDev)
We should fix that so the cache key step is inside the span
But either way in the meantime if that's correct it means that DaggerDev.engineDev has no exclude filter on one of its args
stray vapor
But either way in the meantime if that's correct it means that `DaggerDev.engine...
one of its args, or one of its dependencies args?
remote yarrow
one of its args, *or* one of its dependencies args?
its source arg: https://dagger.cloud/dagger/traces/5978b321aca25bec9cc69b0dbf43beac?span=e808d966c16980aa
if you click the Directory for the arg you can expand and see it doesn't have any excludes
remote yarrow
😭 can you spot it?
wow yeah we should really error out in that case... or at min print some warning to telemetry if we really want users to be able to write arbitrary comments that look an awful lot like a syntax error in a pragma