@borkdude would it be possible to do a new babashka release? It seems the nREPL port fix isn't in 0.2.3 yet.
Thanks!
Preliminary changelogs: https://github.com/borkdude/babashka/blob/master/CHANGELOG.md#v024-snapshot-unreleased Feel free to try out the binary from master. I will release tomorrow if nothing else comes up. About the printed message for nREPL: I noticed they are slightly different for nREPL and the socket REPL. We might want to make those similar.
Released 0.2.4
π :bmo:
Thank you π:skin-tone-2:
Iβm working towards a new release but for now you can download a master version from #babashka_circleci_builds
Is there any router library with httpkit that is known to work out of the box with babashka?
I don't know of any. Right now your best bet is building something simple by just looking at the :uri
and :method
keys of the request
Thanks :)
Preliminary changelogs for 0.2.4:Β https://github.com/borkdude/babashka/blob/master/CHANGELOG.md#v024-snapshot-unreleased Feel free to try out the binary from master. I will release tomorrow if nothing else comes up.
cc @mkvlr
@borkdude yay, thank you!
This will be a nice way to reproduce issues with babashka in the issue tracker :)
https://nextjournal.com/mk/babashka-environment is building the docker image
could also have a version that fetches & builds from git
too bad circle ci doensβt have predictible artifact names by sha
Maybe this helps? I haven't looked into the details of this script: https://twitter.com/ndj/status/1322999454295760898
babashka is also built on Github but I consider those builds secondary, since I sometimes find Github actions less stable
or you can build babashka from scratch in nextjournal :)
we already had a notebook for that I think a while ago
yep, guess for a bug report the sha would be best?
Usually I ask people about the version number
babashka/process is now available on clojars: https://clojars.org/babashka/process