Tiago Quelhas

This is a duplicate of https://github.com/bazelbuild/bazel/issues/10075, note in particular the discussion starting from https://github.com/bazelbuild/bazel/issues/10075#issuecomment-546872111.

If you care about this, I think the next step would be to start a discussion with the [Remote Execution API working group](https://github.com/bazelbuild/remote-apis) to add protocol support for it.

I've just submitted 32b0f5a, which will cause non-symlink outputs created via `ctx.actions.symlink` (i.e., with a `target_file` parameter) to be materialized on the local filesystem as symlinks when `--remote_downloads_minimal` is enabled....

FYI, I'm going to backport this into 5.4.0 because I got a report of another user running into an issue related to this.

Created Google internal issue b/133453443.

Have you installed a JDK on your machine? See https://github.com/bazelbuild/bazel/issues/7304, which looks like a similar issue.

Sorry for the delay, importing it now.

Re-reading the discussion, I don't believe there's anything left to do here, but let me know if you think otherwise.

My previous comment was a little too optimistic. I do think there are use cases where accurate tracking of tree artifact contents is required, and this probably goes beyond empty...

Doing some back-of-the-napkin math, a digest cache with 50k entries (current default) should consume around 11MB, assuming compressed oops, average pathname length of 100 bytes, and hash length of 32...