-
Notifications
You must be signed in to change notification settings - Fork 30.4k
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
Problems Panel Sticky Errors From Closed Files #61241
Comments
@mjbvz can you clarify is this is the expected behavior or a bug? |
@bpasero mjbvz doesn't want to answer so can you clarify if this the intended behavior or not? Persistent errors/warnings are bugging me very much, perhaps there's a configuration I overlooked to disable them? |
Duplicate of #59363 Will follow up there |
@mjbvz The issue you linked to me is specific to typescript, but I'm seeing the same problematic behavior with .json: ^ With having Settings closed. This is also an issue with any language. I believe this is not related to Maybe this issue should be reopened? @mjbvz |
Oh, I thought you pinged me because you were writing js/ts. Is this for any file type? What if you disable all extensions? |
@Astrantia Is it happening only for settings file or all files? For settings file what are the steps to reproduce... I am asking because I am not able to repro with settings file |
@sandy081 This has been happening to me for all files, but I don't know how to reproduce it yet. It just happens spontaneously after a long usage of vscode. |
@Astrantia It is hard to fix without able to repro. When it happens next time please check if there are any errors in the console (Use command Closing this as it can't be repro. |
I'm not sure why this occurs sometimes and doesn't other times. The problem I have is the following:
I don't want to see the warnings/errors from the previously closed files. Is this a bug or is there a setting for this that I've been unable to find?
@mjbvz
The text was updated successfully, but these errors were encountered: