Dmitry Ivankov

docs: --nocache_test_results may actually not always be required for coverage

7

### Description of the bug: https://bazel.google.cn/docs/coverage?hl=en#remote-execution > Bazel will currently fail to create coverage information if tests have been cached previously. To work around this, --nocache_test_results can be set specifically...

%252C isn't un-escaped in spinnaker UI while %252c is

2

### Issue Summary: `https://spinnaker_hostname/#/applications/myapp/executions?pipeline=Deploy%20something%252C%20otherthing` Resolves to `PIPELINE: Deploy something%2C otherthing` while `https://spinnaker_hostname/#/applications/myapp/executions?pipeline=Deploy%20something%252c%20otherthing` Resolves to `PIPELINE: Deploy something, otherthing` One issue is that double-escaping is needed for comma `,` but not...

false-positive trigger on java17record.equals(null)

7

- [X] If you think you found a bug, please include a code sample that reproduces the problem. A test case that reproduces the issue is preferred. A stack trace...

json output converts numbers to strings

1

```sh # roundtrip works $ echo "a: 1e+9" | yq -Y . a: 1e+9 # json output quotes the number $ echo "a: 1e+9" | yq . { "a": "1e+9"...

use the released binary of protoc instead of compiling it from source

10

Similar to https://github.com/bazelbuild/rules_proto/issues/35 it would be nice for some users to save time on compiling protoc https://github.com/grpc/grpc-java/blob/master/compiler/BUILD.bazel#L14 protoc plugin depends on "@com_google_protobuf//:protoc_lib" which is a cc_library so may be not...

Cyclic dependency error with multi-classifier POMs

8

Importing `io.netty:netty-tcnative-boringssl-static:2.0.52.Final` makes bazel complain about cyclic error ```console $ bazel build @maven//:io_netty_netty_tcnative_boringssl_static .../external/maven/BUILD:84:11: in jvm_import rule @maven//:io_netty_netty_tcnative_boringssl_static_windows_x86_64: cycle in dependency graph: @maven//:io_netty_netty_tcnative_boringssl_static (d5a9994f7dbed333fedf2517edff904e2ccf8dfa4714a908e2c4920ae526e339) .-> @maven//:io_netty_netty_tcnative_boringssl_static_windows_x86_64 (d5a9994f7dbed333fedf2517edff904e2ccf8dfa4714a908e2c4920ae526e339) | @maven//:io_netty_netty_tcnative_boringssl_static_linux_x86_64 (d5a9994f7dbed333fedf2517edff904e2ccf8dfa4714a908e2c4920ae526e339)...

Input has currently only includes artifacts, but should include - artifacts - excluded_artifacts - version_conflict_policy - repositories - fail_on_missing_checksum - fetch_javadoc & fetch_sources - coursier version - (?) override_targets keys...

@unpinned_maven//:pin fails on malformed maven_install.json

3

```sh $ echo garbage > maven_install.json $ bazel run @unpinned_maven//:pin ..rules_jvm_external/third_party/bazel_json/lib/json_parser.bzl:672:18: JSON parsing failed. Could not parse the input: ERROR: An error occurred during the fetch of repository 'maven': Failed...

Seen javadoc process consuming lots of cpu&mem, also just a matter of being able to customize what's exported. Disabling should disable not only publishing but also building sources/javadocs.

Bazel 5.1.1 with openjdk17 server

6

### Description of the bug: If using openjdk17 as bazel server runtime some actions may fail ``` java.lang.ExceptionInInitializerError at com.google.devtools.build.lib.actions.ParameterFile.writeContent(ParameterFile.java:118) at com.google.devtools.build.lib.actions.ParameterFile.writeParameterFile(ParameterFile.java:111) at com.google.devtools.build.lib.analysis.actions.ParameterFileWriteAction$ParamFileWriter.writeOutputFile(ParameterFileWriteAction.java:170) at com.google.devtools.build.lib.exec.FileWriteStrategy.beginWriteOutputToFile(FileWriteStrategy.java:58) at com.google.devtools.build.lib.analysis.actions.FileWriteActionContext.beginWriteOutputToFile(FileWriteActionContext.java:49) at com.google.devtools.build.lib.analysis.actions.AbstractFileWriteAction.beginExecution(AbstractFileWriteAction.java:66)...