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

Improve VS Code when working with network drives #13665

Closed
4 of 6 tasks
bpasero opened this issue Oct 13, 2016 · 71 comments
Closed
4 of 6 tasks

Improve VS Code when working with network drives #13665

bpasero opened this issue Oct 13, 2016 · 71 comments
Assignees
Labels
debt Code quality issues file-io File I/O

Comments

@bpasero
Copy link
Member

bpasero commented Oct 13, 2016

Some issues impact users that try to run VS Code against slow network drives. Specifically:

@dogmatic69
Copy link

dogmatic69 commented Nov 15, 2016

we remove folders from the recent folders list when they do not seem to exist even though they are

Just had this happen, I did notice once the drive is reconnected and I open the folder manually all the open files I had were re-opened.

Edit: Closer inspection, these are files I had open at some point, but not what I had open last. Also did not maintain the order of the files opened.

@dogmatic69
Copy link

Another problem while using network drives is that the go to file ctrl+p is very slow, pretty much unusable.

@Sublime45
Copy link

Sublime45 commented Dec 2, 2016

This happens a lot while working on my computer (not a network hard drive).
To make things worse, it flushes any "undo history" I may have. So even if I go through the compare and accept changes, then I cannot undo any of the stuff.

It is starting to get a bit frustrating. You should at least add a setting to disable it.

Update: With the new update I can't even compare and save anymore. Now after I press the compare button I get a notification pop up that says Could not resolve any model with provided uri..
So now I have a lot of unsaved changes in my file and no way to save them.

@andrewdigitalchaosca
Copy link

This is happening very frequently to me as well, working on a network drive as well, every other save I get an error

@pmhoudry
Copy link

I got the same frequent error on a samba share via virtualbox host only network.

@bpasero
Copy link
Member Author

bpasero commented Jan 4, 2017

I pushed a fix for the annoying save error, happy for feedback in todays insider build.

@pmhoudry
Copy link

pmhoudry commented Jan 4, 2017 via email

@fegumi2003
Copy link

fegumi2003 commented Jan 10, 2017

Hi all - I've been using VS Code for a week. I'm getting this error 4 out 10 times I save the file. This happens specifically with files in a SharePoint.

When I click on compare it does show me the differences, but I can't push my version over the SP one.

@bpasero
Copy link
Member Author

bpasero commented Jan 10, 2017

@fegumi2003
Can you try to reproduce with our nightly insider builds? You can give our preview releases a try from: http://code.visualstudio.com/Download#insiders

@fegumi2003
Copy link

@bpasero I've been able to reproduce this using the insider version. What troubles me is that when I'm comparing the disk vs VS Code versions; discard or accept the changes does exactly the same (changes wiped out).

@bpasero
Copy link
Member Author

bpasero commented Jan 12, 2017

Ok thanks for trying, I think this needs another look then. What I fixed specifically was this error happens when you have a slow connection and manage to hit Ctrl+S multiple times without the first save actually returning. There might still be a bug that the mtime we get back after the save is not the same as the one on the server. Though still hard for me to understand how that can happen.

@rbtbar
Copy link

rbtbar commented Jan 26, 2017

Regarding the issue described as "we prevent saving when we think the contents on disk are newer":

It happens to me on a LOCAL drive too, when for instance a js beautifier is triggered in the background via monitoring script.

@bpasero
Copy link
Member Author

bpasero commented Jan 26, 2017

We fixed that one for upcoming 1.9 release.

@dogmatic69
Copy link

We fixed that one for upcoming 1.9 release.

Just local files?

@bpasero
Copy link
Member Author

bpasero commented Jan 26, 2017

Only one way to find out: http://code.visualstudio.com/Download#insiders

@AdamBJ
Copy link

AdamBJ commented Jul 6, 2017

@bpasero I'm still getting the sporadic saving error using version 1.13.1. Is the saving problem still an ongoing issue?

@bpasero
Copy link
Member Author

bpasero commented Jul 7, 2017

@AdamBJ what is your setup? and when you then compare files, is there a change to the remote file?

@AdamBJ
Copy link

AdamBJ commented Jul 7, 2017

I'm running Ubuntu 14.04 LTS as a virtual machine (via VMWare Workstation Player). The problem occurs when I've SSHed into a machine at my school and am working in one of the folders stored on the remote machine. As for the compare, the file on disk that is "newer" is the previous version of the file (i.e. the file minus any changes I've made since opening it).

One odd thing is that the problem doesn't seem to happen unless I'm on campus -- when I remote in from home I don't run into the error.

Let me know if you want more specific details on anything.

@se-m
Copy link

se-m commented Jul 11, 2017

Hi.
I prefer to mount network shares to folders.
e.g. mklink /d c:\proj \\server\share\foldername\
I was faced with a problem that if you open such folder the editor does not read its settings from .vscode at all. But with same share folder mounted as disk vscode works fine.

Is there a way to force vscode work with such folders as with a network drive? (maybe list of folders in user settings)

VsCode: 1.13.1
Windows 7

@samirotiv
Copy link

Intellisense & autocomplete don't work on the latest version with an SMB share.

@AdamBJ
Copy link

AdamBJ commented Jul 17, 2017

@bpasero The network drives save issue only seems to happen when I'm using my laptop which is running a 32-bit version of VS Code on Ubuntu 14.04 LTS.

UPDATE: When I run into this error, it seems to happen every other save. I love VS Code, but this save issue really is killing my productivity.

@RobIsHere
Copy link

#31667

@nguyenbathanh
Copy link

Any news?

@barberdt
Copy link

I can confirm @samirotiv's statement regarding autocomplete/intellisense not working with an SSHFS-mounted drive (on Mac). Similar to @nguyenbathanh, I'm curious what may be going on here. FWIW, the Path Intellisense extension seems to have no issue auto-completing paths with the same mounted drive. Thanks for any and all support!

@barberdt
Copy link

@bpasero is this still the proper place to bring up related issues or would a new issue make more sense? Happy to accommodate in whatever way makes the most sense. Thanks!

@ChadRidings
Copy link

Error: Failed to save 'syncSummary.txt': The content on disk is newer. Click on Compare to compare your version with the one on disk. (Settings Sync 2.8.2 on Dec 18, 2017)

@paulej
Copy link

paulej commented Dec 18, 2017

@ChadRidings Is that a Visual Studio Code issue or a Settings Sync issue (https://marketplace.visualstudio.com/items?itemName=Shan.code-settings-sync). That repo is https://github.com/shanalikhan/code-settings-sync/

@ChadRidings
Copy link

@paulej that is a good question. Yea I was looking at that repo yesterday as well. I've been taken down a rabbit hole where it's hard for me to determine if this is a problem with the application or a problem with the extension. I'll report back when I have a better idea.

@THCloud
Copy link

THCloud commented Jan 9, 2018

hi:I also have similar problem, I work with samba, open a folder on remote machine, (mine is Win, remote‘s is linux), and I wanna use shell on remote machine, can VSCode integrated teminal do it?

@danvc
Copy link

danvc commented Jan 9, 2018

@THCloud yes, you can, but I strongly recommend you to use the integrated terminal by SSH, I mean, connect to the server using SSH session.

@JalpeshVadgama
Copy link

Is there any update for this? As I m using it for Linux network drive and it's taking so much time compared to sublime text. Sublime text it's blazing fast.

@aimcom
Copy link

aimcom commented Mar 15, 2018

I have problems with sshfs mounted directories in Visual Studio Code on Ubuntu, too. Autocomplete and IntelliSense don't work properly.

So I've created a small workaround that I want to share: It worked for me to copy the sshfs directory locally, watch changes in this directory with inotifywait and copy them into the sshfs directory with a small shell script. This doesn't reflect changes on the remote filesystem but this is not important for me.

@johndugan
Copy link

Another Samba user here. I have two workflows - If I'm remote, I work with a Debian VM on Hyper-V (on my laptop). If I am at my desk, I work with a Debian VM on a VMware server that has better hardware.

In both cases, the Git features in code have very poor performance. Search is fairly performant though.

@yellow-sunshine
Copy link

yellow-sunshine commented Jul 22, 2018

I was trying to use VS Code with my git repository on a samba share. I am using mac and the samba share is on a remote Ubuntu 18.04 machine hosted on AWS. VS code and git would not work properly when I had my repository on a samba share but I had to get work done so I went ahead and started working without git. I was editing a file that was 2 days old, hours of work, and VS code hanged. When I reopened VS Code I was shocked to see my file on the server was blank. In fact, every file I had open at the time of the crash was blank. Now if git would have been workign properly I would not have lost data.

I guess it is back to Dreamweaver? Before I do somethign crazy like that, I am trying also a NFS. Git hub is still having issues. but I got 2 commits to go through. I am hacing trouble with more commits. It keeps telling me I can not write and index.lock file. Prob because VS code is unable to write to the network drive

@bpasero
Copy link
Member Author

bpasero commented Sep 10, 2018

I am closing this issue and ask people to file individual issues with reproducible steps after searching for duplicates. Having one large issue turns out to be not very helpful to manage.

@bpasero bpasero closed this as completed Sep 10, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators Oct 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
debt Code quality issues file-io File I/O
Projects
None yet
Development

No branches or pull requests