Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tidy up and comment daemon CLI #8180
Tidy up and comment daemon CLI #8180
Changes from all commits
8f44edc
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Instead of documenting a limitation, I think we could make it work.
The point of this mode of operation is that we forward everything, so that should probably include informing the client about their trustedness correctly.
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 actually went with the first one for 3 reasons:
LocalStore
, for example, it will blindly returnTrusted
. So standard streams + non-RemoteStore
still means an invalidated client.So bottom line is I think this is a good idea, but it deserves is own follow-up PR.
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.
Also I remembered that the way it works today is that the trusting of operations in
processConnection
is based solely on this parameter, but the trusting status returned to the client already takesstore->isTrustedClient()
into account.That means in a chained daemon situation that even if an intermediate daemon trusts the the client (and doesn't block any request) the result of
store->isTrustedClient()
is still the intersection of the trust of each link in the chain.I actually think that might be good semantics: