This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # announcements (21)
- # aws (6)
- # babashka (28)
- # beginners (39)
- # biff (1)
- # calva (23)
- # cider (5)
- # clj-kondo (108)
- # clojure (11)
- # clojure-europe (17)
- # clojure-nl (2)
- # clojure-nlp (10)
- # clojure-uk (8)
- # clojurescript (29)
- # community-development (4)
- # conjure (20)
- # css (3)
- # datalevin (9)
- # datomic (3)
- # events (2)
- # figwheel-main (11)
- # fulcro (36)
- # honeysql (7)
- # humbleui (4)
- # interceptors (4)
- # introduce-yourself (3)
- # jobs (1)
- # lsp (51)
- # malli (1)
- # meander (71)
- # minecraft (8)
- # other-languages (18)
- # pathom (15)
- # polylith (25)
- # portal (10)
- # re-frame (5)
- # reitit (15)
- # releases (1)
- # remote-jobs (1)
- # shadow-cljs (11)
- # tools-deps (27)
v0.1.14 of https://github.com/atomisthq/jibbit for packaging deps.edn projects into docker/oci container images - https://github.com/atomisthq/jibbit/blob/main/CHANGELOG.md#0114 • help from @olymk2 on an example that demonstrates a https://github.com/atomisthq/jibbit/wiki/polylith-example
Nice to see you continue developing jibbit. We almost started using it the other day but finally we didn't need to go the docker route for this specific project... Do you people still offer a product for our CI to e.g. run static checks on our clojure repos? Your new product (vulnerability scanning) seems to have eclipsed your (potentially) previous product.
Hey @U0514DPR7 - thanks, ya, the underlying product still supports adding custom github checks to github repos. We just really needed to start pulling in vulnerability data so we that we could start offering workload protection and remediation automation (for example: only pull images built from a commit that has passed these checks AND does not introduce new vulnerabilities). So it might have looked like we shifted away from the CI checks; although I would say it was more that we were being pulled towards other checks on artifacts further to the right (but still correlated back to the commit of course). Same principle though. Building artifacts and verifying artifacts should be separate concerns.
Ok so if I create an account and add a repo for vulnerability checking, I should still see the old catalog of e.g. Atomist Actions (or whatever was their name) that were marketed as competitive and more productive than GitHub Actions?
Ya, that's right Daniel. Feel free to DM me as well - I can give you more details.
I wrote a small, self-contained, and reasonably efficient—i.e. it uses transducers—library for doing TF-IDF calculations and a bit of stuff on top of that: https://github.com/kuhumcst/tf-idf If you’re interested in NLP, data science, or if you perhaps need to index documents for search this might be interesting to you?
Nice! Any performance rough estimates? Eg memory consumption / retrieval time etc? We have an Elasticsearch transition coming up but I'm keen to see if we can use our own algorithms for some things, to gain some flexibility.
Sorry, no real stats, but it's probably not possible to get much leaner memorywise while using Clojure's own data structures and its core functions. I guess the mathematics could possible be optimised using primitive operators, but I'm not interested in that kind of performance tuning for now.
SCI v0.3.5 - Clojure/Script interpreter
• https://github.com/babashka/sci/issues/711: support
• https://github.com/babashka/sci/issues/712: destructuring in protocol impl not working
• https://github.com/babashka/sci/issues/715: allow property access on vars in CLJS
print-err-fn in SCI core API
:name metadata via helper functions and use metadata for var names
• Improve error reporting for
• https://github.com/babashka/sci/issues/714: Improve instance member call parity with Clojure/JVM
sci/read-eval to false
• Fix for
copy-ns when var has no metadata
add-import API functions in
sci.async: EXPERIMENTAL namespace for async evaluation in CLJS
https://github.com/babashka/sci / #sci
Released clojure-lsp https://github.com/clojure-lsp/clojure-lsp
• Decreased uncached startup time by 60-70%!
• Improved completion performance
• Support sorting classes inside package imports during
• Improve progress report both on editor and CLI using new clj-kondo callback feature
• Rename namespace and all references when renaming a clojure file
For more information, check #lsp
This release was supported by https://www.clojuriststogether.org/
60-70% is wild! nicely done to everyone involved
omg the last bullet!!!
wow yeah, i missed that last bullet, that's a game changer
i need to find how to use it
It should work out of the box on all editors that support
workspace/willRenameFiles @U02N27RK69K, this was introduced on Emacs's lsp-mode some weeks ago, Calva should already have that
@UKFSJSM38 I'm curious what the numbers 12.35.40 in the version means, is this the time of release?
that's so rad!!