Tslint stops working sometimes VS Code inside of network drive

Tslint plugin stops working sometimes VS Code inside of network drive.

I have used vscode-tslint for a while on Windows 10 inside of a network drive repository (mounted via sshfs). It has always worked with type checking and intellisense, though is sometimes a bit slow.

Upon switching to the vscode-typescript-tslint-plugin I can sometimes get it to work inside of a network drive, though it is unstable, and oftentimes stops working entirely. I’m not sure how to provide logs to debug, but with some direction I could do that.

[oneillsp96]

I am having the same experience locally. I thought it was just the autoFix on save feature, but I disabled that, and am still seeing the service run slow and occasionally just die, leaving me with an editor full of red squiggly errors that do not go away even after the problem is fixed (until a vscode restart). It seems to occur most often when restructuring TSX markup. For example, trying to wrap an existing div in another div. like it sees an open element, sees there is no closing element (since you haven’t typed it yet). But then when you add the closing </div>, it doesn’t recognize that the error is fixed, and sometimes stops working altogether requiring a vscode restart.

[manu-st]

Is there a way to add even more logging in the typescript-tslint-plugin to figure out where it is stuck? Or while finding a solution, have a quick way to restart the tslint engine without having to restart VS Code?