Mike Fairhurst
f1c1dfacb7
This CL enables us to have different crash reporters that report to different backends, this will be useful if we report plugin errors to staging and server errors to prod. Currently doing this with server errors so that we can make the switch over to prod incrementally. For the time being, the staging backend will have our whole crash history, and continue to get new crashes. Reports and dashboards can switch over to the prod backend as we get enough history for those reports to be useful, and when we have switched everything over we can stop reporting to staging entirely. Change-Id: Ie29b4e05c89fd57faf1487a2c2eba3701fc319d0 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/145922 Reviewed-by: Devon Carew <devoncarew@google.com>
analysis_server
A long-running process that provides analysis results to other tools.
The analysis server is designed to provide on-going analysis of one or more code bases as those code bases are changing.
Using the server
The analysis server is not intended to be used stand-alone, and therefore does not have a human-friendly user interface.
Clients (typically tools, such as an editor) are expected to run the analysis
server in a separate process and communicate with it using a JSON protocol. The
original protocol is specified in the file analysis_server/doc/api.html
and (less complete) Language Server Protocol support is documented
in tool/lsp_spec/README.md.
Features and bugs
Please file feature requests and bugs at the issue tracker.