This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # aws (3)
- # babashka (48)
- # babashka-sci-dev (1)
- # beginners (143)
- # calva (62)
- # clj-kondo (6)
- # clj-otel (3)
- # cljs-dev (59)
- # cljsrn (4)
- # clojure (39)
- # clojure-austin (5)
- # clojure-europe (60)
- # clojure-losangeles (1)
- # clojure-nl (2)
- # clojure-romania (4)
- # clojure-spec (3)
- # clojure-uk (2)
- # clojurescript (32)
- # datomic (17)
- # events (3)
- # figwheel-main (4)
- # graphql (3)
- # gratitude (2)
- # holy-lambda (52)
- # introduce-yourself (3)
- # jobs (1)
- # juxt (5)
- # kaocha (2)
- # lsp (33)
- # nyc (3)
- # off-topic (9)
- # other-languages (4)
- # overtone (1)
- # portal (21)
- # reitit (2)
- # remote-jobs (5)
- # shadow-cljs (65)
- # tools-deps (2)
- # xtdb (8)
Hi, I noticed that most (or all) pods don't have releases for linux/aarch64, even tho babashka itself does. (I keep running into this issue when I copy my scripts to a raspberry) I was wondering what's the main reason/limitation behind this?
@adamkrisz The main reason/limitation is people not having asked for those so we didn't put in the effort yet
I see, thanks! (also good to hear 😄)
We rely on #circleci for aarch64 support - as long as they offer this, we can add support to pods
@adamkrisz Thanks for the issue. Meanwhile you could also try out #nbb if you don't mind using Node.js - it is a babashka variation for Node.js and can run any Node.js library including playwright, which is an excellent browser testing framework. Here is an example of that: https://github.com/babashka/nbb/tree/main/examples/playwright
If you want you can also try to work on the aarch64 support yourself using a PR, to speed things up
oh yeah, I actually did exactly that as a workaround! Thanks for you excellent work btw 😄
I also had problems with the postgressql pod a while back, but I see it has aarch64 releases now
I'll try to open a PR then, I was just looking into how it got solved for the other pods
@adamkrisz I just pushed the aarch64 and updated the manifest, so you should now be able to use the pod in babashka using version 0.1.0.
You might have to clear your
~/.babashka/pods directory first.
I decided to not release a new version but update the existing one just with the aarch64 binary
coo., thank you!
@borkdude, what do you think of adding https://github.com/igrishaev/etaoin/blob/9f07e3098a8e152a7998438718c631e85fe0ba05/src/etaoin/api.clj#L79 to the https://github.com/babashka/pod-babashka-etaoin api? 🧵
That should theoretically be possible I guess? Since it's just an http client basically?
Yeah… had a little look. It uses clj-http. I guess we’d need to switch that to clj-http-lite?
I already did that here: https://github.com/borkdude/etaoin-graal
there is also this thing: https://github.com/tatut/clj-chrome-devtools but that is slightly different
I’ll go raise an issue over at etaoin to see if there is interest in becoming babashkable directly.
ok, and if he isn't interested, then we could maintain a fork like https://github.com/grzm/awyeah-api is doing for aws-api
probably does not matter cause it doesn’t seem to be used, but https://github.com/borkdude/etaoin-graal/blob/38e12414ae49b9f1f532a01862109922054b4c95/project.clj#L39-L40.
A very short term thing is adding the execute method to the etaoin pod. I'm probably releasing a new version soon since there was just another PR.
Thanks borkdude! Since we have interest 🎉, I think I’ll focus on making etaoin bb friendly instead.