Dmitry Ivankov

There are no steps to reproduce documentation issues, sorry

Docs say that using `--nocache_test_results` is needed to get test coverage and that test coverage can't be cached. But actually running `bazel coverage` without `--nocache_test_results` can produce coverage output and...

`gazelle_dependencies` adds a lot of `go_repository` which is unfortunate (they are only needed to build gazelle I think, not to expose as a library?), but luckily they are wrapped in...

There is a workaround - configure both netrc and default coursier location, like ~/.config/coursier/credentials.properties But very nice to have single source of truth :+1: Seems to be safe to add...

> Downloading https://releases.bazel.build/1.0.1/release/bazel-1.0.1-linux-x86_64 could be that read_netrc isn't available in bazel 1.0.1

you can also try with ```sh bazel run --java_toolchain=@bazel_tools//tools/jdk:toolchain_java8 --define "maven_repo=file://$HOME/.m2/repository" //multiplication:mul.publish ```

Workaround of deleting maven_install.json and remove maven_install_json= from WORKSPACE, rerun pin command, add back maven_install_json= to WORKSPACE was working for me.

Another useful thing could be setting `-merge` git attribute https://git-scm.com/docs/gitattributes#_performing_a_three_way_merge on `maven_install.json` to avoid conflict markers but keeping conflicted status

Workaround is to manually fetch cyclic dependencies and override them, like so ```python override_targets = { "io.netty:netty-tcnative-boringssl-static": "//workaround:io_netty_netty_tcnative_boringssl_static", "io.netty:netty-tcnative-boringssl-static:osx-x86_64": "//workaround:io_netty_netty_tcnative_boringssl_static_osx_x86_64", "io.netty:netty-tcnative-boringssl-static:osx-aarch_64": "//workaround:io_netty_netty_tcnative_boringssl_static_osx_aarch_64", "io.netty:netty-tcnative-boringssl-static:windows-x86_64": "//workaround:io_netty_netty_tcnative_boringssl_static_windows_x86_64", "io.netty:netty-tcnative-boringssl-static:linux-x86_64": "//workaround:io_netty_netty_tcnative_boringssl_static_linux_x86_64", "io.netty:netty-tcnative-boringssl-static:linux-aarch_64": "//workaround:io_netty_netty_tcnative_boringssl_static_linux_aarch_64", }, ```...

Unfortunately that's not a simple workaround. 1) find dependencies that form a cycle (`io.netty:netty-tcnative-boringssl-static*` in this case) 2) copy their definitions to a new BUILD file (would look similar to...