This is an automated email from the ASF dual-hosted git repository.
juergbi pushed a change to branch juerg/re-proxy
in repository https://gitbox.apache.org/repos/asf/buildstream.git
omit d83682858 _sandboxremote.py: Use buildbox-casd as remote execution
proxy
omit 39c0a0883 casdprocessmanager.py: Add stubs for the Remote Execution API
add 3ba314afc _protos: Update protos from remote-apis
add 7544fb2f3 _protos: Update local_cas.proto from buildbox
add d988d5c50 casdprocessmanager.py: Add stubs for the Remote Execution API
add f4f16e3dd _sandboxremote.py: Use buildbox-casd as remote execution
proxy
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (d83682858)
\
N -- N -- N refs/heads/juerg/re-proxy (f4f16e3dd)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
.../build/bazel/remote/asset/v1/remote_asset.proto | 50 ++++
.../bazel/remote/asset/v1/remote_asset_pb2.py | 40 +--
.../remote/execution/v2/remote_execution.proto | 314 +++++++++++++++++++--
.../remote/execution/v2/remote_execution_pb2.py | 249 ++++++++--------
.../execution/v2/remote_execution_pb2_grpc.py | 119 +++++---
.../_protos/build/buildgrid/local_cas.proto | 23 ++
.../_protos/build/buildgrid/local_cas_pb2.py | 74 ++---
7 files changed, 632 insertions(+), 237 deletions(-)
