Fork me on GitHub
#babashka
<
2022-12-06
>
Daniel Jomphe16:12:19

I'm very happy to see that Hyperfiddle RCF is, or will soon be, compatible with Babashka!!!

borkdude16:12:44

Yeah :) You can try this with the dev version right now if you want

borkdude16:12:52

both bb dev + rcf master

borkdude16:12:09

https://github.com/babashka/babashka-dev-builds

bash <(curl ) --version 1.0.168-SNAPSHOT --dir /tmp

Daniel Jomphe16:12:14

Will do, most certainly today!!! Oh, bb dev... ok, will probably go ahead to try it, I added (again) some RCF tests to a namespace this morning that (again) broke our BB tasks b/c they visited that namespace. Instead of doing lots of gymnastics, better to use dev.

borkdude16:12:14

I can probably do another bb release this week

borkdude16:12:18

end of the week probably

borkdude16:12:23

but testing would be much appreciated

Daniel Jomphe16:12:46

Should I see this after installing 168-snapshot, did my install correctly target the snapshot?

borkdude17:12:11

no, with --dir /tmp it downloaded it to the /tmp dir :)

borkdude17:12:22

so you'd have to execute it from /tmp/bb

borkdude17:12:26

or remove the --dir option

Daniel Jomphe17:12:44

Yeah, I instead did this: > # https://github.com/borkdude/babashka#installer-script > RUN curl -sLO https://raw.githubusercontent.com/borkdude/babashka/master/install 2>&1 > RUN chmod +x install --version ${VERSION_BABASHKA} --download-dir . > RUN ./install 2>&1

Daniel Jomphe17:12:54

in our dev container dockerfile, where the version is 1.0.168-SNAPSHOT

Daniel Jomphe17:12:43

Back to this, checking why this happens

./install: line 46: $2: unbound variable

Daniel Jomphe17:12:41

Final version is now OK:

# 
ARG VERSION_BABASHKA
RUN curl -sLO  2>&1
RUN chmod +x install
RUN ./install --download-dir . --version ${VERSION_BABASHKA}
com.hyperfiddle/rcf {#_#_:mvn/version "20220926-202227"
                     :git/url ""
                     :sha "86339e422e38f39951686b1aee6ececc17c4c1d4"}

Daniel Jomphe18:12:28

Using the latest BB and RCF, I can confirm that they now work together. Cheers, @borkdude! And thanks again!

🎉 4
borkdude15:12:20

New bb released

nice 1
1
Daniel Jomphe18:12:28

Using the latest BB and RCF, I can confirm that they now work together. Cheers, @borkdude! And thanks again!

🎉 4
rafd19:12:04

Should --classpath "src" be identical to :paths ["src"] in bb.edn ? I'm getting different behaviour.

Bob B20:12:50

I don't think that's generally true - if there are deps in bb.edn, using --classpath "loses" them:

$ cat bb.edn
{:paths ["src"] :deps {djblue/portal {:mvn/version "0.29.1"}}}
$ bb '(babashka.classpath/get-classpath)'
"src:... several lines of classpath"
$ bb -cp "src" '(babashka.classpath/get-classpath)'
"src"

rafd20:12:07

Yeah, that's what I was seeing! I was confused, because the doc for -cp implies that only :paths in bb.edn is replaced (not the deps), but, on second reading, I see how Classpath to use. Overrides bb.edn classpath. can mean "entire classpath as generated from bb.edn , include deps, is overriden"

Bob B20:12:44

[insert meme of 'aliens!' guy with text 'classpaths!']

😂 1
dangercoder20:12:50

When excecuting commands via babshka.process process - is it possible to "swallow" output so it's not displayed in stdout?

dangercoder20:12:15

Solved it, the :error output was defaulting to stdout (i think).

👍 1
borkdude21:12:45

for swallowing output I'd use :err :string so the stderr is written to a string that you then don't consume