Get desktop application:
View/edit binary Protocol Buffers messages
A TricorderService is a repository and code analysis service created for a specific language ecosystem that will be started and managed from within Warp. It helps Warp understand how an ecosystem works.
Returns whether the service is ready to take further requests. Since we are initializing tricorder services from within warp as separate processes, we need a signal to tell us that it is indeed ready.
(message has no fields)
(message has no fields)
Generates a Warp Signature for a given source and symbol. This is used during the Target Resolution phase, to understand how to build, test, or run a given target. The entirety of the repository is normally available to this rpc, but the signature is expected to correspond to a single path, be it a file or a directory. A list of dependencies will be provided to facilitate the analysis of code in case that paths to 3rd party dependencies are required. For example, in languages with preprocessors that require the inclusion of header files, this list of dependencies will include information about the paths where those header files may reside.
The root of the workspace that the Tricorder will be analyzing.
The path to the file that this signature corresponds to. This path will be relative to the `workspace_root`.
A list of dependencies known to be required to generate a signature for this file.
The root of the workspace that the Tricorder will be analyzing.
The root directory where this package is located.
The URL that this package was downloded from.
The name of the dependency to preprae.
Used in:
Used in:
The dependencies that were provided for signature generation.
A non-empty collection of requirements. These specify new dependencies that are needed to generate the signature.
Used in:
The root of the workspace that was analyzed.
The file that the signatures correspod to.
A non-empty collection of signatures for this file.
Used in:
repeated Requirement dependencies = 3;
Used in: