Hi, Crux ppl Could you tell me if there is anything in clojure/crux which might break coz I am trying to run 2 crux DB in one VM? Errors are random clojure compulations

common things seems to be - breakage on trying to compile something from taonesso

Hi @olekss.janis What configuration of Crux are you using? Kafka + KV?

breakes on i.db

but when it is alone -> it works, but when two such codes end up in the same VM, randomly breaks on taonesso compilation -> tandomly -> means really randomly, feels like real clash of some namespaces or overwriting something somewhere

Let me try and see if I can reproduce

to have more fun -> it all runs with quasar -javaagent, though I tried to put all crux and it's dependencies on quasar exclusion list

yep broke

So not corda or quasar problem, pure this code gave exactly the same bug

Is there some cheap fix?

Running on windows

problem is I can't run sequentially, as I won't be able to control the node using crux startup during integration tests

could you elaborate on the latter point - how would you like to control the node?

I can't... that's the point, but seems crux has some issues or I am not smart enough to configure, but this simple code snipped prooves that 2 crux services started at the same VM breaks... I just checked the very code I posted with one instance, and it starts up no problem

OK, checking

so what is wrong with crux/clojure that it can't spin 2 nodes at the same time?

writing a test right now to verify.... hang tight

ok will be around - probably blinking in/out

@jonpither I rewrote just the code to run in sequence... and no problems... on first startup it took some time, probably due to compilation, and then very fast spinned up 2 versions without errors

Good to know. I've a failing test of sorts, but looks a bit different, am investigating https://github.com/juxt/crux/pull/340/commits/894732630c68e98d1df5facffd9ab9ef513e7292

note that test is in a branch, not master

in case if there is easy fix, ping me... now I am off

I am also free to bump up the dependency version in case if you release fix...

hmm ok my test had a bug in the assertions (typical) - it passes now: https://github.com/juxt/crux/blob/jp/node-config-property/crux-core/test/crux/node_test.clj

I also tried testing this against standalone, so I need to rethink my approach - will check something else

to be honest - didn't understood what you just told? Is there bug? Or I need to change something on my side? Or you will be rethinking approach how to implement something, or this bug is not so essential... ? 🙂

Sorry for being unclear - we can't find a bug after a few different tests now. When I said "rethinking our approach" - I meant coming up with ideas of tests to write, that would reproduce your error

@olekss.janis could you please share your gradle.kts file?

defo my bad, for being unclear up there ^