Hey, I am currently running a central

[quiet bay]

Errors like this

[languid fern]

@quiet bay wow that is one beefy machine! I don't know of anyone with this exact setup, but I've certainly seen teams pursue the "one giant persistent machine" route.

And, using a remote dagger engine over tailscale definitely works. I've relied on that on my daily work setup for over a year (now switched to using Dagger Cloud's hosted engines)

[quiet bay]

Thanks, great to confirm my general understanding isn’t wrong. I have since noticed that switching from bun back to node eliminated many of the silently caught issues in my code: Seems like it just hides the actual error behind weird bun specific errors.

But in general I ran into many small unhandled cases of the typescript sdk. We are currently thinking about migrating all of our companies CI pipelines to dagger in the hope to reduce flakiness, but even though the general dagger concepts are great, the typescript sdk sometimes felt a bit unstable, eg method names with numbers lead to weird issues because it seems like they are converted to graphql using regex.

Is it generally recommended to use the go sdk for maximum stability? Or is the typescript sdk generally stable as well.

I don’t want to spam you with bug reports if the typescript sdk is not considered stable yet

[languid fern]

The typescript SDK is definitely considered stable. Please spam away 🙂 And sorry about the issues

I think bun support is relatively recent compared to node support. That might be part of it?

cc @lofty cobalt @slender python

[lofty cobalt]

Hey 😄

The Typescript SDK with Node is considered stable, we also have support for Bun and Deno, but these can't be considered as stable as Node since we have fewer users and less feedback on them.
Because TypeScript is much more flexible than Go, it's more common to find unhandled cases so please feel free to open issues whenever you find one and I'll be happy to resolve them so Bun can be more stable 😄

[quiet bay]

Here my rough diagnosis from my issue when I had a function named translateI18n. I don't remember exactly what I had as an arg there, but I remember I had some JSON.stringify(...) .replace does not exist on undefined error.

Renaming the method fixed it

[lofty cobalt]

Okay, could you open an issue so we can keep track of it 😄