crt-31

Bump. This really should be addressed now that Bazel officially supports Windows. CRLF is what is expected by basically all Windows tools, and it is basically best practice to use...

Thanks, @vladmos for continuing this discussion. I tried the things you asked about on my Windows box: * checkout this repo with core.autocrlf=true: go files have CRLF * run gofmt:...

This ticket can probably be closed. SemanticDB support was added in #1508

This issue can probably be closed now. SemanticDB support was added in #1508

@crazyjat, I was looking at this... is it still an issue for you? If so, what version of rules_scala and bazel are you using? And what's in your thrift file?

bump. This is needed for Bazel's rules_scala to properly support Scala3. (see https://github.com/bazelbuild/rules_scala/pull/1545). Probably needed my many other tools too. (Quick look: I see some issues where JarArchive isn't being...

Try using --tool_java_runtime_version=remotejdk_17. That should be what the scala compiler is hosted on. For what gets used during run and test, use --java_runtime_version=remotejdk_17. (I think host_javabase and java_toolchain are both...

I don't believe rules_scala should depend on _experimental_ features. But I'd be fine if rules_scala supported multiplex and non-multiplex workers. As long as I can still run builds in a...

I'm not opposed to the setting necessarily, but for the use case the OP describes: My understanding is that IntelliJ is using [ bazel-bsp](https://github.com/JetBrains/bazel-bsp) to incorperate bazel into their IDE....

Path mapping is a "highly experimental" Bazel feature, and I don't believe rules_scala should depend on experimental features. If this path mapping can be optionally enabled, then that would be...