Tiago Quelhas

For local execution, I think the rough outline of "keep a map of futures for in-flight executions, resolve the future on action upload, block on the future when downloading an...

In your initial message, it looks like you ran an incremental build where the output tree was determined to be already up to date, so nothing actually needed to run...

The issue here is that, when building without the bytes, we create the symlink before the file it points to exists (it will be downloaded later if the symlink is...

Another case where we get in trouble with the path representation mismatch between the host and exec platforms is https://github.com/bazelbuild/bazel/issues/19208. As noted there, the hard part of fixing this issue...

@calebzulawski By "doesn't work", do you mean the credential helper never gets called? Or does it get called, but the credentials aren't passed along? What does your `--credential_helper` flag look...

Marking untriaged to surface it again at our next bug triage meeting.

The worker API and Java handler implementation have been moved to https://github.com/bazelbuild/bazel-worker-api.

> While adding more tests, I noticed that there is a pathological case that the new representation currently doesn't handle: If multiple artifacts at canonical locations collide, then the last...

I'm making the following changes on import: - Use new field ID for `InputSet.input_ids` and `Output.output_id` instead of reusing an existing ID (makes it easier to write a polyglot tool,...

Manual cherry-pick in https://github.com/bazelbuild/bazel/pull/23525