Comments (14)
All paths are relative to the exec root. You're right, the proto documentation should be fixed! Thank you!
from remote-apis.
All paths are relative to the exec root. You're right, the proto documentation should be fixed! Thank you!
This contradicts the previous clarification in #26
BuildStream, BuildGrid and BuildBarn (buildbarn/bb-remote-execution#18) follow the current proto documentation. I.e., they treat output paths as being relative to working_directory
and this change would break existing clients and servers.
from remote-apis.
Bleh! Sorry, Juerg! You're right. I have short memory :-)
Okay, then this should be fixed on the RBE side, and then the SDK...
from remote-apis.
So the conclusion is that the documentation is correct, our RBE implementation is wrong, and the SDK is (consequently) also wrong?
What would the migration path be for clients that rely on the previous behaviour (relative to exec root)?
from remote-apis.
I think that RBE will have to go through a phase where it will infer the client assumption based on where the actual outputs of the action are on the worker, before all its clients are fixed.
@bergsieker @EricBurnett
from remote-apis.
That sounds touchy. Could we be explicit with some sort of RBE-specific migration bit in the protos, clearly marked as RBE only?
from remote-apis.
I don't think it's that touchy. To my knowledge, RBE only has two clients using the feature. Importantly, Bazel is not one of them! So even though the simple migration plan is not formally well defined (what if an action creates two outputs with the same path, one relative to exec root and one relative to work-dir?) I suspect it will work well in practice. And we can quickly fix the two clients, so that the phase doesn't need to last more than a couple of weeks.
And if we do see cases of ambiguity, we can flag those and reevaluate...
@bergsieker and @EricBurnett -- thoughts?
from remote-apis.
I am working on such a client right now, and maybe the Chrome guys are as well. (Unless that's one of the ones you were aware of?)
How can you know whether an action creates outputs relative to the working dir and exec root? After the action completes, do you look for both of them, then adjust the output accordingly?
from remote-apis.
Yes, that is what I'm suggesting. As a temporary fix in RBE, look for both paths, take the one that exists, and log/surface any inconsistencies (such as both exist, or one output exists under working dir only while another under exec root only).
from remote-apis.
@ola-rozenfeld your proposal SGTM. Or depending on how launched these clients are (is the use of our mis-implementation in prod, or just in progress?), we could possibly just make a backwards-incompatible (breaking) change to RBE and accept a short period where these clients don't work, in the interest of getting to the right behaviour sooner.
In either case, I suggest we take this discussion to a RBE bug - sounds like the API is clearly well defined and we've simply mis-implemented it, which is a RBE issue and not a remote-apis issue :).
from remote-apis.
@EricBurnett , assuming discussion moved to an RBE bug, and no changes are needed here, can this be closed?
from remote-apis.
Yes, we've moved this to an internal bug. The published spec is clear, and we'll update our server to match.
from remote-apis.
Also see bazelbuild/bazel#13188; Bazel wasn't changed to match, although it's only assuming the old semantics if an experimental flag is set.
from remote-apis.
The code in Bazel that relied on this was added on Feb 13, 2020.
from remote-apis.
Related Issues (20)
- Compression: Further specify ByteStream WriteResponse committed_size field for compressed blobs HOT 1
- How does GetCapabilities() interact with authorization & unknown instance names? HOT 3
- Git tags for minor versions
- Non-Bazel Server Example HOT 3
- Replace message Tree with a topologically sorted varint delimited stream of Directory messages HOT 1
- REv3 idea: Make is_topologically_sorted the default, and eliminate tag bytes
- Let exit_code be better aligned with C/POSIX
- REv3 idea: Make use of digest_function in requests mandatory
- REv3: Use IPLD (CIDs, DAG-PB, etc.)
- Chyba
- CAS: Existence Caching in Intermediate Caches (user experience report) HOT 2
- Please tag REv2 2.1.0 2.2.0 [...] HOT 6
- API extension for Git hashes HOT 1
- Googleapis is outdated HOT 1
- Should we make a resolution to NOT have a v3? HOT 2
- Support compression with external dictionary HOT 6
- Add supported_max_cas_entry_size property to CacheCapabilities HOT 2
- Bazel version to use to run hooks/pre-commit unclear HOT 1
- REv3: Reduce asymmetry between O(n) output files and O(1) output directories HOT 2
- Platform standardization HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from remote-apis.