Ólafur Páll Geirsson

My bad, using `eval ..` won't work because the `lsif-java` script defaults to Java 8 anyways. Your workaround is OK for now. I'll see what we can do to improve...

The problem could be that the detected `rootUri` (workspace directory) does not point to an sbt build. @ArulselvanMadhavan can look a `.metals` directory a parent /child directory of your intended...

@ArulselvanMadhavan it seems your client is sending invalid JSON configuration with `null` values. We should report a helpful error in that case, please open a ticket in Metals.

@itryapitsin, any chance you could take a look at this?

Currently, `sourcecode.File` returns `c.enclosingPosition.source.path` which can be problematic - it's an absolute path depending on what the build tool passes in - string is OS-dependent - awkward to extract only...

@varungandhi-src the root bug seems to be that semanticdb-kotlinc is setting `Kind.TYPE` here instead of `Kind.Class` https://sourcegraph.com/github.com/sourcegraph/scip-kotlin@cbbf452c9bf0165d8144ba17a6f2026e00257fd6/-/blob/semanticdb-kotlinc/src/main/kotlin/com/sourcegraph/semanticdb_kotlinc/SymbolsCache.kt?L167:62-167:66 Alternatively, we can update scip-java to add an extra case for `case Kind.TYPE:...

Used the opportunity while fixing Kotlin 1.9 support to also fix this bug https://github.com/sourcegraph/scip-java/pull/682

I'm trying to confirm 100% that this bug has been fixed but now I'm hitting on another bug in our code search UI. Reported here https://sourcegraph.slack.com/archives/C05MHAP318B/p1706882647263079 I'm not able to...

@kamilkloch The motivation for this behavior is based on the (perhaps false?) assumption that fixtures should be independent of each other and it was therefore a nice simplification to remove...

Can we work around this issue by using an older version of JDK v11? This was working before.