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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deleting a folder and undo from Finder is not retrieving the folder in VS Code #29766

Closed
sandy081 opened this issue Jun 28, 2017 · 6 comments
Closed
Assignees
Labels
author-verification-requested Issues potentially verifiable by issue author bug Issue identified by VS Code Team member as probable bug file-watcher File watcher macos Issues with VS Code on MAC/OS X verified Verification succeeded
Milestone

Comments

@sandy081
Copy link
Member

Testing #29478

  • Open a Folder in VS Code
  • Assume above folder has a sub folder say Sub Folder
  • Go to Finder and delete Sub Folder
  • Observe that it is removed from VS Code - 馃憤
  • Undo the action in Finder by cmd+z. Folder comes back in Finder

Expected folder to come back in VS Code but not.

@Tyriar Tyriar added bug Issue identified by VS Code Team member as probable bug file-watcher File watcher labels Jun 28, 2017
@Tyriar Tyriar added this to the July 2017 milestone Jun 28, 2017
@bpasero
Copy link
Member

bpasero commented Jun 29, 2017

It looks like the undo event causes a CHANGED event on the folder instead of an ADD event. There are no ADD events for the contents of the folder either. Marking as important (not for June though) because I think this is a pretty bad regression from e.g. Chokidar where this works properly.

Does not reproduce on Windows btw.

@bpasero bpasero added important Issue identified as high-priority workbench-multiroot Multi-root (multiple folders) issues labels Jun 29, 2017
@Tyriar Tyriar added the macos Issues with VS Code on MAC/OS X label Jun 29, 2017
@Tyriar
Copy link
Member

Tyriar commented Jul 21, 2017

It looks like this has been fixed:

screen shot 2017-07-21 at 7 05 15 am

@Tyriar Tyriar closed this as completed Jul 21, 2017
@bpasero
Copy link
Member

bpasero commented Jul 21, 2017

@Tyriar I am still getting it and I am not 100% sure the only change that got in meanwhile (Axosoft/nsfw#24) would have an impact.

I see it on macOS by just deleting a top level folder from the workspace and the undoing that. In the video below I use single folder workspace but nsfw is enabled via settings:

flicker_chrome58

Maybe worthwhile to report to NSFW? I can try to come up with a test case.

@bpasero
Copy link
Member

bpasero commented Jul 21, 2017

I opened: Axosoft/nsfw#31

If we are unlucky then maybe we need to add manual code to detect this case and convert a MODIFIED event on a folder that was previously DELETED as CREATED (and all the children inside).

@Tyriar Tyriar modified the milestones: July 2017, August 2017 Jul 31, 2017
@Tyriar Tyriar modified the milestones: Backlog, August 2017 Aug 25, 2017
@Tyriar Tyriar added upstream Issue identified as 'upstream' component related (exists outside of VS Code) and removed important Issue identified as high-priority labels Aug 25, 2017
@bpasero bpasero removed the workbench-multiroot Multi-root (multiple folders) issues label Nov 17, 2017
@Tyriar Tyriar added upstream-issue-linked This is an upstream issue that has been reported upstream and removed bug Issue identified by VS Code Team member as probable bug labels Oct 10, 2019
@bpasero
Copy link
Member

bpasero commented Sep 22, 2021

Somehow this started to work for me again. Can others try too? When you use insiders nowadays you can simply open a single folder and you will get nsfw as watcher.

@bpasero bpasero added info-needed Issue requires more information from poster and removed info-needed Issue requires more information from poster labels Sep 22, 2021
@bpasero
Copy link
Member

bpasero commented Sep 22, 2021

Hm nevermind, still seeing it, but not in all cases. This is super weird...

@bpasero bpasero assigned bpasero and unassigned Tyriar Oct 11, 2021
@bpasero bpasero added bug Issue identified by VS Code Team member as probable bug and removed upstream Issue identified as 'upstream' component related (exists outside of VS Code) upstream-issue-linked This is an upstream issue that has been reported upstream labels Oct 11, 2021
@bpasero bpasero modified the milestones: Backlog, October 2021 Oct 11, 2021
@bpasero bpasero closed this as completed Oct 11, 2021
@bpasero bpasero added the author-verification-requested Issues potentially verifiable by issue author label Oct 15, 2021
@sandy081 sandy081 added the verified Verification succeeded label Oct 27, 2021
@github-actions github-actions bot locked and limited conversation to collaborators Nov 25, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
author-verification-requested Issues potentially verifiable by issue author bug Issue identified by VS Code Team member as probable bug file-watcher File watcher macos Issues with VS Code on MAC/OS X verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

3 participants