Vasek - Tom C
Vasek - Tom C
I can reproduce the error locally with `dagger call test test --test-regex="TestDaggerRun"` ``` multi.go:85: ✘ Container.from(address: "alpine:3.18.2"): Container! 1m0.0s multi.go:85: ! failed to resolve source metadata for docker.io/library/alpine:3.18.2: failed to...
@helderco I added all your comment, I think this PR is ready for a last review before a merge 🚀 As a follow up, I'll add a piece of documentation
@helderco I think I completed the changes that you asked, feel free to review anytime :D
@helderco I added the changes based on your comments! I would like to merge this PR tomorrow if you think it's okay, I manually tested it and everything works!
> @TomChv just want confirm this was a known breaking change Yes it is 👍
I'm going to handle this issue by throwing an error if nothing has been registered after a scan.
> Dagger has a [NodeJS SDK](https://docs.dagger.io/sdk/nodejs). What if it also had a [DenoJS](https://deno.land/) SDK? I love Deno and I think it fit well to Dagger to have a Deno SDK....
After quick research, our TS GQL client is also available in Deno : https://deno.land/x/[email protected] So basically the only part to change in Deno is our static files. The generation shall...
> I've tried the latest dagger release 0.12.3 with deno, but unfortunately, I get the error message Cannot assign to read-only property 'name' of function. Is the deno runtime still...
I removed the TS label since it's not related to TypeScript