Fabian Meumertzheim
Fabian Meumertzheim
Sent https://github.com/buildbuddy-io/buildbuddy/pull/7787 to make an exception for Monaco. Customers that don't want `unsafe-inline` in styles can disable or decline to use the `/code` route.
I talked to Tyler and confirmed that warnings in dev can't cause releases to be rolled back, but I will monitor this for a while before we enable it in...
It's good for Go too and debugging also works. CLion also got pretty good with Bazel.
Have you tried running a build with `--keep_going`? That gives you all findings without failing the build immediately. Given how often warnings end up being ignored and just add to...
CC @jayconrod Through the `go_deps` extension, Gazelle is aware of all external Go repositories and could be configured to read a well-known file under them to extract directives out. This...
Since the guidance is that canonical repo names should not be hardcoded, stable paths require an additional layer of indirection anyway. I created [bazel_env.bzl](https://github.com/buildbuddy-io/bazel_env.bzl) specifically for this purpose. Its example...
bazel_env.bzl doesn't require direnv for its `toolchains`, just for `tools`. I should probably clarify that in the docs, but it does simply create a stable path without any external tool...
The API for creating and adding module maps is private, so the only thing you could try now is to split up the `CcInfo`: Populate the linking context from your...
Instead of an incompatible attribute on repo rules and module extensions, it may be possible to temporarily make the new toolchain types `label_flag`s that by default point to the old...
@mattyclarkson I think we (at least I) missed the interaction with `unsafe`. Rereading the Go thread on this, `purego` disables: * ASM, which may require a C toolchain (not entirely...