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

Vscode does not automatically refresh after external file changes #21252

Closed
raodoudou321 opened this issue Feb 23, 2017 · 10 comments
Closed

Vscode does not automatically refresh after external file changes #21252

raodoudou321 opened this issue Feb 23, 2017 · 10 comments
Assignees
Labels
file-watcher File watcher info-needed Issue requires more information from poster
Milestone

Comments

@raodoudou321
Copy link

  • VSCode Version: Code 1.9.1 (f9d0c68, 2017-02-09T00:26:45.394Z)
  • OS Version: Windows_NT ia32 6.1.7600
  • Extensions:
Extension Author Version
theme-onedark azemoh 0.4.3
path-intellisense christian-kohler 1.2.0
jquerysnippets donjayamanne 0.0.1
vscode-html-css ecmel 0.0.33
text-transform florianloch 0.1.0
beautify HookyQR 0.8.8
docthis joelday 0.4.0
vscode-icon-rotation krizzdewizz 1.0.3
vue liuji-jim 0.1.5
vuehelper oysun 0.1.0

Steps to Reproduce:

  1. I am in the outside editor on the VSCODE to open the file was modified, but VSCODE file does not carry out real-time refresh
@bpasero
Copy link
Member

bpasero commented Feb 23, 2017

@raodoudou321 is this reproducible all the time? is this a file from a workspace you opened or outside?

@bpasero bpasero added the info-needed Issue requires more information from poster label Feb 23, 2017
@bpasero bpasero added this to the Backlog milestone Feb 23, 2017
@raodoudou321
Copy link
Author

@bpasero
All files.
I am using ECLIPSE to modify the file, but VSCODE does not have real-time refresh (using other editors to modify VSCODE and no real-time refresh).

@bpasero
Copy link
Member

bpasero commented Feb 24, 2017

Please see if you can find any logged output that could help us find the source of the issue:

  • run code --verbose from the command line and attach the output
  • in Code select Help | Toggle Developer Tools and select the Console
  • attach any output you see in the Console you can find

Thanks!

@raodoudou321
Copy link
Author

@bpasero Hello.
I follow the prompts to catch the following BUG:
1.
workbench.main.js:138 [FileWatcher] Watcher failed to start after retrying for some time, giving up. Please report this as a bug report!

[FileWatcher] process error:

[FileWatcher] process error:

[FileWatcher] process error: 由于 Exception.ToString() 失败,因此无法打印异常字符串。

[FileWatcher] terminated unexpectedly (code: 3762504530, signal: null)

[FileWatcher] is restarted again...

@bpasero
Copy link
Member

bpasero commented Feb 24, 2017

@raodoudou321 awesome, this explains why changes do not show up but does not explain why the watcher does not work. Can you attach a screenshot how this error looks? I am missing some info here.

What kind of workspace are you opening and what is the envrionment (e.g. network share, samba share?)

@raodoudou321
Copy link
Author

@bpasero
errorPic.zip

@bpasero
Copy link
Member

bpasero commented Feb 24, 2017

@raodoudou321 can you try to run the file watcher from the command line? It is called CodeHelper.exe in C:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\services\files\node\watcher\win32 and just append the folder you are opening in VS Code as argument to the watcher.

@CNSKnight
Copy link

CNSKnight commented Jun 6, 2017

I see this commonly on linux versions (currently 1.12.2)

  • open script
  • git stash apply (overwriting script)
  • no change/prompt in vscode

have seen in console:

[IPC Library: Watcher] Error: watch /home/steeve/cfa-tmp/spot-app/.git/index.lock ENOSPC

@bpasero
Copy link
Member

bpasero commented Jun 7, 2017

@bpasero bpasero added the file-watcher File watcher label Jun 8, 2017
@edwin-hendriks
Copy link

Hi there. I have the same problem while opening a jetty.log file. It apparently seems to be a tricky thing to solve. But, why not simply add a refresh or reload command to VS code. That will help out me and probably others as well.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
file-watcher File watcher info-needed Issue requires more information from poster
Projects
None yet
Development

No branches or pull requests

5 participants