#Monorepos - formerly-Can't run simple go sdk example - exit status 1

1 messages · Page 1 of 1 (latest)

rustic viper
#

Followed steps 1-3 in the getting started guide, running main exits with status 1 and no description

go 1.19, debian

left path
#

I'll try to repro

# 
multibuild ➤ go run main.go
Building with Dagger
multibuild ➤ echo $?
0
#

I get the expected result with exit code of 0

#

Do you have Docker daemon running?

rustic viper
#

it is yeah

#

weird

#

i wonder how i could troubleshoot

left path
#

happy to jump in #dev-audio and share screen for a sec 🙂

rustic viper
#

sweet

left path
left path
left path
#

Context is that Leigh is investigating potential tooling for better CI for monorepo.

toxic wedge
#

Hi, @rustic viper, pleased to meet you

#

curious what you're looking to do for your monorepo! The demo that I did for the call is a tiny part of what I eventually want to do

left path
#

Monorepos - formerly-Can't run simple go sdk example - exit status 1

#

@devout pilot 👋

devout pilot
#

@left path thanks a lot man

devout pilot
#

i think it seems we can replace bazel with dagger and can have another advantages also like CICD as code and all

#

where is documentation of dependency management in dagger?

#

And when dagger api will be released so we can think on building rust SDK?

#

@left path ay update on this bro?

left path
#

as for dependency management, we don't have a doc like this: https://bazel.build/basics/dependencies and don't have explicit dependencies, but in essence, if a step in your pipeline requires another step's output, then there's a dependency, otherwise things will run in parallel.

devout pilot
#

when doc will be updated?

left path
#

Could you open an issue and tell us what you need in a dependency management doc? 🙏

devout pilot
#

is there any API docs available?

#

ok i will create the issue by today evening

left path
devout pilot
#

ok thanks

rustic viper
rustic viper
#

Will give your talk a watch

#

Thanks !

devout pilot
gaunt juniper