Just tried opening a REPL in the dev build using Run with Deps and got this printed in an error window:

java/sql/Timestamp
Cloning: 
Checking out:  at c830e77ff9b00f1e27b7e21f2393f83261aec61b
Downloading: com/cerner/clara-rules/0.19.1/clara-rules-0.19.1.pom from 
Downloading: prismatic/schema/1.1.6/schema-1.1.6.pom from 

I've also now gotten to a place where the Aliases folder in the Clojure Deps dropdown is gone.

I was using 2019.2.2. Switched back to 2018.3.6 and the Aliases box came back.

@kenny The aliases box will probably not appear if the project can’t resolve, so that might actually be the same problem. Based on the java/sql/Timestamp part of the error, that’s because 2019.2 by default uses JDK11. Some Clojure deps aren’t ready for JDK9+ yet, and since the new deps integration (like the lein one) runs some stuff in-process, that can affect it. Unfortunately these error messages are always really obscure and it’s hard to track them down. Are you using s3-wagon-private, for example? If you upgrade that to 1.3.2 this problem should go away, assume that dep is the issue.

One thing that was a bit strange about what I was doing is switching between branches where projects had been removed & added. Not using s3-wagon, to my knowledge.

Ok, there are other deps with this problem, but that’s been the one that has bitten most people.

All our projects run and are deployed with Java 11. That means it's likely coming in from a dev dep, I guess.

Yeah, sounds like it.

I’ll check to see if I can get a better idea of where those errors come from.

The disappearing aliases thing was quite confusing though. Is there a way to show an error message instead?

Did you see an error about the project resolution failing?

Maybe. I'll try to reproduce it again. What would make it harder to notice is when switching between branches that have removed modules. It seems like every time I switch a branch I get 1-3 notification boxes which makes noticing error messages a lot harder.

What are the notification boxes? If they’re from Cursive I can try to reduce that or combine them somehow.

After just doing the switch again, I got 2: Refresh deps and Update npm deps

Shouldn't modules be branch dependent?

How do you mean?

Oh, and another one is: > Workspace associated with branch 'platformization' has been restored

Right, IntelliJ does that - basically that means that it stores things like open files, window layout, breakpoints etc per branch, and when you switch it restores them.

Yeah it's useful but adds to the notification noise when switching branches.

Right, unfortunately I can’t change any of that. The only one I can control is the deps refresh one, that you won’t see when I fix auto-import if you have that enabled, but the others are out of my control

In master I have modules: a, b In branch1 I have modules: a, c Module a & b seen in Clojure Deps when in master and modules a and c when in branch1.

Is that not what you’re seeing?

No. Modules persist across branches. Sometimes I'll get an error about a module disappearing when switching between branches as well. I can't seem to reproduce the latter right now.

Yeah, thinking about it I can see why that might happen. I’ll think about that and try to fix it.

The actual directory for the module may still exist when switching to a branch without the module (e.g. it contains unversioned files like node_modules) but will not contain a deps.edn.

Ok. I think I can check that and fix it.

Any idea how to figure out the problem dep for that java/sql/Timestamp thing?

It must have something to do with Cursive since I can open a REPL in the CLI without getting that exception.

No, I’m going to think about that and see if I can reproduce it and improve the error message.

e.g. I can do this in the CLI

clj -A:dashboard:dev:test
Clojure 1.10.1
user=> 

Yeah, the way this works is that Cursive runs the project resolution in-process in an isolated classloader, which makes it a lot faster for larger projects. The issue is that the JDK used is always the IntelliJ boot JDK, this was almost never a problem previously, but after JDK9 it’s a issue.

Even weirder is it only happens when I use Run with Deps. If I select Run with IntelliJ project classpath with the above aliases selected, it works.

Can you isolate the dep more by trying those aliases one by one? I guess each one can probably have a lot of deps in it though.

Yeah, run with IntelliJ classpath doesn’t do anything at all to calculate the classpath, because IntelliJ already has it recorded.

I think I know the problem dep because I've had issues with it before - metasoarous/oz

Ok, does upgrading that to latest help?

Trying that now. I can probably override deps to get it to work too.

Latest still has the issue.

But actually running your project with that dep on JDK11 doesn’t have the problem, right?

What do you mean by "actually running"?

Actually, thinking about this I’m not sure this makes sense for deps. Lein has this problem because the dev deps run arbitrary code during project resolution via plugins - Deps doesn’t do that.

Well, presumably oz is actually used for something in your project. That project works if you run it e.g. from the command line, right?

If I use the "Run with IntelliJ project classpath" and load a ns uses Oz, it will work.

i.e. it doesn’t look like oz has a problem with JDK 11.

I think there’s something else going on here, and the more I think about it the more I think it might be something in deps itself that Cursive is doing differently.

I have to step out for a bit, but I’ll be back later and I’ll see if I can repro this issue.

Ok. I'm going to head out for the evening. Can look at it more tomorrow. The dashboard does have this dep:

;; explicitly include this dep to fix a jetty version conflict
                                            com.cognitect/http-client {:mvn/version "0.1.99"}

Ok. I’ll see if I can come up with a project which repros the problem.

Loaded up an existing project with a module that no longer existed and received: