This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-04-05
Channels
- # announcements (7)
- # beginners (10)
- # calva (14)
- # clj-otel (8)
- # clojure (42)
- # clojure-europe (20)
- # clojure-nl (1)
- # clojure-norway (22)
- # clojure-spec (8)
- # clojure-uk (7)
- # core-async (10)
- # cursive (1)
- # events (1)
- # hyperfiddle (20)
- # introduce-yourself (1)
- # jobs-discuss (11)
- # lsp (48)
- # missionary (3)
- # music (1)
- # off-topic (7)
- # overtone (9)
- # pedestal (17)
- # rdf (1)
- # releases (3)
- # shadow-cljs (12)
- # specter (13)
- # squint (1)
- # yamlscript (3)
The next major version of kc-repl (the interactive Kafka consumer) is out. This adds handling for Avro (via Schema Registry integration) and Protobuf (via Schema Registry, or standalone compiled classes from .proto files) data, in addition to numerous bug fixes. I also recorded a few demo videos to showcase some of the capabilities of the tool, which you can find linked to the bottom of the project’s README.md
Contributions and feedback very much welcomed! There are a lot of issues to tackle, and I’m particularly interested in getting help on the deps.edn setup, and getting proper CI working.
https://github.com/jeff303/kc-repl/releases/tag/v2.0
Big thanks to the following community members:
@U0567Q30W for help with Cursive and deps.edn related issues
@U064X3EF3 for more help with deps.edn and miscellaneous things I forget because my Clojure usage is sadly infrequent
@U04V70XH6 for making build-clj, which I was surprised to find deprecated in the time it took me to get this release out 😅, but which nonetheless helped me get the initial version out and provided a path for migrating to tools.build
A lot of the ideas behind build-clj and the lessons learned from using it are written up in https://clojure-doc.org/articles/cookbooks/cli_build_projects/ now.
1> Didn’t see anything in the readme, how’s SSL support?
It should work! The demos I recorded were against a Confluent Cloud hosted Kafka cluster using the SASL_SSL security mechanism. Under the hood, I’m just using the standard Apache Kafka consumer client libs, which in turns means the properties are identical (with a few exceptions, which I need to document admittedly).
That said, the existing tests don’t exercise that. I’ve burned an absurd amount of time trying to get a workable set of Docker test containers for Kafka + Schema Registry + Zookeeper, so haven’t even tried to mess with SSL for testing yet. So I won’t 100% rule out any issues with it.
Released two new libraries for writing telegram bots :robot_face: https://github.com/Akeboshiwind/tg-clj - An aws-api inspired wrapper for the telegram bot api https://github.com/Akeboshiwind/tg-clj-server - A framework to help build bots out of composable (testable) parts These fell out of wanting to just read the telegram api docs (which are pretty good) and not having to work with a layer in-between. Feedback would be much appreciated :)