Fork me on GitHub
#babashka
<
2022-09-13
>
grzm21:09:12

Looks like there’s a regression in clj-commons/clj-yaml since 0.7.109 and including the current release 0.7.110 It’s no longer I noticed it while using babashka 0.9.162.

% clj -Sdeps '{:deps {clj-commons/clj-yaml {:mvn/version "0.7.108"}}}' -M -e "(require '[clj-yaml.core :as yaml]) (doseq [x [\"083\" {:x \"083\"}]] (print (yaml/generate-string x)))"
'083'
{x: '083'}
 % clj -Sdeps '{:deps {clj-commons/clj-yaml {:mvn/version "0.7.109"}}}' -M -e "(require '[clj-yaml.core :as yaml]) (doseq [x [\"083\" {:x \"083\"}]] (print (yaml/generate-string x)))"
083
{x: 083}

grzm21:09:52

I’m guessing this is in the upstream snakeyaml library.

borkdude21:09:07

@grzm if this is an urgent problem, I can release bb master tomorrow, I already updated clj-yaml on master.

grzm21:09:31

Cheers! Tomorrow would be fine.

grzm21:09:49

Crikey. I can’t even get the issue opened on github and you fix it already.

borkdude21:09:14

you can get a new master build here: https://github.com/babashka/babashka-dev-builds to test if it was fixed

grzm21:09:31

As far as I can tell, the bug actually is still in clj-yaml 0.7.110

grzm21:09:41

% clj -Sdeps '{:deps {clj-commons/clj-yaml {:mvn/version "0.7.110"}}}' -M -e "(require '[clj-yaml.core :as yaml]) (doseq [x [\"083\" {:x \"083\"}]] (print (yaml/generate-string x)))"
083
{x: 083}

grzm21:09:55

I haven’t checked snakeyaml to see if it’s fixed there.

borkdude21:09:28

In that case, please make some noise in #clj-commons and then we can update the lib in bb

grzm21:09:58

Ah, that’s what I was looking for and not finding.

grzm21:09:59

Cheers!

👍 1