Luis Padron

@alanzeino Thanks for putting up this PR, we'd love the new rules being supported as well where I work. I found that the following diff on the `bazel` branch is...

Yeah that works and it's what we do today but it lacks a few things: - the argument cannot have the correct type, because the async function is not supported....

I'm also seeing something similar to this in Bazel 7 without BwtB: `11:01:10 ERROR: Foo/BUILD.bazel:11:15: Compiling Foo.c failed: unable to finalize action: Missing digest: / for bazel-out/ios_arm64-opt-ios-arm64-min12.0-applebin_ios-ST-/bin/path/to/Foo.d` Interestingly we're only...

@tjgq is this actually a feature request? It feels like a bug since this works just fine for us in Bazel 6

Thanks for the reply, yeah the error are slightly different but related cause of the .d files. FWIW we're using remote_download_outputs=all so I was expecting nothing to change here for...

Thanks for the suggestion we're testing out `--noexperimental_inmemory_dotd_files ` now

@tjgq So `--noexperimental_inmemory_dotd_files` does seem to work, at least we haven't hit this issue in a few iterations. Should I open a separate issue for that or is this known?

I filed https://github.com/bazelbuild/bazel/issues/22387 thanks!

yes that would be perfect thank you @keith. Any idea if theres a desire to merge that from the maintainers? We can keep this open and close it if that...

#567 solves this for us thanks Keith!