Vasek - Tom C

> Those two sentences seem to contradict each other? https://github.com/dagger/dagger/issues/8030 is self-calls, so what is "supported and tested"? Or am I missing something? The bindings are generated so you can...

> 👋 want to drop some output issue (not a blocker, just a confusion issue). I try implementing the Elixir generator ([wingyplus/elixir-generator](https://github.com/wingyplus/elixir-generator)), the generator exports `dagger_sdk` directory to the host...

> 👋 want to drop some output issue (not a blocker, just a confusion issue). I try implementing the Elixir generator ([wingyplus/elixir-generator](https://github.com/wingyplus/elixir-generator)), the generator exports dagger_sdk directory to the host...

I squash all my commit to simplify the rebase on #9505, now I'm going to start the rebase, wish me luck 🚀 **EDIT 2**: Fixed by #9645 **EDIT** I found...

Failure on test everything else isn't related to this PR: https://v3.dagger.cloud/dagger/traces/e3aec1efb6618d36d5a2fe2b6807c641?listen=bdc294a9d8aa54cc&span=5cb3827b70f01851 Same for scan engine that is a flake like we all know :)

> The failure in there appears to be: Good catch, I pushed a fix

> The above results in dagger.gen.go starting with package dagger, which doesn't work because I already put a main.go with package main in there. > I think we should ideally...

> There are some failing integ tests but it looks like they were already failing before that commit, TestClientGenerator/TestOutputDir/nested_directory_(generated/nested/test)/go Thanks! This test shouldn't have failed but sometime cloud doesn't directly...

Current failing tests are non related to that PR, I'll add the changes around dagger.json in a follow up PR so we can iterate faster

> # test.com/test/generated > generated/dagger.gen.go:21:2: querybuilder redeclared in this block > generated/dagger.gen.go:19:2: other declaration of querybuilder > generated/dagger.gen.go:21:2: "dagger.io/dagger/querybuilder" imported and not used Oh this is a related to my...