i'd like to see the bytes being exchanged between bb and a pod. is there some kind of debug functionality along these lines?

@sogaiu it all works over stdin and stdout. So you can just send some bencode to the pods stdin and watch the output

i want to see what other pods are doing

the docs are not enough for me to figure things out

Alternatively you can use the babashka.pods library and put some printlines in there

And run it on the JVM

i am not using clojure to do this

You are not loading the pod from Clojure?

i am loading the pod from babashka -- the pod is not written in clojure

Then what I’ve said before still stands

Just look at the tests of the filewatcher for example

Those run on the JVM while the fw is written in Rust

i will go back and look again

thanks for the hints

because stdin and stdout are already being used, print didn't seem like it was going to work. what i ended up doing was this:

(defn write [^.OutputStream stream v]
  (spit "/tmp/pod.log"
        (str "wrote: " v "\n")
        :append true)
  (locking stream
    (bencode/write-bencode stream v)
    (.flush stream)))

(defn read [stream]
  (let [res (bencode/read-bencode stream)]
    (spit "/tmp/pod.log"
          (str "read: " res "\n")
          :append true)
    res))

@sogaiu that works, but like I said, if you use the babashka.pods library you can just do this on the JVM without rebuilding

https://github.com/babashka/babashka.pods

i think from where you sit it probably seems easy because you understand all of the bits already 🙂 for someone who is in the midst of trying to figure out other pieces (and someone like me with limited stack space and capability 🙂 ), it was too many uncertain pieces.

in any case, thanks for the tips

@sogaiu Changing these lines in the JVM library is easier, since you don't need to rebuild the entire babashka. it's more flexible

lol

it is easier to you because you already understand

so changing a line in bb, compiling it with GraalVM, needing another change, compiling it again with GraalVM is more difficult then doing exactly the same thing in running a JVM program? that really doesn't make sense to me 😉

look: this test is just ran on the JVM: https://github.com/babashka/pod-babashka-filewatcher/blob/master/test/pod/babashka/filewatcher_test.clj it does exactly the same thing as within bb.

but suit yourself 🙂

there is no disagreement about IF you understand the alternatives which one would be easier. i believe what you say. the problem is when one's stack space is full holding a lot of other details, trying to understand additional alternatives can be too much. basically, the issue is a cognitive problem on my side 🙂

that makes sense

@sogaiu This also works:

$ BABASHKA_POD=true clj-kondo <<< $(bb -e '(bencode/write-bencode System/out {"op" "describe"})')
d6:format3:edn2:id7:unknown10:namespacesld4:name22:pod.borkdude.clj-kondo4:varsld4:name13:merge-configsed4:name6:print!ed4:name4:run!eeeee

You can then pipe the output back into something like:

$ BABASHKA_POD=true clj-kondo <<< $(bb -e '(bencode/write-bencode System/out {"op" "describe"})') | bb -e '(bencode/read-bencode (.PushbackInputStream. System/in))'
{"format" #object["[B" 0x545ac490 "[B@105866550"], "id" #object["[B" 0x30ffb9b0 "[B@105866a48"], "namespaces" [{"name" #object["[B" 0x77363113 "[B@105867690"], "vars" [{"name" #object["[B" 0xec59d35 "[B@1058682e0"]} {"name" #object["[B" 0x4478964a "[B@105868e58"]} {"name" #object["[B" 0x34bb1efa "[B@105869ad8"]}]}]}

This way you can develop a small bb script which interacts with your pod

thanks -- i will have to digest these things later when my stack is not so full 🙂

it is similar to the nREPL protocol

@sogaiu One other hint: you can print to sterr in the pod for debugging as well

yeah, i've been doing that since the first run, thanks 🙂

at least from the pod side

there is also a python pod example

don't know which language you're writing the pod in

C?

yes, i've been looking at the python example too.

i'm writing it in janet

shell macro: https://gist.github.com/borkdude/63a86a04f5d97aae4825326c0309dad2#file-macro-clj-L19

very cool