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

File watching doesn't work between shared folders (parallels) #29607

Closed
joaomoreno opened this issue Jun 27, 2017 · 4 comments
Closed

File watching doesn't work between shared folders (parallels) #29607

joaomoreno opened this issue Jun 27, 2017 · 4 comments
Assignees
Labels
feature-request Request for new features or functionality file-watcher File watcher *out-of-scope Posted issue is not in scope of VS Code upstream Issue identified as 'upstream' component related (exists outside of VS Code)
Milestone

Comments

@joaomoreno
Copy link
Member

Testing #29478

I'm not getting file events for a Parallels shared folder from macOS to Linux 32 bits, independently of multi root. It doesn't seem to be a regression, since it fails on both the old and new file watchers.

@bpasero
Copy link
Member

bpasero commented Jun 27, 2017

@joaomoreno to be clear the events fail within Linux when changing files on mac or vice versa or actually both directions?

This may just be a limitation of the underlying native watcher infrastructure, not sure we can do anything about it.

@bpasero bpasero added bug Issue identified by VS Code Team member as probable bug file-watcher File watcher labels Jun 27, 2017
@joaomoreno
Copy link
Member Author

macOS is the host OS. Linux guest is the guest OS. Code is running inside the Linux guest OS.

@bpasero bpasero added this to the June 2017 milestone Jun 28, 2017
@bpasero bpasero changed the title File watching doesn't work in shared folder File watching doesn't work between shared folders (parallels) Jun 28, 2017
@bpasero bpasero removed their assignment Jun 28, 2017
@bpasero bpasero removed this from the June 2017 milestone Jun 28, 2017
@bpasero
Copy link
Member

bpasero commented Jun 28, 2017

I can reproduce with our old watcher for both macOS => Windows as well as Windows => macOS. I do not think this is critical and I do not think we can actually do something about it other than falling back to polling when we detect this (which I am not sure how to...).

@Tyriar Tyriar added this to the Backlog milestone Jun 28, 2017
@Tyriar Tyriar added feature-request Request for new features or functionality and removed bug Issue identified by VS Code Team member as probable bug labels Jun 28, 2017
@bpasero bpasero added the upstream Issue identified as 'upstream' component related (exists outside of VS Code) label Sep 11, 2018
@Tyriar Tyriar added the *out-of-scope Posted issue is not in scope of VS Code label Sep 12, 2018
@vscodebot
Copy link

vscodebot bot commented Sep 12, 2018

This iteration we focus on issue grooming. This issue is being closed to keep the number of issues in our inbox on a manageable level, we are closing issues that are not going to be addressed in the foreseeable future: We look at the number of votes the issue has received and the number of duplicate issues filed. More details here. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding and happy coding!

@vscodebot vscodebot bot closed this as completed Sep 12, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Request for new features or functionality file-watcher File watcher *out-of-scope Posted issue is not in scope of VS Code upstream Issue identified as 'upstream' component related (exists outside of VS Code)
Projects
None yet
Development

No branches or pull requests

3 participants