-
Notifications
You must be signed in to change notification settings - Fork 307
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
Analysis server does not update problems/ linting errors over LiveShare #2094
Comments
Can you clarify exactly what your setup is. Are the changes being made on the host or client, and where are they not updating? Are they updating on the other machine? Also - could you check if there are any errors shown in the dev console (Help -> Toggle Developer Tools -> Console). Thanks! |
What do you mean by setup? |
Thanks, that's what I wasn't sure about :) @lostintangent before I dig too much into this, are there any known issues like this (sorry if you're not the right person to ask, but you assisted with a previous issue :-))? This seems like something the live sharing extension should be keeping synchronised, I can't think of what could go wrong in the language extension to cause this? |
I'm unable to reproduce this issue today. I started a session and clicked the "Try joining yourself" link which spawns a new VS Code, and the errors seem to be synced fine (though only those for the current file seem to show up on the client - I presume that's Live Share functionality). Can you still reproduce any issues here? |
You did a local session? I wouldn't say that that's guaranteed to be the same. I always get this issue. Even still now. I haven't tried in a few weeks, but I can't recall a time where I didn't have the issue |
I did. I figured it'd be the same since they're two separate VS Code instances and connecting via the URL, but I don't know if it has shortcuts. Can you give an example of exactly what you did so I can make sure when I try it across multiple machines I do the same thing? Thanks! |
This issue has been marked stale because it is tagged awaiting-info for 30 days with no activity. Remove the stale label or comment to prevent the issue being closed in 10 days. |
@DanTup I connected with another user. That's it. Multiple users over remote sessions with the same results. It would update rarely, most of the times, it would show old analysis errors and warnings so I'd have to ask the other user if there were any issues with the code. |
There's an open issue at microsoft/live-share#3509 about sync and performance issues. I don't think there's a lot that can be done in the Dart extension (at least without some guidance from Live-Share). The synchronisation of things like errors is entirely done by Live Share, so if they're out of sync between client/host, that seems like a Live Share bug. There are some perf issues when I'll close this as a dupe of that one (as we can't fix sync issues here), but I'm subscribed to that LiveShare issue, so if things come up that we can do in the Dart/Flutter extensions to improve performance etc., I'lll take a look. |
If I'm working on a project in Liveshare and fix a linting error, it doesn't disappear in the problems section. This is the output of Flutter doctor -v on the host machine
flutter doctor -v on the client machine:
The text was updated successfully, but these errors were encountered: