Fork me on GitHub
Slack Archive

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

2019-08-12

Channels

#cursive
<
2019-08-12
>
miikka12:08:16

Hey, I upgraded IDEA to 2019.2 and Cursive as well and now all symbols are unresolved and the deps.edn tab does not show any aliases

miikka12:08:25

i.e. nothing works, halp

miikka12:08:46

I guess it's a known problem

miikka12:08:41

i'm now confused

helios12:08:49

It is a known problem, afaik, that deps.edn in 2019.2 is not working (and possibly fixed in the latest preview of 2019.2.1?)

helios12:08:15

About the symbols, try to do "File > Invalidate Cache / Restart", it does help with me (but im not using deps.edn)

dpsutton12:08:10

check the pinned message about the current versions.

miikka12:08:11

how do I see pinned messages?

miikka13:08:38

I found the pinned messages but the view message button does not do anything...

miikka13:08:17

Invalidate Cache / Restart did not help with either of my problems

Joni13:08:26

I just joined here for a related issue and that’s the only thing i found.

miikka13:08:34

Also I'm not getting any NPEs

manutter5113:08:57

Basically there’s issues with 2019.2 (and to a lesser extent 2019.1), and the most stable version to use with Cursive right now is 2018.3.

manutter5113:08:05

I’m currently sticking to 2019.1, which has the issues where the paren matching is a bit messed up, but I work around that by using rainbow parens and paying real close attention to the matching colors.

miikka13:08:25

Downgraded to 2019.1, it works again.

👍 8
SgtZdog20:08:25

@cfleming is it a bug that the Evaluate Expression (alt+shift+8) during debug can't resolve symbols at the current breakpoint? I know this is the current best way to get a REPL while execution is suspended, but I was hoping I would have symbol resolution in the Evaluate. Perhaps I'm doing something wrong. If this is working as intended, I'm definitely putting in a feature request.

cfleming22:08:50

@miika Yes, for deps support 2019.1 works fine. As reported in that mailing list post, the problem you saw with unresolved symbols is still present there but it’s intermittent. If you get it again, restarting the IDE tends to fix it again for a while.

joaohgomes19:08:47

I had a similar issue but after downgrading to 2018.3 everything seems much stable now.

torbjornvatn07:08:47

I've tried upgrading to 2019.2.1 and downgrading to 2018.3, but I still get the unresolved symbols warning everywhere. A bit hard to code when I can't follow any references 😕

torbjornvatn07:08:52

I kept the 2019.2 "regular" version though, maybe that's causing some kind of confusion?

torbjornvatn08:08:59

Any news on when we can expect things to be back in a working state @cfleming? Do you have links to the relevant YouTrack tickets so I can follow them?

cfleming08:08:48

@U06BKCW95 There’s a pinned message in this channel which links to this: https://groups.google.com/d/topic/cursive/ntvsiLAehY0/discussion - that has all the details.

cfleming08:08:13

Unfortunately it’s not looking like either Deps or the indexing will be fixed in 2019.2.1, at least I haven’t heard that they will be.

cfleming08:08:13

I just posted an update to that thread about the recent Deps issue.

cfleming22:08:14

@kevin.zemon Yes, there’s an issue for that - I haven’t looked at it yet though.

👍 4