search

rkostrzewski / vscode-monitor-file

An extension that allows monitoring files
MIT License
2 stars 0 forks source link

Doesn't work anymore #1

Closed nilskp closed 7 years ago

nilskp commented 7 years ago

No reloading.

nilskp commented 7 years ago

Nevermind, it does work, but there are sporadic cases of not.

rkostrzewski commented 7 years ago

Was it a delay of reloading (it might happen for various logging libraries which flush data from memory to disk to reduce I/O overhead) or was it completely not reloading even tough a file could be opened in a different editor? OS name & version will help in determining the issue. Thanks.

nilskp commented 7 years ago

I'm on Windows 10.

I still see this, to varying degrees. I'm not sure how reloading is determined, but I wonder if it's related to reading timestamps, perhaps something with differences between linux and windows and/or related to precision, i.e. millis or seconds.

nilskp commented 7 years ago

So, I just saw this again. Last log line shown has timestamp 2017-07-25 13:39:01.133, and then never updates again. Invoking F1 + Monitor File is necessary to refresh and shows the following log lines, the next immediate one having timestamp 2017-07-25 13:39:03.754. So, there's a 2+ second delay between those two lines, but that line (and all following) is never picked up.

nilskp commented 7 years ago

It's almost certainly some race condition, that seems to bring it into a state where it stops reacting. I'm surprised if I'm the only one seeing this.

nilskp commented 7 years ago

Appears to be resolved when I switched to 64-bit version of VSC.