You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Gopls uses window/workDoneProgress/create to notify users of long running server-side operations and for errors that require user action to resolve (e.g. Error loading workspace...).
I found this notification doesn't get cleared if the server restarts before the work is done or the user addresses the root cause.
These orphaned notifications will not disappear without a complete reload of the window.
Considering this problem can occur when the language server crashes in the middle of work, I believe clearing this orphaned notification is client's responsibility. Having the vscode lsp client library handle this is ideal for us, but if it's not the case, we sill need to look into a way to track the notifications and clear them up before restarting the language server (maybe utilizing the new onProgress middleware).
The text was updated successfully, but these errors were encountered:
We need to update the language client library to 7.0.0 that already includes the fix.
Unfortunately, 7.0.0 requires vscode engine 1.52+ (the latest official version).
Gopls uses
window/workDoneProgress/create
to notify users of long running server-side operations and for errors that require user action to resolve (e.g. Error loading workspace...).I found this notification doesn't get cleared if the server restarts before the work is done or the user addresses the root cause.
These orphaned notifications will not disappear without a complete reload of the window.
Considering this problem can occur when the language server crashes in the middle of work, I believe clearing this orphaned notification is client's responsibility. Having the vscode lsp client library handle this is ideal for us, but if it's not the case, we sill need to look into a way to track the notifications and clear them up before restarting the language server (maybe utilizing the new onProgress middleware).
The text was updated successfully, but these errors were encountered: