Alex Li

> I am having this for some time, and I thought it was only me (after opening #48611). Yeah, we have received a couple of developers' feedback from our community...

> The protocol between the Dart analysis server (DAS) and IDE is by design eventually consistent, meaning that there periods when IDE and results from DAS are inconsistent, but eventually...

I use the same project to test by switching between Flutter 2.10, Flutter 3, and the latest master of Flutter, it seems to be introduced by some commits between 2.10...

Done bisecting and the https://github.com/flutter/flutter/commit/2d186585136bae7ee64a7298e34cc3fedaccad8d is the first bad commit, which means the issue might be introduced between 24bf86f and 5bc905e: ``` 2d186585136bae7ee64a7298e34cc3fedaccad8d is the first bad commit commit 2d186585136bae7ee64a7298e34cc3fedaccad8d...

@scheglov Can we have a higher priority here? As @RobertV212 said, this is annoying when codes are involved with version controls, also it almost breaks the analysis in my project...

I think we can find a Dart project for this. When I was developing flutter_tools it also happened. I will provide feedback later.

> I tried to do a bunch of insert a line, undo, insert again, undo sequences as fast as I can in my IntelliJ, and it does happen, but extremely...

> OK, I can reproduce it sometimes. Great to hear that. Meanwhile should I do more bisecting since I'm trying to setup the SDK environment?

> I don't know. If my suspicion is right, there is no need to do bisecting anymore. Well since it is able to reproduce I think there's no need to.

Any news on this?