This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-09-04
Channels
- # aleph (1)
- # announcements (7)
- # beginners (22)
- # calva (31)
- # cider (2)
- # clj-commons (1)
- # clj-http (2)
- # clj-kondo (10)
- # cljsrn (33)
- # clojure (18)
- # clojure-europe (7)
- # clojure-nl (3)
- # clojure-uk (2)
- # clojurescript (93)
- # depstar (3)
- # events (1)
- # figwheel-main (3)
- # fulcro (13)
- # graalvm (95)
- # graphql (1)
- # introduce-yourself (1)
- # lsp (92)
- # off-topic (2)
- # pathom (11)
- # releases (1)
- # shadow-cljs (33)
- # specter (6)
- # tools-deps (4)
- # vim (3)
- # web-security (1)
- # xtdb (7)
This is probably known, but starting a local crux node on java 16 ends the JVM with SIGABRT
Yep. There are some workarounds, but can't guarantee any will resolve for your situation: https://github.com/juxt/crux/issues/894
fwiw, these env variables worked for me
;; CRUX_DISABLE_LIBCRYPTO=true
;; CRUX_ENABLE_BYTEUTILS_SHA1=true
;; to prevent crash "java is loading libcrypto in an unsafe way"
(c/start-node {})
2021-09-04 18:39:25,633 [nRepl-session-a0bb1109-6c2a-44f1-8841-1078801856ae] WARN crux.cache - Could not open ConcurrentHashMap.table field - falling back to LRU caching. Use `--add-opens java.base/java.util.concurrent=ALL-UNNAMED` to use the second-chance cache.
Process finished with exit code 134 (interrupted by signal 6: SIGABRT)
👍 2