#First I’ve heard of it, do you have a

1 messages · Page 1 of 1 (latest)

dense marten
#

./hack/dev or whatever to get a new CLI

in a directory using the new CLI
dagger init --name foo --sdk go --source .

#

then

dagger call search --message "french fries"
#

vs

#
dagger --progress=plain call search --message "french fries"
#

could well be my code and how strings are being passed around... 🤷‍♂️

I'm looking at ensuring quotes are around things when I exec grep eventually, but ran into this while debugging.

dense marten
#

I fixed my error...
I needed some quotes around something in the bash script I was executing. Pushing a commit now with the delta.

valid oak
#

Ah got it - just to get some feedback on it, would —debug have helped?

dense marten
#

doesn't seem to

#

maybe because what happens is that the way I wrote it initially, the file that gets greped doesn't have the contents I expect (blank in fact) so the exit code of 1 is from the grep itself.

valid oak
#

Oh try passing it after the dagger command instead of at the end

#

That’s another thing worth fixing

dense marten
valid oak
#

Not sure why but it seems to just be ignored, you’d also expect an unknown flag error if it was being passed to the module so not sure where it’s being dropped

dense marten
#

yep debug helps