Skip to content
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

[bug] Sync problem #212

Open
Songggggr opened this issue Jun 22, 2024 · 7 comments
Open

[bug] Sync problem #212

Songggggr opened this issue Jun 22, 2024 · 7 comments

Comments

@Songggggr
Copy link

Songggggr commented Jun 22, 2024

If set it, error not sync, even if it is fixed

"extensions.experimental.affinity": {
    "golang.go": 2
  }

image

@usernamehw
Copy link
Owner

I don't use Go.

If extension works fine but stops with "extensions.experimental.affinity" - then file an issue with VSCode repo.

@jonlepage
Copy link

jonlepage commented Jun 22, 2024

I don't use Go.

If extension works fine but stops with "extensions.experimental.affinity" - then file an issue with VSCode repo.

hi,
I don't use Go (TS), but I've also noticed several serious issues these past few days.

With the last update of VSCode and yours plugin, it feels like everything is broken.
I'm experiencing several minutes of latency between error inline messages.
Switching between two tabs instantly fixes the issue, but it's quite disruptive to have to switch tabs after each fix!

Moreover, I've wasted several minutes on a problem that was already solved before understand the issue .

I've tried several configurations in Error Lens: Delay Mode such as Debounce, old, new, but they're all broken at different levels!
I hope the VSCode team can guide you on this issue.
If you open a issue plz share i will got vote for bring this to priority !

I haven't been able to identify a triggering factor for this behavior, unfortunately.
Sorry to ne able to help you more.

@usernamehw
Copy link
Owner

With the last update of VSCode and yours plugin

This doesn't help that much. What works?

Ext ver / VSCode ver 1.89.1 1.90.2
v?.??.?
v3.18.0
v3.20.0

@jonlepage
Copy link

jonlepage commented Jun 23, 2024

Oki np, I'll will just wait a few week for Microsoft to fix the outstanding issues from the last update, there were some stability issues, including one I reported.
microsoft/vscode#214496

If there's no more information by ~ next week or more users with same issue, I'll will try take a day to try to understand where the "error-len" latency problem is coming from on my side !
I have very few plugins, but I don't really have a suitable environment for debugging VSCode extensions or collecting extensions data and with addition , I'm overloaded with a big project, so it's hard to take my focus off it for now.

@jonlepage
Copy link

@usernamehw I took a few minutes to make a video to clearly demonstrate the problem: Scrolling, saving, or triggering ESLint formatting does not update the error message.
Only switching to a different tab or waiting about 30 to 40 seconds will update the message.
This problem also occurs randomly, e.g. about 1/5 when i edit code.
some time it fast and instantly, sometime it juste idle !
It's very difficult to understand why !


ca3rfagaf3a3fg.webm

if you have any theory or want me testing fast setting, i take it !

@jonlepage
Copy link

jonlepage commented Jun 24, 2024

update more info:

  • I disabled all the extensions and reactivated each one to see if it was an extension causing the issue:

Unfortunately, the problem persisted.

  • Then, I disabled all my VSCode settings in groups and reactivated each one to check if it was a setting causing the issue:
    Problem was fixed ! it was maybe a setting ?
    After reactivate all one by one, the clues led me to "typescript.tsserver.experimental.enableProjectDiagnostics": true, which allows scanning all open files at start vscode.
    However, since yesterday, after reactivating all the exact same settings, I no longer have this latency issue!!!
    everything responds in ~500ms as expected !

I don't understand it anymore!
Could the deactivation and reactivation of settings have fixed something in VSCode??
Or maybe I closed a file that contained code that was driving vscode-error-lens crazy?
i have more than 400 files and some files have weird template string and emoji !?
It's hard to say at this stage!

I will keep updated the issue, but my theory is that perhaps by activating "typescript.tsserver.experimental.enableProjectDiagnostics": true,, i have a specific file in the project workspace was breaking vscode-error-lens?
I haven't been able to reproduce this issue, but if it happens again in the coming weeks, I'll have more information to understand this behavior.

@vdawg-git
Copy link

vdawg-git commented Jun 26, 2024

I also have high latency problems now with Typescript.

Could be a TS problem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants