Comments (3)
The intersection between remote-apis (which is technically independent of Bazel, despite being hosted there), Bazel, and support tooling has always been tricky. We definitely shouldn't have Bazel-specific logic in this repository. That likely leads to...tools_remote being a wrapper that glues together Bazel-specific log parsing with this SDK? But I think you were just referred away from tools_remote...
from remote-apis-sdks.
Indeed, tools_remote appears to be dead now. Turning this repo into a suitable base for solving this puzzle would be reasonable.
Alternatively, standardising RemoteExecutionLog would also be reasonable, it's not very strongly tied to bazel, and any remote execution client could produce something similar.
I'm not sure what's the most correct direction here.
from remote-apis-sdks.
Right, the intention was that this repository would be the generic remote client solution that subsumes everything that tools_remote was, except for parts that are entirely Bazel-specific, e.g. help debugging Bazel invocations -- those would be left with tools_remote. And we always thought that RemoteExecutionLog falls in that category.
You have a good point on RemoteExecutionLog being potentially standardizable... but for now, it is a part of Bazel, and defined there. Changing that would not be easy.
Would using tools_remote for Bazel-specific debugging, and using this repository for everything else work for you?
from remote-apis-sdks.
Related Issues (20)
- Support resumable uploads HOT 1
- implement resumable uploads HOT 1
- implement a unified uploader
- implement a unified downloader
- implement upload/download cancellation
- Symlinks to inputs are incorrectly rejected HOT 3
- Output paths should be relative to the working directory HOT 1
- Remove deleted api `grpc.WithBalancerName` HOT 2
- Support node properties in the remote tool HOT 1
- test failing at master (Mac)
- ByteStream `resource_name` is incorrect if the instance name is empty HOT 2
- go/pkg/balancer uses experimental gRPC APIs HOT 15
- Bazel and Go builds have inconsistent dependencies
- Allow clients to provide InputDigests to avoid unnecessary transfer HOT 2
- Add PlatformProperties to client.Action HOT 3
- Only deduplicate currently uploading task, rather than all uploaded task when upload unified HOT 3
- Support credentialhelper in remotetool HOT 2
- Is it possible to use context.WithTimeoutCause in Client.CallWithTimeout? HOT 2
- ActionDg shouldnot related with DoNotCache option HOT 2
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-sdks.