New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pub upgrade did not trigger analysis #17179
Comments
https://codereview.chromium.org/240003005/ r35132 Added Fixed label. |
Rolled back as https://codereview.chromium.org/252703004/ Added Triaged label. |
Another manifestation of this bug is that it causes confusing warnings of the form "Foo cannot be assigned to Foo". Here's a repro:
import 'package:analyzer/analyzer.dart';
import 'package:analyzer/analyzer.dart';
A similar effect can happen even without changing the pubspec, if the version of analyzer is upgraded on the server and the user reruns "pub get". The reason this happens is that after changing pubspec.yaml, the analyzer fails to notice that file1.dart and file2.dart are now referring to different versions of analyzer.dart than they were previously (and hence need to be reanalyzed). After file1.dart is trivially edited, the analyzer reanalyzes it and discovers that it is now referring to the AstNode from analyzer version 0.15.3. But it still (incorrectly) thinks file2.dart is still using the AstNode from analyzer version 0.15.1, so it reports the bogus warning. |
We decided this morning not to bother fixing this in the Java-based analyzer, since we are in the process of replacing that with he Dart-based analysis server. I'm working on the fix for the Dart-based analysis server. Set owner to @stereotype441. |
Removed this from the 1.6 milestone. |
Removed Oldschool-Milestone-1.6 label. |
Removed Area-Editor label. |
Added Analyzer-Server label. |
Cannot reproduce; assumed stale. |
Username: kasperl
I just ran 'pub upgrade' on a project which updated one of my dependencies. Then I started the project in Dartium, but unfortunately a constructor had changed so Dartium stopped with a NSM error. However, I didn't get any static warning in the editor before I chose 'Reanalyze sources'.
////////////////////////////////////////////////////////////////////////////////////
Editor: 1.2.0.dev_05_15 (2014-02-24)
OS: Mac OS X - x86_64 (10.9.2)
JVM: 1.6.0_65
projects: 1
open dart files: 1
auto-run pub: true
localhost resolves to: 127.0.0.1
mem max/total/free: 1996 / 266 / 162 MB
thread count: 31
index: 235202 relationships in 50083 keys in 260 sources
SDK installed: true
Dartium installed: true
The text was updated successfully, but these errors were encountered: