This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-10-14
Channels
- # announcements (9)
- # beginners (49)
- # calva (26)
- # cider (6)
- # clj-kondo (17)
- # cljsjs (1)
- # cljsrn (2)
- # clojure (72)
- # clojure-europe (5)
- # clojure-france (8)
- # clojure-greece (1)
- # clojure-italy (5)
- # clojure-nl (9)
- # clojure-spec (49)
- # clojure-uk (17)
- # clojuredesign-podcast (13)
- # clojurescript (137)
- # cursive (15)
- # data-science (1)
- # datomic (55)
- # duct (2)
- # emacs (5)
- # figwheel-main (11)
- # fulcro (11)
- # graphql (1)
- # hoplon (1)
- # instaparse (1)
- # jobs (12)
- # jobs-rus (1)
- # leiningen (1)
- # nrepl (34)
- # nyc (2)
- # off-topic (1)
- # onyx (1)
- # pedestal (1)
- # re-frame (6)
- # reitit (3)
- # remote-jobs (1)
- # shadow-cljs (196)
- # sim-testing (1)
- # spacemacs (9)
- # sql (1)
- # vim (70)
- # xtdb (31)
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
Hi @olekss.janis What configuration of Crux are you using? Kafka + KV?
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
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
problem is I can't run sequentially, as I won't be able to control the node using crux startup during integration tests
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
@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
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?