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

Problems Panel Sticky Errors From Closed Files #61241

Closed
Astrantia opened this issue Oct 18, 2018 · 8 comments
Closed

Problems Panel Sticky Errors From Closed Files #61241

Astrantia opened this issue Oct 18, 2018 · 8 comments
Assignees
Labels
info-needed Issue requires more information from poster

Comments

@Astrantia
Copy link

I'm not sure why this occurs sometimes and doesn't other times. The problem I have is the following:

  1. Open any file which has warnings/errors showing up in Problems panel.
  2. Notice warnings/errors show up just fine.
  3. Close the file and/or open another file.
  4. Notice the errors from the previous file are still persistent in the Problems panel.

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

@vscodebot vscodebot bot added the error-list Problems view label Oct 18, 2018
@Astrantia
Copy link
Author

Astrantia commented Oct 20, 2018

@mjbvz can you clarify is this is the expected behavior or a bug?
it has been like this since I started using visual studio code, so im not sure

@Astrantia
Copy link
Author

@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?

@mjbvz
Copy link
Collaborator

mjbvz commented Oct 22, 2018

Duplicate of #59363

Will follow up there

@mjbvz mjbvz closed this as completed Oct 22, 2018
@mjbvz mjbvz self-assigned this Oct 22, 2018
@mjbvz mjbvz added the *duplicate Issue identified as a duplicate of another issue(s) label Oct 22, 2018
@Astrantia
Copy link
Author

Astrantia commented Oct 22, 2018

@mjbvz The issue you linked to me is specific to typescript, but I'm seeing the same problematic behavior with .json:
image

^ With having Settings closed.

This is also an issue with any language. I believe this is not related to tsc compilations, watches, and else.

Maybe this issue should be reopened? @mjbvz

@mjbvz mjbvz assigned sandy081 and unassigned mjbvz Oct 22, 2018
@mjbvz mjbvz removed the *duplicate Issue identified as a duplicate of another issue(s) label Oct 22, 2018
@mjbvz
Copy link
Collaborator

mjbvz commented Oct 22, 2018

Oh, I thought you pinged me because you were writing js/ts.

Is this for any file type? What if you disable all extensions?

@mjbvz mjbvz reopened this Oct 22, 2018
@sandy081
Copy link
Member

@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 sandy081 added info-needed Issue requires more information from poster and removed error-list Problems view labels Oct 23, 2018
@Astrantia
Copy link
Author

@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.

@sandy081
Copy link
Member

@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 Toggle Developer Tools).

Closing this as it can't be repro.

@vscodebot vscodebot bot locked and limited conversation to collaborators Dec 7, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
info-needed Issue requires more information from poster
Projects
None yet
Development

No branches or pull requests

3 participants