Jens Grassel

I can confirm this but I wonder if this is more an issue on the Ensime side...

Currently bumping into the same issue but will follow the development on https://github.com/sbt/sbt/issues/6193.

For me it works if I set `crossScalaVersions := Nil` in my root project. Note: I follow the recommended layout of having a root project which aggregates the cross project(s).

@tminglei Would it be possible to change the fetching logic for timestamp related values? I'm thinking in the direction of pulling them out as formatted datetime strings and parsing them...

Ah, okay. So the problem is that the column is a binary one. Which means we would have to wait for a fix from the postgresql side or store timstamp...

This is just a quickshot but would something like this maybe provide a workaround until this is officially fixed? ``` diff --git a/org/postgresql/jdbc2/AbstractJdbc2ResultSet.java b/org/postgresql/jdbc2/AbstractJdbc2ResultS index 64d949f..efbc370 100644 --- a/org/postgresql/jdbc2/AbstractJdbc2ResultSet.java +++...

I've just realised that the problem roots far deeper. Forget that workaround. ;-)

Hmm... The same also happens when using `NonEmpty`. ``` import eu.timepit.refined._ import eu.timepit.refined.api._ import eu.timepit.refined.boolean._ import eu.timepit.refined.collection._ import eu.timepit.refined.numeric._ import eu.timepit.refined.string._ @ type SomeString = String Refined MatchesRegex[W.`"[a-zA-Z_][a-zA-Z0-9-_.]*"`.T] defined type...

My approach is to generally fail a predicate if the given value "is null". This works for the matches stuff: ``` scala> type MString = String Refined MatchesRegex[W.`"[a-zA-Z_][a-zA-Z0-9-_.]*"`.T] defined type...

After giving this some more thoughts I propose to not handle this within refined. #### Reasoning as follows: 1. Automatic negation of predicates in the case of `null` breaks the...