Konstantin Shcheglov
ada9cf43db
What happens in this case is that when we analyze this project with many (very small) files, we successfully index first declarations (on computing RESOLVED_UNIT3) and then RESOLVED_UNIT. But when we attempt to search, we ask for RESOLVED_UNIT, which is flushed. So, we compute it. In the process we compute RESOLVED_UNIT3, and the listener in _setupIndexInvalidation() indexes declarations, and overwrites the full index. There are several possible solutions, the simplest one is to not overwrite any existing index information while indexing declarations. R=brianwilkerson@google.com BUG= https://github.com/dart-lang/sdk/issues/26355 Review URL: https://codereview.chromium.org/1946353004 .
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
protocol is specified in the file analysis_server/doc/api.html.
Features and bugs
Please file feature requests and bugs at the issue tracker.