This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-12-06
Channels
- # adventofcode (71)
- # aleph (1)
- # announcements (6)
- # aws (1)
- # babashka (27)
- # beginners (60)
- # biff (7)
- # calva (3)
- # clj-kondo (3)
- # clj-yaml (1)
- # clojure (60)
- # clojure-europe (43)
- # clojure-nl (3)
- # clojure-norway (75)
- # clojurescript (16)
- # code-reviews (7)
- # css (4)
- # cursive (47)
- # datascript (4)
- # events (5)
- # fulcro (37)
- # gratitude (5)
- # hyperfiddle (4)
- # introduce-yourself (4)
- # joyride (23)
- # juxt (4)
- # malli (4)
- # membrane (64)
- # nbb (8)
- # off-topic (12)
- # other-languages (6)
- # pathom (6)
- # polylith (9)
- # random (3)
- # rdf (66)
- # reitit (3)
- # releases (2)
- # shadow-cljs (18)
- # tree-sitter (10)
I'm very happy to see that Hyperfiddle RCF is, or will soon be, compatible with Babashka!!!
For anyone wondering https://github.com/hyperfiddle/rcf.
https://github.com/babashka/babashka-dev-builds
bash <(curl ) --version 1.0.168-SNAPSHOT --dir /tmp
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.
Should I see this after installing 168-snapshot, did my install correctly target the snapshot?
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
in our dev container dockerfile, where the version is 1.0.168-SNAPSHOT
Back to this, checking why this happens
./install: line 46: $2: unbound variable
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"}
Using the latest BB and RCF, I can confirm that they now work together. Cheers, @borkdude! And thanks again!
Using the latest BB and RCF, I can confirm that they now work together. Cheers, @borkdude! And thanks again!
Should --classpath "src"
be identical to :paths ["src"]
in bb.edn
? I'm getting different behaviour.
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"
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"
When excecuting commands via babshka.process process
- is it possible to "swallow" output so it's not displayed in stdout?