Gunnar Wagenknecht

> Ok, so we should probably have some kind of check to determine if the file is a linked resource, and prefer the original file as opposed to the shortest...

@nicksnyder @srikrsna-buf I think the issue should be re-opened and some blurb should be added to the documentation. I ran into the error as well and it took me quite...

@fmeum Is my assumption wrong that `bazel run //:gazelle` should apply `go_env`? Because when I manually set it (`export GOPRIVATE=github.com/private`) Gazelle seems to work.

It looks like item 6 is still a problem even for `bazel build`. Any possibility that a global `~/.gitconfig` is ignored due to sandboxing? I found issue reports in Bazel...

> Any possibility that a global `~/.gitconfig` is ignored due to sandboxing? Not due to sandboxing but due to humans messing with action environment. In case anyone else hits this,...

We are struggling with the same issue. The import seems to be generated relative with a "random" path. Is there any doc/pointer on how the resolution is expected to work?

I think https://github.com/bazel-contrib/rules_nodejs/pull/3855 could be temporary fix, though. It works for our cross-platform rules_oci image building.

Yikes, it's likely going to anayze the entire mono-repo. There are a few performance issues with JDTLS that we don't see in Eclipse. When opened *inside* a workspace, the extension...

@tomasaschan Did you use the pre-release version or the latest release version? I noticed we haven't pushed a release to the stable channel in a while.

I released 1.4.0 this morning. That's the version you should use. The older one was definitely broken. Add this: ``` # collapse all targets into one Java project (for Maven...