Clojurians Log v2
clj-commons 2023-11-17
Since overtone/at-at is widely used but hasn't been updated in a while and there are some open PRs and issues I created a fork and released an updated version earlier this year. Someone - cant find their response - suggested it be a good idea to add at-at to clj-commons. We would obviously need agreement from the original author. How would we best go about this to get it arranged? https://github.com/LouDnl/at-at
I believe that @plexus might be tinkering with overtone stuff?
At least I seem to remember that lambda island released a new version of overtone not so long ago?
A bunch of folks are reviving Overtone, see the #overtone channel and mailing list. I have repo and clojars access. I haven't looked into the state of at-at yet. @thierry572 it would be helpful if you can comment on PRs saying you've reviewed them and adding any remarks or concerns, then I can be pretty quick in merging what seems reasonable to merge, and I can push a new release.
@plexus I released a new version in january which has all PRs that are open including some new features and a utility namespace.
So you reviewed the PRs? Or did you just blindly merge everything?
Not blindly no, because when I tried that things broke ;)
Heres my clojars link https://clojars.org/org.clojars.loud/at-at
Not surprising, that's why some comments to help me triage would be helpful. Updating the CHANGELOG will also be a bit of work. If I can get help with these things we can get an official release out very quickly. If not it'll take a bit longer.
Ah nice, that's already great!
non required namespace with utilities
I mainly revived at-at earlier this year because I needed a unique identifier to be able to ignore duplicate jobs
Also have a dev branch on deps.edn
unfinished tho: https://github.com/LouDnl/at-at/blob/dev/deps.edn
added unittests aswell https://github.com/LouDnl/at-at/tree/master/test/at_at
and some actions for building releases
borkdude added a pull to fix reflections for babashka