Mike Fairhurst
eff4807eef
Report it as a silent exception. This way it will show up in log files and (in the future) over crash reporting (since we haven't solved the underlying cause), but *not* to users, because it currently appears to be harmless. In the future we should consider a "logged-only" type of exception, once we are confident this isn't causing secondary issues, if we don't intend to or think we are able to solve this at a deeper level. Change-Id: I2ee339718fbd6e7c684ccc42718fbb57742f2dd7 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/134467 Reviewed-by: Paul Berry <paulberry@google.com> Commit-Queue: Mike Fairhurst <mfairhurst@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.