This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # asami (6)
- # babashka (74)
- # babashka-sci-dev (164)
- # beginners (50)
- # biff (3)
- # calva (71)
- # clj-kondo (4)
- # cljdoc (39)
- # cljsrn (4)
- # clojars (8)
- # clojure (70)
- # clojure-austin (7)
- # clojure-czech (5)
- # clojure-europe (4)
- # clojure-losangeles (1)
- # clojure-nl (10)
- # clojure-norway (1)
- # clojure-uk (3)
- # clojurescript (38)
- # community-development (18)
- # cursive (129)
- # datomic (9)
- # fulcro (7)
- # graalvm (4)
- # improve-getting-started (1)
- # jobs (1)
- # kaocha (2)
- # liberator (9)
- # lsp (22)
- # malli (3)
- # membrane (95)
- # off-topic (86)
- # releases (2)
- # sci (5)
- # specter (2)
Might be a change that @rahul080327 did in his PR last night?
interesting, having a look if i caused it, what exactly is the change youre seeing @UFUKJ3QG7? the arch is different?
ah yes theres no amd64, checking now
@rahul080327 You aren't overwriting the
latest ones with versions from master, right....?
@UFUKJ3QG7 Can you specify which exact version you were using
yeah the latest will be overwritten even push to master. theres a bug which doesnt make the amd64 archs, its only arm
ah, but wasnt that how the shell script was working? sorry fixing right now
yes, that's how the shell script has always worked and last time there was a refactoring to this with the buildx stuff this mistake was also made and corrected later
should i do a revert of my commit, that should get it back to it, til i fix the bug?
I'll try a rebuild of from circle now
rerunning the last 0.8.0 one now
yeah its quite a complex thing and feared i missed something 😕
In the next commit we should have BOLD CAPITALS in that logic which only pushes to latest on non-SNAPSHOT
i found the issue too, wasnt checking if version contains snapshot, but is snapshot 😞
@UFUKJ3QG7 Should be fixed now - can you test?
moving to #babashka-sci-dev for the PR
😅 ! Thanks for moving so fast @rahul080327
well more eyes on the review next time!
@UFUKJ3QG7 could you try out
babashka/babashka:0.8.1-SNAPSHOT too once if possible? wanna make fully sure the archs are correct 😄
What I'm seeing on amd64:
$ docker run --rm babashka/babashka:0.8.1-SNAPSHOT bb -e '(+ 1 2 3)' Unable to find image 'babashka/babashka:0.8.1-SNAPSHOT' locally 0.8.1-SNAPSHOT: Pulling from babashka/babashka e0b25ef51634: Pull complete bf3385f5392f: Pull complete 4a72072863da: Pull complete 7f9ab196048c: Pull complete 4f4fb700ef54: Pull complete Digest: sha256:de4a585a4f7cde6a41a3a623e2205622730cb7a7e31bba9672f982c0d0eed4fa Status: Downloaded newer image for babashka/babashka:0.8.1-SNAPSHOT 6
NoVALUG talk by @rahul080327: Babashka and Clojure https://www.youtube.com/watch?v=ZvOs5Ele6VE
all better now 😄
@borkdude is it reasonable to add something like
cwdto babashka.fs that returns the Current Working Directory? At the moment I'm doing this
(:out (sh "pwd")).
you could also do
What @rahul080327 said is the recommended way, but yes, we could just make a function that does that
Any opinions for a name for a function in
babashka.fs that returns the value
(System/getProperty "user.dir") aka
PWD in bash shells?
My Python brain wants
get-cwd from https://docs.python.org/3/library/os.html#os.getcwd
i’m partial to
current-working-directory for its explicitness, but I don’t think too many folks would be confused by
can't go wrong with
pwd either 🙂 (print working directory - not quite printing, but getting the string representation of it, close enough) - of the options given, I like cwd - the more bash'isms the better, not familiar with the lib, but
ls for listing the dir (getting the files as an array of maps or strings) would also be great
oh I thought pwd stood for "path to working directory"
Oh maybe you are right @U5NCUG8NR, I always thought p meant print. But that doesn’t really make sense for the PWD env var.
man pwd implies print (https://linux.die.net/man/1/pwd)
Has anyone ever stumbled upon rrb-vector being necessary for a dependency you tried to run in bb?
And that depends on puget which depends on fipp which depends on rrb-vector. It all leads to fipp
It seems bb install have been broken when trying to install it from Scoop ( windows ). when i try to launch it, it always asks me about where is located the exe file.
yes, this was the unfortunate effect of doing another 0.8.0 release to fix docker images which were accidentally overwritten due to a bug in a PR.
@ales.najmann could you maybe update the scoop package so it will pick up the newest SHA for the (new) 0.8.0 release?
Babashka 0.8.1 (2022-04-15)
prepare subcommand to download deps & pods and cache pod metadata
• https://github.com/babashka/babashka/issues/1041: Improve error message when regex literal in EDN config
• https://github.com/babashka/babashka/issues/1223: Ensure that var metadata (specifically
:name) aligns with the var's symbol (which in turn ensures that
doc will print the var's name)
• https://github.com/babashka/babashka/issues/556 Add server-status to org.httpkit.server
• https://github.com/babashka/babashka/issues/1231: missing methods in
reify should fall back to default interface methods
• Fix destructuring in defrecord protocol impls