-
Notifications
You must be signed in to change notification settings - Fork 114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add NodeProperty message to filetype nodes #91
Add NodeProperty message to filetype nodes #91
Conversation
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please visit https://cla.developers.google.com/ to sign. Once you've signed (or fixed any issues), please reply here with What to do if you already signed the CLAIndividual signers
Corporate signers
ℹ️ Googlers: Go here for more info. |
b488979
to
323a322
Compare
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the ℹ️ Googlers: Go here for more info. |
323a322
to
c6ee52e
Compare
CLAs look good, thanks! ℹ️ Googlers: Go here for more info. |
c6ee52e
to
5a8c9bd
Compare
4580d97
to
dbfd7b1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, just a few naming nits:
@@ -412,6 +412,10 @@ message Action { | |||
// If true, then the `Action`'s result cannot be cached, and in-flight | |||
// requests for the same `Action` may not be merged. | |||
bool do_not_cache = 7; | |||
|
|||
// List of required supported [NodeProperty][build.bazel.remote.execution.v2.NodeProperty] | |||
// keys. If a property is not recognized the server returns INVALID_ARGUMENT. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we beef out this description a bit? In particular, I think the server should have leeway to interpret these properties how it sees fit. For example, some properties may be applicable to directories but not files (or vice-versa).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree the server is ultimately responsible for interpreting those properties but I'm not sure what you're requesting. Do you just want the comment here to make that more explicit?
dbfd7b1
to
89124bc
Compare
adad520
to
bd5e0a1
Compare
bd5e0a1
to
4b128a0
Compare
thanks @ola-rozenfeld @bergsieker |
How does one specify properties on the root directory of the input root? Wouldn't it have been smarter to place the properties inside the Directory message itself? I also wonder how this will impact the size of directory objects, considering that all of this (even names of keys) is done through strings. |
@@ -573,6 +583,9 @@ message Platform { | |||
// * The files, directories and symlinks in the directory must each be sorted | |||
// in lexicographical order by path. The path strings must be sorted by code | |||
// point, equivalently, by UTF-8 bytes. | |||
// * The [NodeProperties][build.bazel.remote.execution.v2.NodeProprty] of files, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This contains a typo.
/facepalm
Yeah, I suspect it will have a big impact, my hope basically is that the need for this will be a rare case, and that clients will use these only as needed. |
Then my hope is that we don't follow through on what is requested in #99. |
closes #90
If there's interest in this change it can be signed off under the Codethink Ltd cla