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

nodemon can't detect the change from windows to vagrant-docker #208

Closed
karousn opened this issue Jun 4, 2020 · 2 comments
Closed

nodemon can't detect the change from windows to vagrant-docker #208

karousn opened this issue Jun 4, 2020 · 2 comments

Comments

@karousn
Copy link

karousn commented Jun 4, 2020

Which version of Mutagen are you using (mutagen version)?

0.11.4

Which operating system (platform/version/architecture) are you using?

Windows 10 Pro

What is the issue that you're experiencing?

When i change a file on my host (i can see that my file changed in the vagrant guest) i should see nodemon refresh on my docker (in vagrant) log, using rsync i can see that but not with mutagen.

What are the steps to reproduce the issue?

use mutagen on vagrant-docker infrastructure and use nodemon to refresh node server after each change.

What is the expected result of these steps in the absence of the issue?

i should see nodemon refresh on my docker (in vagrant) log

What is the actual result?

nodemon doesn't refresh

@karousn karousn changed the title nodemon can't detect the change windows to vagrant-docker nodemon can't detect the change from windows to vagrant-docker Jun 4, 2020
@karousn
Copy link
Author

karousn commented Jun 8, 2020

After some test, i can confirm that i have refresh work but after some time of project start doesn't work any more so i must restart my mutagen project to see the refresh of nodemon again.

@xenoscopic
Copy link
Member

Thanks for the report on this, sorry for the slow reply. I'm fairly certain that this shares the same underlying cause as #163, namely the lack of detection of rename operations. There's an open Pull Request (#158) that I haven't had time to review/finish. I'll try to prioritize that since this is important. If you don't mind, I'll close this as a duplicate of #163 just to keep the issue tracker manageable, so I'd recommend subscribing to that and the PR for a resolution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants