I upgraded leiningen today to 2.9.8 (not sure what I had before, some 2.9.x) and suddenly one of my projects started failing when running lein repl

Caused by: java.lang.IllegalAccessError: resolve-var does not exist
...
    at clojure.tools.analyzer.jvm$eval68270$loading__6721__auto____68271.invoke(jvm.clj:9)

@jumar not sure if it's the same issue, for one thing that one is relatively old now

mind to post your stracktrace, full?

clojure.tools.analyzer.jvm seems weird to have in Leiningen itself

Here's the full stacktrace with several references to propriatery namespaces replaced with things like XXX, etc.

Huh, it seems it's actually cider causing this - I will take it over to #cider

Hi I’m getting the following error when running `lein run`. Not sure what’s causing it:

Syntax error compiling at (/tmp/form-init5805669980636889423.clj:1:73).
19
could not find a non empty configuration file to load. looked in the classpath (as a "resource") and on a file system via "conf" system property
21

I’m running the following command in continuous integration: lein run -m user < /dev/null && npm i however, the problem is that the first command never terminates, and adding & after it causes the second command to run before the first command is finished. Is there a way to run the first command and wait for it to finish before running the second command?

that's what ; does - lein run -m user < /dev/null; npm 1 - or you can just put each command on its own line if this is a script file

but I'm still confused "the first command never terminates" would be a problem no matter what

if you’re starting a web server like i’ve seen you say, i would not expect lein run to terminate. It would launch a web server to keep handling requests

yeah but it runs a bunch of things and then settles down.

I want the other stuff to run (some tests) after it has populated the db in lein run and such

a straight forward way to do this is a little program that looks like

(db/migrate!)
(webserver/start! (config/CI))
(clojure.test/run-all-tests)

if the timing is predictable you can use lein run; sleep 10; npm 1

or you could pipe lein's output to a file, then wait for the file to contain a line of output indicating the server started before doing the next step- something like

lein run > logfile < /dev/null
tail -f logfile | grep -m1 "webserver started"
npm 1

that’s largely how nrepl works with clients

also, in CI you might already be dealing with docker images, and docker-compose has utilities for ensuring one task is done / ready for input before the next runs

another consideration is that if you make migrate a separate task instead of bundling it into run, you can wait for it to successfully complete and the start time for run will be smaller and more predictable

even more so, if you bulld a jar first, then use java to run that jar for the migrate and run steps