Analyzer analyzes files in ignored directories/other projects if you open them, and doesn't stop when they're closed

Repro:

1. Open the Flutter repo in VSCode
2. Navigate to the definition of something in dart:ui or the Dart SDK (i.e. a file under the bin/cache/** folder)
3. Problems window starts showing analysis issues in that folder based on current analysis options, even though analysis_options.yaml excludes it.
4. Close the file (or even VSCode as a whole), but the problems still persist.

It seems to go away if I rm -rf ~/.dartServer with VSCode closed and then re-launch.

[DanTup]

BTW to repro it, do a Ctrl/Cmd + Click on String in any dart file. It will open up string.dart from the SDK, which doesn’t follow Flutter’s analysis rules. Once it’s there, it won’t disappear until you clear your .dartServer and restart VS code

Aha, right. I see now. I believe this is the issue described in a comment at https://github.com/dart-lang/sdk/issues/25551#issuecomment-418437599. However I don’t think it has its own issue, so I’ll open one for better visibility so it doesn’t get missed.

[dnfield]

I can kind of work around this by adding a filter to the problems window like !bin/cache/**, but it sztill suggests there’s a ton of problems even though they’re filtered out from view.