This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-05-19
Channels
- # announcements (1)
- # asami (75)
- # beginners (16)
- # calva (14)
- # cider (4)
- # clj-kondo (11)
- # cljs-dev (3)
- # clojure (110)
- # clojure-australia (1)
- # clojure-china (1)
- # clojure-europe (38)
- # clojure-hk (1)
- # clojure-indonesia (1)
- # clojure-japan (1)
- # clojure-korea (1)
- # clojure-my (1)
- # clojure-nl (1)
- # clojure-sg (1)
- # clojure-spec (1)
- # clojure-taiwan (1)
- # clojure-uk (2)
- # clojurescript (34)
- # conjure (1)
- # data-science (9)
- # datahike (7)
- # datalevin (1)
- # datascript (1)
- # datomic (5)
- # etaoin (1)
- # fulcro (23)
- # graalvm (50)
- # helix (4)
- # hyperfiddle (8)
- # introduce-yourself (1)
- # jobs (3)
- # kaocha (10)
- # malli (8)
- # mid-cities-meetup (1)
- # minecraft (1)
- # off-topic (13)
- # pathom (14)
- # polylith (38)
- # reitit (1)
- # releases (1)
- # sci (65)
- # shadow-cljs (28)
- # specter (12)
- # tools-deps (8)
- # vim (1)
- # vscode (11)
- # xtdb (31)
As far as I can tell the only thing in the way of native binary for Datahike is the simple-supervisor inside of superv.async
Unable to compile the GraalVM native image because of an issue. There is more detailed discussion here. https://clojurians.slack.com/archives/CAJN79WNT/p1652929373280729
Even though it won't be as fast as it can be. Perhaps we can tell it to initialise the class at run-time.
I exported my 0.4 database and imported it in 0.5 with datahike/migrate
Now I get following expection, whenever I call d/history
:
Execution error (IllegalArgumentException) at hitchhiker.tree.op/eval11140$fn$G (op.cljc:8).
No implementation of method: :-affects-key of protocol: #'hitchhiker.tree.op/IOperation found for class: incognito.base.IncognitoTaggedLiteral
The same exception comes up, when I try to use wanderung to migrate from the new 0.5 database to another 0.5 database, with the same configs (except path).Hmm, sorry to hear that. I know @UB95JRKM3 was working on migration a lot. Unfortunately I can't help a lot here. Right now he is on holiday as well as @UQVCR784A. I guess the best thing to do is to open an issue on Github.