Skip to content
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

Merged

Conversation

traveltissues
Copy link
Contributor

closes #90

If there's interest in this change it can be signed off under the Codethink Ltd cla

@googlebot
Copy link

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 @googlebot I signed it!) and we'll verify it.


What to do if you already signed the CLA

Individual signers
Corporate signers

ℹ️ Googlers: Go here for more info.

@googlebot googlebot added the cla: no Pull requests whose authors are not covered by a CLA with Google. label Aug 15, 2019
@traveltissues traveltissues force-pushed the traveltissues/add-node-properties branch 2 times, most recently from b488979 to 323a322 Compare August 16, 2019 12:13
@googlebot
Copy link

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 @googlebot I consent. in this pull request.

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 cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

@traveltissues traveltissues force-pushed the traveltissues/add-node-properties branch from 323a322 to c6ee52e Compare August 16, 2019 12:23
@googlebot
Copy link

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

@googlebot googlebot added cla: yes Pull requests whose authors are covered by a CLA with Google. and removed cla: no Pull requests whose authors are not covered by a CLA with Google. labels Aug 16, 2019
@traveltissues traveltissues force-pushed the traveltissues/add-node-properties branch from c6ee52e to 5a8c9bd Compare September 23, 2019 13:42
@traveltissues traveltissues force-pushed the traveltissues/add-node-properties branch 3 times, most recently from 4580d97 to dbfd7b1 Compare October 2, 2019 13:12
Copy link
Contributor

@ola-rozenfeld ola-rozenfeld left a 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:

build/bazel/remote/execution/v2/remote_execution.proto Outdated Show resolved Hide resolved
build/bazel/remote/execution/v2/remote_execution.proto Outdated Show resolved Hide resolved
build/bazel/remote/execution/v2/remote_execution.proto Outdated Show resolved Hide resolved
build/bazel/remote/execution/v2/remote_execution.proto Outdated Show resolved Hide resolved
build/bazel/remote/execution/v2/remote_execution.proto Outdated Show resolved Hide resolved
build/bazel/remote/execution/v2/remote_execution.proto Outdated Show resolved Hide resolved
build/bazel/remote/execution/v2/remote_execution.proto Outdated Show resolved Hide resolved
@@ -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.
Copy link
Collaborator

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).

Copy link
Contributor Author

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?

@traveltissues traveltissues force-pushed the traveltissues/add-node-properties branch from dbfd7b1 to 89124bc Compare October 2, 2019 14:41
@traveltissues traveltissues force-pushed the traveltissues/add-node-properties branch 2 times, most recently from adad520 to bd5e0a1 Compare October 2, 2019 20:24
@bergsieker bergsieker merged commit 4f46bfd into bazelbuild:master Oct 8, 2019
@traveltissues
Copy link
Contributor Author

thanks @ola-rozenfeld @bergsieker

@traveltissues traveltissues deleted the traveltissues/add-node-properties branch October 8, 2019 14:53
@EdSchouten
Copy link
Collaborator

EdSchouten commented Oct 22, 2019

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,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This contains a typo.

@ola-rozenfeld
Copy link
Contributor

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?

/facepalm
You are 100% right, this should be in the Directory message! Will send a PR to fix.

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.

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.

@EdSchouten
Copy link
Collaborator

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.

@ola-rozenfeld
Copy link
Contributor

#102

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla: yes Pull requests whose authors are covered by a CLA with Google.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add properties for files
6 participants