This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-10-30
Channels
- # aleph (4)
- # announcements (5)
- # architecture (1)
- # aws (5)
- # babashka (12)
- # beginners (143)
- # chlorine-clover (4)
- # cider (16)
- # clj-kondo (44)
- # cljfx (26)
- # cljsrn (2)
- # clojure (34)
- # clojure-europe (28)
- # clojure-gamedev (1)
- # clojure-nl (3)
- # clojure-provo (2)
- # clojure-spec (6)
- # clojure-uk (17)
- # clojurescript (99)
- # code-reviews (6)
- # core-async (15)
- # cryogen (9)
- # cursive (14)
- # data-science (1)
- # datomic (16)
- # duct (1)
- # events (4)
- # exercism (1)
- # figwheel-main (3)
- # fulcro (3)
- # hugsql (7)
- # leiningen (4)
- # malli (15)
- # off-topic (13)
- # pathom (8)
- # re-frame (7)
- # reitit (35)
- # remote-jobs (1)
- # sci (10)
- # shadow-cljs (32)
- # sql (5)
- # tools-deps (102)
- # tree-sitter (3)
- # uncomplicate (7)
- # vim (40)
- # xtdb (8)
I am running dev-local/import-cloud (in parallel for unique db-names. May be relevant, not sure) and received this exception. Any idea what would cause this?
This definitely has something to do with being parallel. It will consistently fail when ran in parallel.
@U1QJACBUM I'm not sure that your answer https://ask.datomic.com/index.php/493/is-dev-local-import-cloud-thread-safe to true 🙂
huh. Ok I will run this down @U083D6HK9 . Could you copy your comment over to the ask question so we don't lose this to slack archiving?
Sure. I was hoping to provide a bit more insight than this exception though 🙂 Just wasn't sure what would be helpful for you all. I may be able to create a repro.
@U083D6HK9 also it might be relevant to know if these DBs are special (i.e. large or something)
I've also noticed that import-cloud can hang forever. I left an import running for the past 4 hours and the normal red "Loading ..." didn't even appear.
fyi, you can delete https://ask.datomic.com/index.php/493/is-dev-local-import-cloud-thread-safe?show=498#c498. I didn't see a way to on my end.