events 2022-10-10 | Slack Archive

reborg16:10:03

Still room available for the first London Clojurians in person Meetup after a long time: https://www.meetup.com/london-clojurians/events/288023345/ (Wed, Oct 12th, 6pm BST)

‼️ 1

Daniel Slutsky19:10:20

Note we have three visual-tools meetings this month: https://clojureverse.org/t/visual-tools-meeting-13-monthly-interactive-visualizations-shiny-shadow-cljs-clay/ https://clojureverse.org/t/visual-tools-meeting-14-clerk-workshop/ https://clojureverse.org/t/visual-tools-meeting-15-a-common-ground-for-notes-with-kindly/

Daniel Slutsky14:10:26

Just fixed the hour in meeting 15. 🙏

Daniel Slutsky19:10:36

The second NLP-in-Clojure meeting will take place in the end of the month, with a talk by @carsten.behring. https://clojureverse.org/t/nlp-study-session-2-predict-real-vs-fake-disaster-tweets-with-dvc-clojure-and-python/

Daniel Slutsky14:10:01

#Also sent to the channel

See you on Sunday at @carsten.behring's NLP talk, combining Clojure, Python, and DVC.

Daniel Slutsky11:10:43

#Also sent to the channel

See you later today at the NLP talk.

Daniel Slutsky17:10:10

#Also sent to the channel

Starting in a moment: https://bit.ly/daslu2-zoom

nate22:10:31

Two recordings of recent Los Angeles Clojure Meetup events: • https://www.youtube.com/watch?v=_tpNKAv4fro - Polylith with Sean Corfield (June 2022) • https://www.youtube.com/watch?v=Dr8wBGPXxng - Exploring the Flow-storm debugger (September 2022)

🎉 4

1

jpmonettas23:10:05

nice to see people trying the debugger. The latest version fixes a bunch of issues specially on windows, and there is also a chapter on the UserGuide on how to make it work on WSL2 without using a remote connection https://jpmonettas.github.io/flow-storm-debugger/user_guide.html#_working_on_windows_with_wsl2

jpmonettas23:10:55

I also see that you where trying to instrument clojure namespaces like clojure.core/inc and clojure.walk/walk. The thing with instrumeting clojure namespaces is that the debugger uses those, so if you instrument clojure.core/inc for example, when it runs it will trace and make the debugger "react" to it, and part of the debugger code will probably will be using inc to show you the results, so it will be called again, and you will get a stack overflow

Daniel Slutsky14:10:01

replied to a thread:The second NLP-in-Clojure meeting will take place in the end of the month, with a talk by @carsten.behring. https://clojureverse.org/t/nlp-study-session-2-predict-real-vs-fake-disaster-tweets-with-dvc-clojure-and-python/

See you on Sunday at @carsten.behring's NLP talk, combining Clojure, Python, and DVC.

Daniel Slutsky11:10:43

replied to a thread:The second NLP-in-Clojure meeting will take place in the end of the month, with a talk by @carsten.behring. https://clojureverse.org/t/nlp-study-session-2-predict-real-vs-fake-disaster-tweets-with-dvc-clojure-and-python/

See you later today at the NLP talk.

Daniel Slutsky17:10:10

replied to a thread:The second NLP-in-Clojure meeting will take place in the end of the month, with a talk by @carsten.behring. https://clojureverse.org/t/nlp-study-session-2-predict-real-vs-fake-disaster-tweets-with-dvc-clojure-and-python/

Starting in a moment: https://bit.ly/daslu2-zoom

2022-10-10

Channels