Justin Chadwell

Updated to: - Hold back the OTEL upgrades - Upgrade buildkit manually - Get `sdk/go` in sync as well - Fix deprecated checks

Hm, even the `// +private` removal doesn't solve everything. Turns out, we can very easily hit this case: https://github.com/dagger/dagger/pull/7804#issuecomment-2216493990 (and I've pushed a test for it in https://github.com/dagger/dagger/pull/8358/commits/1b8c1758faea4171b0d44c02b8313d6d1dfcb88b). We incorrectly...

> Another option (this one might work 🎉), could be to have a `Call` additionally return the client ID that it actually used. This is neat, because now when we...

No objections, I think this could definitely be an improvement for running dagger functions in k8s/etc :tada: Previously, in the standalone SDK model, I don't think this was as important,...

@shykes could you elaborate a bit on point 2? I think the engine image probably won't have the CLI embedded, it'll just have the engine as we build it today...

Nice, thanks both! :tada: I don't *think* we have a guide, but I can point you to a couple places (sorry, just throwing something together around kubecon): - Support originally...

@Scalahansolo happy to follow-up with the gitlab issue on discord if you want! I'd guess though that maybe `.local/bin` isn't in the `PATH` - could you share the output of...

One issue I can forsee if we allow *both* errors and values returned - this pattern won't fit neatly into every language. For go, where `v, err := doThing()` is...

Ok, so wanting to circle back to this, I actually have a concrete use case in https://github.com/dagger/dagger/pull/9356 I'd like to solve. Essentially, making a release now returns a "release report"...

> Getting back to your original use case ("I want to attach to an errored container with terminal") we might need some sort of syntax for "capture an error and...