Sam Gammon

that does sound like a major gain

with https://github.com/bazelbuild/bazel/pull/14724 it seems like progress is being made on this and may no longer require `LCOV_MERGER=true` (after some rules updates to adopt, presumably)

@LStAmour, @LouisStAmour, @cherryland - i am also building a chrome extension, among other things, in typescript/closure. thank you for this thread, it offers a ton of useful help @cherryland -...

@LouisStAmour food for thought... we had requested that `elemental2` include generated Java files from Chrome API externs. this would allow chrome extensions to be coded in J2CL. i would be...

@dgcoffman i saw you applied the changes that introduced Bazel 4 compatibility. we're on 4.0 and getting this error -- any ideas?

@ittaiz it seems to work fine on macOS for me in 2021, running Big Sur and Bazel 4.0.0.

how is it possible that coverage, python, and bazel don't work together, in the year of our lord 2020

forget i said anything about crates: https://doc.rust-lang.org/nightly/unstable-book/compiler-flags/source-based-code-coverage.html i've got a sample working locally outside of Bazel, which uses `-Zinstrument-coverage`/`grcov`/`lcov` to generate coverage data and merge with our canonical LCOV report,...

is it a typo, as `fortawesome`?

@rarous in our case we want to build against MDC sources, and allow rewriting in the lib and app . if i understand correctly this issue would help with that,...