After upgrading to 0.12.2 (from 0.12.0):

[random root]

Hey @thick axle or @harsh ridge do either of you have any ideas on this one? I want to see if this is a broader issue

[harsh ridge]

possibly fixed by this? https://github.com/dagger/dagger/pull/8011 - cc @thin forge

[thin forge]

Yeah it's the same error message. @next lava to confirm, are you setting Secret either directly in any struct fields in a module or setting Secret on a Container that ends up in a struct field? If you have a link to the code hitting this I can also just look quickly myself

[next lava]

Lemme check

But chances are, both

[thin forge]

Oh I also just saw the links you sent outside this subthread, I'll take a quick look

[next lava]

I'm not entirely sure where the problem is coming from.

Could be coming from here: https://github.com/sagikazarmark/daggerverse/blob/main/registry-config/main.go#L132

Or somewhere around here: https://github.com/sagikazarmark/daggerverse/blob/main/helm/chart.go#L72

I'm saving secrets in module structs and then mount all of them here: container.from.withUser.withoutEnvVariable.withoutEnvVariable.withMountedSecret

The tricky part though that the secret for that particular function is created by another module call...that stores some intermediate secrets in its struct.

[thin forge]

Okay yeah that looks like it's what was fixed in https://github.com/dagger/dagger/pull/8011. That's merged so it will be in the next patch release, which we're currently planning on doing July 30th: https://discord.com/channels/707636530424053791/1265193826918727783

You're the second user to report this since last night when I fixed it though so I'll see if it makes sense to do the release even earlier, like this Thursday or something. It's unfortunately not easily worked around

[next lava]

No problem, 0.12 works just fine.

[vocal creek]

Hitting this as well this morning. Can see downgrading avoids it for now, I'll try 0.12 🙂

[thin forge]

Ah okay, thanks for letting me know, I think I'll just run the release tomorrow to get this pain out of the way so everyone doesn't need to be stuck on v0.12.0. Seems to be widespread enough in impact. Will wait for confirmation from the rest of our team but can track the release here: https://discord.com/channels/707636530424053791/1265193826918727783

[thin forge]

We just released v0.12.3, once you have a chance let me know if the error is gone now. We have a bunch of test cases here, so think the various cases should be covered now

[next lava]

FTR: it's still happening on 0.12.4