you don't need to call the function just require the namespace that contains it at some point

(you can require it manually in the REPL, but also require it in your dev entry point so that it's always loaded)

I'm assuming you're using shadow cljs ou figwheel main for hot reload

doseq is great when parallelism is not needed and sequential will do fine. Here’s a snippet using core.async to bring arbitrary parallelism to a task like this one, without using pmap:

(let [dest-ch (a/chan)
      parallelism 8]
  (a/pipeline-blocking parallelism
                       dest-ch
                       (map clone-repo)
                       (a/to-chan! (extract-key :sshUrl repos))
  dest-ch))

I had this problem, check out @U7ERLH6JX response https://clojurians.slack.com/archives/C053AK3F9/p1685473873556869 I ended up using virtual threads in my problem

Here is what it looks like with doseq:

(defn clone-all-repos
  [repos]
  (doseq [url (extract-key :sshUrl repos)]
    (clone-repo url)))

This is true; this particular function is significantly slower without parallelization, because it clones each repo one at a time.

I've had success using claypoole, https://github.com/clj-commons/claypoole

Here you could use pdoseq which I think will do what you want.

Cool, thanks for the tip! That might get too advanced for me at this stage, and I'm not sure whether it would work in a Babashka script, but I'll save it for later!

@U01PE7630AC, Any particular reason not use clojure/async for paralism ?

@U05AH1BJNQ6 No good reason other than I haven't learned about that yet 🙂

deref'ing will block the thread on which deref was called. deref takes a timeout if you want to avoid blocking for a long time, and an http-kit client request takes a timeout if you want to give up on getting a response after some amount of time. As far as concerns about blocking all the threads, requests could be batched, or use core.async's pipeline-async function, or one of any number of strategies... it's probably mainly a question of design based on your specific context.

Thanks for your response, I am thinking of calling it using async.chan and derefer the result , will that be a good approach ? because async/go will create light weight threads

I'd say it really depends on context

https://clojure.org/guides/destructuring#_namespaced_keywords

it's destructing values from a map with namespaced keys like {:reitit.core/router <something> ...} where the alias r refers to reitit.core (or some similar) namespace

here's a nice discussion highlighting the various ways you can destructure such maps https://clojureverse.org/t/poll-destructuring-namespaced-keywords/1388

Aah nice, yeah now I understand. Thank you so much!

you are using an old version of the Clojure cli, before :git/sha was added, so you update to the latest

https://clojure.org/guides/install_clojure

Ah. Is there a CLI command to update it? If not, do I need to uninstall the current version before installing the new one?

depends which OS and method of install you used

I'm using WSL and unfortunately, I don't remember how I installed it. Is there a way to check that?

If you used the Linux installer, should be able to just install the new version following that script

I'll try that. Thanks for your help!