Justin Chadwell

This should be fixed by https://github.com/dagger/dagger/pull/8318#, which will default to keeping the git directory around in all cases.

Maybe a separate issue, but `Service.Up` also has some issues (when calling from code, not from the CLI) compared to the previous `dag.Host` tunneling API we used to use. Specifically...

@vito I don't think you can start a tunnel to the host without `up` though? So if I wanted to start a service, and then make a request to it...

Agreed, I previously considered whether we could *instead* have `WithErr` (naming tbd), which takes a `func (*dagger.Container) (*dagger.Container, error)`. I'd rather we don't *explicitly* embed errors into containers, but I'm...

We should auto-generate a schema from this struct definition here: https://github.com/dagger/dagger/blob/5ec03a604d50b721aaa65ba7c4db8c875696ac72/core/modules/config.go#L14-L43 Then we should have this as a pipeline in `.dagger/docs.go`, similar to how we generate the cli reference docs...

Oh thanks @wingyplus :tada: Yeah, that looks awesome, honestly, would be happy to pull this into our CI if you wanted to integrate it. > But it might need some...

You can see the generated JSON schema at https://github.com/dagger/dagger/blob/main/docs/current_docs/reference/dagger.schema.json.

> Having said that, maybe we can write an automation script to list all modules from our daggerverse list, and try calling their functions with new engine. Maybe we can...

> (if we do that, we may have to do the runtime change in next PR because right now go mod tidy fails to find that new dependency in dagger...

The SDK runtimes are the modules that are run by the engine to manage modules in a language - the typescript SDK manages modules written in typescript, generating code for...