Fabian Meumertzheim

As far as I can tell, Bazel will only do the following after sending the "BuildFinished" event: * send further BES messages advertising log files and the Starlark profile *...

The output path of the file won't be just `some_file.txt`, it will be a more complicated path starting with `bazel-out`. Could you try setting `args = ["$(execpath some_file.txt)"]`? That should...

I generally like this change, I just want to make sure we get the defaults right without breaking anyone too much. > Only when using Gazelle where one doesn't have...

`Rlocation` is not a good place for this as it's not necessarily true that all entries looked up via `repo/X` are actually in one physical directory on disk. Whether this...

@linzhp I think that we've seen this before, but I don't remember what caused it. Do you have an idea?

You can send a PR to add generally useful constraints to https://github.com/bazel-contrib/bazel-gazelle/blob/master/internal/bzlmod/default_gazelle_overrides.bzl.

I guess I should write that guide, but I still want to simplify the process before documenting it. @UebelAndre's commit is correct: If present, the manifest has to be preferred...

This is expected. Whether a runfiles library uses the directory or the manifest as a "backend" is considered an implementation detail, which is also why "features" offered by only one...

> I guess the "fix" here then is to make sure the manifest and directory based approaches are consistent by making sure the directory based approach cannot return a reference...

Bazel doesn't choose to, it has to (at least with the way it currently generates manifests and runfiles directories). There are situations in which the use of the runfiles directory...