babashka

https://github.com/babashka/babashka. Also see #sci, #nbb and #babashka-circleci-builds .
plexus 2020-11-26T07:32:38.466Z

@borkdude would it be possible to do a new babashka release? It seems the nREPL port fix isn't in 0.2.3 yet.

plexus 2020-11-26T11:11:28.469400Z

Thanks!

borkdude 2020-11-26T11:29:12.469600Z

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.

borkdude 2020-11-27T09:06:17.475800Z

Released 0.2.4

πŸš€ 1
plexus 2020-11-27T09:30:59.476Z

πŸŽ‰ :bmo:

plexus 2020-11-27T09:31:07.476200Z

Thank you πŸ™:skin-tone-2:

borkdude 2020-11-26T07:56:19.467Z

I’m working towards a new release but for now you can download a master version from #babashka_circleci_builds

2020-11-26T10:56:20.468200Z

Is there any router library with httpkit that is known to work out of the box with babashka?

borkdude 2020-11-26T10:59:51.469Z

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

2020-11-26T11:02:10.469300Z

Thanks :)

borkdude 2020-11-26T11:29:45.470200Z

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.

borkdude 2020-11-26T11:29:56.470400Z

cc @mkvlr

mkvlr 2020-11-26T12:14:57.470600Z

@borkdude yay, thank you!

mkvlr 2020-11-26T15:37:33.470900Z

🀫 http://nextjournal.com/try/babashka?cm6=1

1
3
borkdude 2020-11-27T08:38:09.474500Z

@mkvlr Can I share that link publicly in the release notes?

mkvlr 2020-11-27T08:47:59.474700Z

@borkdude yes please

borkdude 2020-11-27T09:01:51.475600Z

Done, released!

🦜 1
borkdude 2020-11-26T15:39:17.471200Z

This will be a nice way to reproduce issues with babashka in the issue tracker :)

mkvlr 2020-11-26T15:41:52.471400Z

https://nextjournal.com/mk/babashka-environment is building the docker image

mkvlr 2020-11-26T15:42:29.471600Z

could also have a version that fetches & builds from git

mkvlr 2020-11-26T15:42:49.471800Z

too bad circle ci doens’t have predictible artifact names by sha

borkdude 2020-11-26T15:44:01.472Z

Maybe this helps? I haven't looked into the details of this script: https://twitter.com/ndj/status/1322999454295760898

borkdude 2020-11-26T15:45:23.472300Z

babashka is also built on Github but I consider those builds secondary, since I sometimes find Github actions less stable

borkdude 2020-11-26T15:45:51.472500Z

or you can build babashka from scratch in nextjournal :)

borkdude 2020-11-26T15:46:09.472700Z

we already had a notebook for that I think a while ago

mkvlr 2020-11-26T15:56:00.472900Z

yep, guess for a bug report the sha would be best?

borkdude 2020-11-26T16:06:51.473100Z

Usually I ask people about the version number

borkdude 2020-11-26T22:30:09.473600Z

babashka/process is now available on clojars: https://clojars.org/babashka/process

πŸŽ‰ 6