-
Notifications
You must be signed in to change notification settings - Fork 38.2k
Closed
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugcandidateIssue identified as probable candidate for fixing in the next releaseIssue identified as probable candidate for fixing in the next releaseimportantIssue identified as high-priorityIssue identified as high-priorityverifiedVerification succeededVerification succeeded
Milestone
Description
- VSCode Version: 1.8.0
- OS Version: Mac OS X El Capitan
This issue seems to happen only for mounted drives (e.g. SSHFS a remote server to access files, and open the mounted folder with VSC).
Steps to Reproduce:
- Open Visual Studio Code with the folder of the mounted drive.
- Edit and save a file (unfortunately, I can I only get this to happen sporadically. Sometimes it works, sometimes it doesn't... and I can't seem to find a pattern for it)
- The following error messages show up:
"Failed to save 'examplefile.js': The content on disk is newer. Click on Compare to compare your version with the one on disk."
And then when I click "Compare":
"Unable to open 'examplefile.js (on disk) ↔ examplefile.js (in Visual Studio Code)': Could not resolve any model with provided uri.."
I hope this was helpful, and if there is currently any resolution to this, I would like to know. It has only been happening since I updated to 1.8.0. It has made VSC unusable for me on my current project (and I really love VSC, its been great).
EDIT: I included a couple of screenshots. It seems to happen with any type of files, but I gave this one as an example.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugcandidateIssue identified as probable candidate for fixing in the next releaseIssue identified as probable candidate for fixing in the next releaseimportantIssue identified as high-priorityIssue identified as high-priorityverifiedVerification succeededVerification succeeded

