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

Folder decorations don't go away when file with problems is deleted #61919

Closed
roblourens opened this issue Oct 27, 2018 · 12 comments
Closed

Folder decorations don't go away when file with problems is deleted #61919

roblourens opened this issue Oct 27, 2018 · 12 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s)

Comments

@roblourens
Copy link
Member

roblourens commented Oct 27, 2018

  • Create empty folder
  • git init (This only reproes when a git repo is present)
  • Add a folder foo/
  • Add a file inside that folder test.ts
  • Type something like invalid syntax in test.ts so that it has TS errors
  • See that folder foo is highlighted red in the explorer
  • In the file explorer, delete foo test.ts
  • foo is still red!

image

Doesn't repro in 1.28

@jrieken jrieken added bug Issue identified by VS Code Team member as probable bug file-decorations info-needed Issue requires more information from poster and removed bug Issue identified by VS Code Team member as probable bug labels Oct 28, 2018
@jrieken
Copy link
Member

jrieken commented Oct 28, 2018

I am actually not able to reproduce... When deleting the file it takes a short while (1-2 sec) the folder decoration disappears...

@roblourens
Copy link
Member Author

I can still repro, but not every time. Can you give me some pointers on where to set breakpoints?

@jrieken
Copy link
Member

jrieken commented Oct 29, 2018

@roblourens
Copy link
Member Author

roblourens commented Oct 29, 2018

When it reproes, I see it call that only once after I delete test.ts. It's called as a result of the treeview refreshing. It seems to find out about the error decoration from the child.

When it doesn't repro, then I also see it called a few more times with this stack

FileDecorationsService.getDecoration (/Users/roblou/code/vscode/src/vs/workbench/services/decorations/browser/decorationsService.ts:401)
ResourceLabel.render (/Users/roblou/code/vscode/src/vs/workbench/browser/labels.ts:213)
ResourceLabel.onFileDecorationsChanges (/Users/roblou/code/vscode/src/vs/workbench/browser/labels.ts:112)
(anonymous function) (/Users/roblou/code/vscode/src/vs/base/common/event.ts:328)
Emitter.fire (/Users/roblou/code/vscode/src/vs/base/common/event.ts:145)
(anonymous function) (/Users/roblou/code/vscode/src/vs/base/common/event.ts:356)

@jrieken jrieken added this to the November 2018 milestone Oct 30, 2018
@vscodebot vscodebot bot closed this as completed Nov 6, 2018
@vscodebot
Copy link

vscodebot bot commented Nov 6, 2018

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!

@jrieken jrieken reopened this Nov 6, 2018
@jrieken jrieken removed the info-needed Issue requires more information from poster label Nov 6, 2018
jrieken added a commit that referenced this issue Nov 6, 2018
@jrieken
Copy link
Member

jrieken commented Nov 6, 2018

This is still a mystery. I have pushed a test that we emit an event for the parent folder when the decoration change for the child folder. Tho, it might be that the marker isn't actually removed. @roblourens when you see this, is the problems view empty or does it still show the error?

@roblourens
Copy link
Member Author

It's still in the problems view too.

@jrieken jrieken removed their assignment Nov 7, 2018
@jrieken
Copy link
Member

jrieken commented Nov 7, 2018

Ok, that makes it a TypeScript issue... Since the marker is still there (and bubbles) it will be shown on any parent folder. It must be removed from the marker service to be cleaned up in the UI

@mjbvz
Copy link
Collaborator

mjbvz commented Nov 7, 2018

Duplicate of #61919

@mjbvz mjbvz marked this as a duplicate of #61919 Nov 7, 2018
@mjbvz mjbvz closed this as completed Nov 7, 2018
@mjbvz mjbvz added the *duplicate Issue identified as a duplicate of another issue(s) label Nov 7, 2018
@roblourens roblourens reopened this Nov 7, 2018
@roblourens
Copy link
Member Author

That's this issue 🤦‍♂️

@mjbvz
Copy link
Collaborator

mjbvz commented Nov 7, 2018

Sorry, should be #61773

@roblourens Is there a (deleted from disk) file still open in your editor like in #58088?

@mjbvz mjbvz closed this as completed Nov 7, 2018
@roblourens
Copy link
Member Author

No

@mjbvz mjbvz removed this from the November 2018 milestone Dec 4, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators Dec 23, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

4 participants