My suspicion is that your functions return lazy sequences, that are not realized since they are never inspected. This would happen if you're using map or for to perform side-effects, for instance. If that is the case, then doseq is a good option for iterating over side-effecting code.

Thanks that fixed it.

You might prefer https://clojuredocs.org/clojure.core/dorun if you don't plan to use the sequences returned by doseq. It may not matter much in your case but where those sequences are large it makes a big difference. dorun doesn't "retain the head" of the sequence, so each iteration is used once and then dropped so it can be garbage collected efficiently. (I sort of feel using doseq without explicitly making use of the returned sequence should also allow each iteration to garbage collect well but that's much more difficult to reason about or prove!)

Yes, dorun or run! are best when you want to iterate for side-effects only and don't use the return value at all

thanks

Please note that doseq does not have a return value.

> "Repeatedly executes body (presumably for side-effects) with > bindings and filtering as provided by \"for\". Does not retain > the head of the sequence. Returns nil."

Right, I forgot. It goes: map -> run! doall -> dorun for -> doseq

You can also avoid sequence functions altogether and use eager functions like: mapv reduce any of the transducer arity loop/recur

That has been really helpful, I was completely unaware of most of those functions

@U07FCNURX Thanks - I was mixing up doseq with doall

jetty web server, reitit+malli for routing, web handling and schema validation, Component for lifecycle management, aero for configuration

Not the smallest template or set of concepts to buy into but it could repay the investment? https://github.com/furkan3ayraktar/clojure-polylith-realworld-example-app

#biff is another option for a more full-stack template: https://biffweb.com/ Some of the built-in components rely on XTDB, but it wouldn't be that hard to modify to use Datomic instead It also uses jetty, ring, reitit, and malli

My Clojure North 2020 https://github.com/markbastian/clojure-north-2020’s final example uses REST/Swagger, Datahike (another datalog variant — would be easy to change to Datomic), Jetty web server, and Integrant to tie it all together.

Cool, thanks guys.

I have helper functions and macros that can create temporary directories and files, the issue is making the test runner think "i'm in this specific directory", so calling (io/file "deps.edn") sees the file in the temporary directory

Can you use with-redefs in the tests?

(redefining a function that you use to get the current directory)

I could, but I was hoping for something slightly less brittle. Maybe that would be fine, just makes me feel like I'm playing with fire

The boring answer is to make pwd an argument. (System/getProperty "user.dir") can be understood as a "side cause", those are best pushed to the boundaries of your program

ah yeah, that makes sense. thanks

The best I can think of is setting up your own maven “repository” by starting up a webdav server in a container and making dummy credentials that allows leiningen et al to GET, PUT, and MKCOL as it wishes

at some point in time I had a webdav server as a private maven repository with apache2… if you’re interested, i can eventually dig up the configuration files. shouldn’t be hard to containerize it and run it in CI

Interesting. the key part is that it should be a proxy, e.g. if artifact foo is not found, query it in Central / Clojars Perhaps such an offering doesn't exist...

You could set up an actual Maven caching proxy, such as Apache Archiva.

There are several drop in proxies

Sonatype Nexus, JFrog Artifactory, etc

@U45T93RA6, I learned a bit, not much, but a bit, about Sonatype nexus as a cache https://github.com/clj-commons/pomegranate/issues/107

Did you consider the :local-repo option in Lein (deps have a similar option)? There might be a special path on your machine that holds m2 artefacts, and you can install Clojure packages there. This folder would act like a cache. Not sure if it solves your problem, but just an idea.

You can even share that folder in CI across various steps/builds, and save the traffic.

Nice! @UE21H2HHD’s example seem much handy. Although I was surprised to find no good google hits for <Sonatype Nexus || JFrog Artifactory> + <circleci | github actions>

github actions can be set up to use specialized Maven settings, which I presume could use a Maven proxy (although not sure how that works when using it on github). The github java action lets you easily set up Maven repo caching which is kind of the norm.