This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-04-01
Channels
- # announcements (3)
- # beginners (59)
- # calva (23)
- # cider (58)
- # clojure (125)
- # clojure-dev (18)
- # clojure-dusseldorf (1)
- # clojure-europe (21)
- # clojure-germany (1)
- # clojure-hamburg (1)
- # clojure-italy (13)
- # clojure-nl (29)
- # clojure-poland (3)
- # clojure-spec (61)
- # clojure-uk (74)
- # clojurescript (12)
- # core-async (6)
- # cursive (4)
- # data-science (7)
- # datomic (14)
- # defnpodcast (1)
- # events (4)
- # fulcro (72)
- # juxt (36)
- # kaocha (3)
- # nginx (3)
- # off-topic (14)
- # pathom (5)
- # ring-swagger (68)
- # shadow-cljs (25)
- # spacemacs (8)
- # sql (42)
- # tools-deps (8)
- # vim (6)
A very peculiar behavior after, I think, upgrade of IDEA to 2019.1 and of Cursive to v1.8.1-2019.1. Now, if I open another project in a separate window, the index seems to be broken as some symbols are not resolved. So, the process after I invalidate the index and open project A is: 1. See all symbols in yellow (not resolved) with indexing in progress 2. Wait for the indexing to stop 3. Open project B 4. Indexing of project B is in progress 5. After it's indexed, half of the symbols in project A become yellow again. A simple restart seems to fix the issue, even after I open both of the projects.
@p-himik Well, that’s unfortunate. Sadly I don’t think there’s much I could do about that on the Cursive side, that sounds like something that’s changed at the IntelliJ level. Hopefully they’ll fix that soon in a 2019.1 point release.