This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-09-21
Channels
- # announcements (51)
- # asami (5)
- # babashka (25)
- # babashka-sci-dev (26)
- # beginners (33)
- # calva (10)
- # clj-kondo (51)
- # clj-yaml (99)
- # clojure (96)
- # clojure-australia (3)
- # clojure-berlin (5)
- # clojure-europe (151)
- # clojure-norway (58)
- # clojurescript (20)
- # cursive (13)
- # datalevin (1)
- # datomic (19)
- # docker (6)
- # emacs (55)
- # events (1)
- # fulcro (50)
- # gratitude (8)
- # juxt (7)
- # leiningen (5)
- # malli (6)
- # membrane (1)
- # nbb (28)
- # off-topic (22)
- # pathom (7)
- # polylith (20)
- # portal (1)
- # reagent (37)
- # reitit (2)
- # releases (2)
- # reveal (32)
- # scittle (34)
- # shadow-cljs (46)
- # testing (10)
- # tools-deps (33)
- # xtdb (18)
@lee https://www.youtube.com/watch?v=0IA3ZvCkRkQ! It looks like your PR was merged (and our hunch that starting with an issue + PR and not using many words was the right approach for this maintainer!)
(Though I'm more of a https://www.youtube.com/watch?v=23YkC7Gx1Y4 kinda guy)
And I needed some of those words to clarify what the actual narrow issue in this case actually was š
pats @U04V15CAJ on the shoulder. YAML is infuriating/crazy-making.
It really looked like something different at the start. And finding the root cause made the change make more sense.
I really like your https://bitbucket.org/snakeyaml/snakeyaml/issues/550/regression-in-handling-number-like-strings#comment-64107854 @grzm!
Also thanks for the idea of how to approach submitting the PR/issue @U04V15CAJ, I think it really helped.
I can respect that. Helps pace the project, you know you get regular updates, keeps the maintainers on track while letting them work on other stuff too. I mean, would you want to worry about YAML 100% of the time?
> I can respect that. Don't get me wrong, I respect that too, I was just lol-sobbing because we just missed the last release window
Trying to give back to Andrey a bit https://bitbucket.org/snakeyaml/snakeyaml/issues/555/snakeyaml-github-actions-failing-for-jdk7.
Btw, I've been wondering, is there a similar "datetime" problem with what gets emitted for 1.1 and read by 1.2?
Ya, Andrey hinted at thatā¦ I wonder. So YAML 1.1 supports timestamps but YAML 1.2 does notā¦
$ bb -e '(yaml/generate-string {:foo #inst "2022-09-09"})'
"{foo: !!timestamp '2022-09-09T00:00:00Z'}\n"
Also:
āÆ bb -e '(yaml/parse-string "foo: 2022-09-09")'
#ordered/map ([:foo #inst "2022-09-09T00:00:00.000-00:00"])
Weird:
āÆ bb -e '(yaml/parse-string "foo: 2022-40-40")'
#ordered/map ([:foo #inst "2025-05-10T00:00:00.000-00:00"])
at least a date string doesn't get emitted like an un-quoted thing, right? <insert meme of boy and girl where girl says "right?" second time and boy looks frustrated>
I didn't even know YAML attempted to do anything with timestamps. I also didn't know there were such crazy subtle gotchas between versions
but now you do right? so are you still an agnostic or do you BELIEVE THAT YAML HELL IS FOR REAL š„
Btw folks, I was just making lame jokes, I hope I didn't offend anyone. I love other's people's clojure.
I love @lee ās Java, both because I think it was an elegant, concise solution and that I didn't have to write it :)
Yeah. Andrey did some minor edits I see here: https://bitbucket.org/snakeyaml/snakeyaml/commits/1962a437263348c3b90857cda4bbfa2bd97908f8
And now I realize @U04V15CAJ ās projects are really just his way of making our Clojure is more like his š
Thanks @grzm! It took me a some time to figure out where to inject my, uh, masterpiece. I used to write Java for a living. I almost forgot how!
Yeah I think his edits are good, his naming is probably clearer. I was surprised he made so few changes. I was wondering if heād be ok with that regex as I donāt think he uses regexes otherwise in that area of his code.
It matched exactly what I was hoping to do, but hadn't yet done the research of where or whether it was feasible in the codebsse
I think the only thing left to do is wrap up your PR @grzm - by the time we finish that, Andrey will probably have published 1.33
Yeah @grzm, the ātypesā thing was just me trying to be witty! I found my way around without too much difficulty.
More people should join this channel, they would come for the YAML but stay for the excellent jokes.
I couldn't help myself. I think I reached my lame joke climax today https://twitter.com/borkdude/status/1572643607324069888
One more idea though: a SnakeYAML PR which turns everything from camelCase to snake_case... Might be a good 1 April prank ;)
I think Andreyās opinion was that https://github.com/spring-projects/spring-boot/issues/32221#issuecomment-1237882892.
This is encouraging: https://github.com/spring-projects/spring-boot/issues/32221#issuecomment-1238021832
Yeah saw that, he seems to have taken quite a few hits of late and is shown to be generally trying to help out there!
I mean it doesnāt take much negative energy for me to say, āblech, maybe notā, when trying to help out. Looks like he has some real tenacity.
https://github.com/spring-projects/spring-boot/pull/32464/files might be worth studying someday.
I was just going to post that link and was going to say almost the exact same thing as you, but then I thought: ah well, lread has already done something similar, I guess ;)
I dunno about thatā¦ but I think our solution (snakeyaml numberish PR) might be better for us at this point in timeā¦ based on what we currently understandā¦ or donāt understandā¦
yes, as long as things just keep working and we can stay ignorant of any edge cases, this seems best
@lee and @grzm I get a really warm, fuzzy feeling for how youāve handled this issue vis a vis the SnakeYAML maintainer. I really feel youāve represented the Clojure community in the best way possible!
Thanks. I think the community does a great job of attracting great people and reinforcing great, productive behavior. I'm happy to be a part of it!