Fabian Meumertzheim

@sgowroji This sounds more like an issue for Team-Local-Exec as it isn't language-specific, but related to sandboxing in general. I mentioned @oquenchil since he was involved in the flag "flip".

@iancha1992 This may need to be picked into a 7.0.2 depending on assessed severity.

@oquenchil The 7.0.2 release has already happened, so there is no risk of blocking it. :⁠-⁠)

@atavakoliyext Either looks good, although I would prefer this if it works: ```diff diff --git a/cmd/generate_repo_config/generate_repo_config.go b/cmd/generate_repo_config/generate_repo_config.go index f573fa2..79d90cc 100644 --- a/cmd/generate_repo_config/generate_repo_config.go +++ b/cmd/generate_repo_config/generate_repo_config.go @@ -141,7 +141,7 @@ func generateRepoConfig(configDest,...

@jayconrod Would you be available to give this a final look? I'm not too familiar with this part of the code, but can look into it if you are busy.

You have to update rules_java past a version with a fix for this bug, but you don't need to load any symbols from it. Just adding a `bazel_dep` for it...

You can use the `build_flags` and `test_flags` fields in `presubmit.yaml` to do what you would otherwise do in `.bazelrc`. Could you try that? Since any flag needed here is something...

> I've encountered pretty significant problems with bzlmod as well as issues trying to get listed on the registry here. As such, my organization is holding off on bzlmod generally...

The processes are still more manual than they could be, just because automation is hard to get right in this setting (especially considering security implications). It's intentional that the very...

`--nobuild` may be appealing here. Most bzlmod-specific issues and changes to the Bazel interface of the module will probably be caught in the analysis phase. That plus a small real...