Clojurians Log v2

Hello 🙂 First time poster.. I was wondering if anyone could point me to a repo or blog post on how to setup a proper workflow for writing babashka with cursive? What I usually do is use deps to manage dependencies for my nREPL, and also require the same dependencies in with babashka.deps/add-deps. However it seems that I can't seem to resolve babashka.deps from within my REPL (curl, fs and process) work fine though

My deps.edn looks like this

{:deps
 {babashka/babashka                 {:mvn/version "0.4.3"}
  borkdude/spartan.spec             {:git/url "<https://github.com/borkdude/spartan.spec>"
                                     :sha     "12947185b4f8b8ff8ee3bc0f19c98dbde54d4c90"}
  org.clojars.clj-clapps/clj-clapps {:mvn/version "0.4.11"}}
 :aliases
 {:test {:extra-paths ["dev" "test"]
         :extra-deps  {org.clojure/tools.namespace {:mvn/version "1.1.0"}}}}}

Am I going about this all wrong? I was never able to get cursive intellisense to work if I don't set it up this way? Any cursive/babashka devs could point me to some workflow tips?

@nicolas.estrada938 There is an issue about babashka in the Cursive issue tracker. Also @cfleming seems to working on improving using babashka from Cursive, scroll back a few days in this channel to see the conversation.

I noticed that after hours of working in the bb repl it becomes slow to print the evaluation result and I have to disconnect/reconnect. After a while it's slowing anyway, I have to kill it and restart nrepl. I am using nrepl-server in VSC with Calva. Is it an issue with my setup ?

I'm not sure what's going on. Perhaps a memory leak?

I only use repl to evaluate 'foreground' functions. No futures, servers, threads etc

but perhaps the REPL builds up some kind of memory leak

Perhaps you can run things like (.freeMemory (Runtime/getRuntime)) to check this

(not sure if this is the right way of debugging this btw, just brainstorming)

Yes, I’m hoping better bb support will be in the next Cursive release.