You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ajhenri opened this issue
Dec 15, 2016
· 4 comments
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugcandidateIssue identified as probable candidate for fixing in the next releaseimportantIssue identified as high-priorityverifiedVerification succeeded
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.
The text was updated successfully, but these errors were encountered:
ajhenri
changed the title
Issue with saving files w/ mounted drive: "Could not resolve any model with provided uri"
Issue with saving files on mounted drive: "Could not resolve any model with provided uri"
Dec 15, 2016
Same issue here on OSX from a Remote ubuntu machine via samba share.
bpasero
added
bug
Issue identified by VS Code Team member as probable bug
candidate
Issue identified as probable candidate for fixing in the next release
important
Issue identified as high-priority
labels
Dec 16, 2016
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bugIssue identified by VS Code Team member as probable bugcandidateIssue identified as probable candidate for fixing in the next releaseimportantIssue identified as high-priorityverifiedVerification succeeded
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:
"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.
The text was updated successfully, but these errors were encountered: