Clojurians Log v2

So clojurists together applications for next year close in a week or so... as I said earlier I'd love to mentor if anyone decides to apply for that. But no one took my hint a little while ago so I'm guessing there's not much interest? Would anyone be interested in applying with me as a pair?

@plexus updated changelog https://github.com/LouDnl/at-at/blob/master/CHANGELOG.md

extra utilities https://github.com/LouDnl/at-at/blob/master/doc/UTIL.md

To set some context for people reading along, @thierry572 started a discussion on #clj-commons about moving at-at to commons. But we should be able to get an official release out instead.

I'll probably do the same thing as with overtone, first do a more conservative release just to get the more obvious fixes and any changes that have accumulated on the main branch out and set a new baseline, then we can look at evolving the library.

dev branch migrated to deps.edn 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 github actions for building releases borkdude added a pull to fix reflections for babashka

the authors of the pullrequests I added are mentioned here: https://github.com/LouDnl/at-at#adaption-and-addition

@thierry572 just to help set your expectations, I'm mostly here to help coordinate and make sure the mail gets through. I'm not stepping up as "the maintainer" of any of these things, and will limit my investment significantly.

I added this feature because I needed it 🙂

(after 10000 #(println "hello from the past!") my-pool :uid "my-unique-identifier") ; schedules function
(at (+ 10000 (now)) #(println "hello from the past!") my-pool :uid "my-unique-identifier") ; will throw an Execution error
; Execution error at overtone.at-at/at (at_at.clj:281).
; Error: Unable to schedule job with uid my-unique-identifier, job is already scheduled.

@plexus thats fine, it would be nice to merge my stuff into main repo if reviewed

Yes, I'll have a look at what's mergable, and if there's any unreleased stuff on main.

Are you interested in contributing to at-at and the overtone ecosystem going forward, or do you mainly want to get these things out so you can move on?

I updated a bunch of stuff

If needed I can contribute sure

Its why I released a new version

Did you reach out to Sam?

I dont think so because the repo seemed 'dead' as in unmaintained, hence I created a fork but kept most stuff the same for sake of the original author. dont want credits for stuff I did not create 🙂

Makes sense, the original authors are indeed no longer actively doing any Clojure stuff. Sam is fully focused on Sonic-Pi. That said he does still care for Overtone, and is happy to see that people are still willing to maintain it. I'd like to get these projects into the current decade. Currently that mainly means making sure that stuff actually works, fixing long standing issues and compatibility problems with newer JVMs, newer Clojure, OS-level changes.

I think I had a look around Slack but its been more then 6 months

For me it's mainly that at-at is a great scheduler, it's lightweight and just works

Beyond that I think we also want to give people a chance to put their mark on these libraries, to further improve and expand them in the spirit of the original implementation, while honoring what is there, and maintaining backwards compatibility. I think it's a tricky balance to get right, but I think it's necessary for them to stay relevant and alive.

Yes, I agree on that!

So yeah, happy to see someone taking an interest in at-at and already doing some of the maintenance work. Since you have substantial changes and additions on your branch I would like to review that first, and bring it in piecemeal, starting with any bugfixes.

I added github actions for testing new commits against all required versions of Clojure and with Java 11

That's fantastic!

Clojure 1.6 up to 1.12 alpha1 are tested

main release uses 1.10.1

Well, let me know if I can do anything or if you need any information

I got a busy day today but I'll have a look this weekend on early next week, and get a release out

My repo could be merged into main branch if needed 😉

@plexus np, I am reachable here or if you need I can give you and email address