This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-08-21
Channels
- # announcements (20)
- # beginners (31)
- # biff (8)
- # cherry (5)
- # cider (4)
- # cljs-dev (1)
- # clojure (26)
- # clojure-australia (2)
- # clojure-europe (16)
- # clojure-spec (10)
- # community-development (8)
- # conjure (1)
- # core-async (1)
- # data-oriented-programming (1)
- # data-science (54)
- # datascript (10)
- # fulcro (1)
- # graalvm (2)
- # malli (5)
- # off-topic (3)
- # pathom (23)
- # rdf (1)
- # re-frame (6)
- # reitit (11)
- # shadow-cljs (6)
- # squint (2)
- # xtdb (33)
Hey, I’d like to try Biff but I immediately fail after the install. I run ./task dev
and it says
[main] WARN xtdb.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.
WARNING: /usr/local/Cellar/openjdk/18.0.2/libexec/openjdk.jdk/Contents/Home/bin/java is loading libcrypto in an unsafe way
rlwrap: warning: clojure crashed, killed by SIGABRT.
The same thing happens if I clone the repo.I think I vaguely remember someone getting a similar error a while ago. I can dig into this later when I'm at my desk, but in the mean time a couple things to try:
• add :biff.xtdb/kv-store :lmdb
to the config.edn file (in either the :prod
or the :dev
section, doesn't matter)
• try running it on jdk 11
those are just random things to try. not sure what the underlying issue is, but I'm guessing it's related to xtdb. do you get a stack trace anywhere? (saved in a file perhaps?)
Thanks for looking into it.
• adding :biff.xtdb/kv-store :lmdb
didn’t help
• no stacktrace, at least not in the current folder or in /var/log
• jdk 11? that’s kinda old but I’m giving it a try
jdk 11's just what I happen to test on :). what kind of machine are you on? (m1 Mac?) I'll look up that libcrypto message later and see if anything turns up.
there's a an old slack conversation here where someone says that you can get around it by setting a couple env vars: https://clojurians-log.clojureverse.org/xtdb/2022-05-06
[main] WARN xtdb.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.
I get the above warning too when running ./task dev
yet it does not prevent Biff or xtdb from running.
I suspect the loading libcrypto in an unsafe way
warning is the problem? Perhaps openssl needs to be upgraded if you've recently upgraded OpenJDK to version 18.0.2Yeah, I've been getting the cache warning too
this sounds related to https://github.com/xtdb/xtdb/issues/894#issuecomment-892612270 a workaround is outlined higher in the thread: https://github.com/xtdb/xtdb/issues/894#issuecomment-891181861