So I decided to give VScode + RA a try and it felt really great compared to VSCode + RLS for
rustc but there was an issue which made RA unusable...
...You see I used a Windows 10 laptop for VSCode + RA but the files I edit are on a mapped network share through samba on an Ubuntu Server.
Strangely, when I use RA on VSCode with this setup the files become unreachable on VSCode but also via File Explorer on Windows itself. If I then close VSCode the issue disappears and I can use the mapped share again through File Explorer.
This setup has worked fine using VSCode + the RLS extension...
Maybe this is a latency issue and RA is maybe constantly checking files? But it seems strange that this should be an issue since the server is in the local network and connected with 1gbps cat6.. maybe it's a samba issue? I'm trying to install RA on VSCode remote to see if I can get rid of the issue that way...
So I tried sshfs instead and the issue just went away seemingly
So this might be a samba issue indeed
It seems like notify falls back to polling on samba: https://github.com/passcod/notify/issues/64
@matklad ah; should I/you file an issue somewhere (RA repo, notify... (tho you know the notify stuff better))
I'd say the issue won't be too actionable, because we are in the "we'll rewrite this anyway soon" state. I think we need to wait and see how notify story unfolds: they are in the process of big rewrite which might completely change the set of bugs
Ah; I'll use sshfs for now then :slight_smile: