kbfs
kbfs copied to clipboard
keybase
Visual Studio Code not saving files properly
Trying to write a .txt file in my public folder,
I get the following error. I can safely open files from Explorer or other programs, I can save in Notepad.
Keybase GUI Version: 1.0.38-20171220134904+a7fe25d
Hi @Tenrys, I think we need a bit more context. Have you installed the file system drivers for Windows via the Folder tab in the Keybase GUI? Do you have a K:\ drive? Are you trying to write directly to K:\public (which won't work) or to your actual public folder (K:\public\tenrys)?
If you still think you're doing everything right, please run keybase log send from the terminal and let us know the log ID, and we'll take a look. Thanks.
Thanks. You get that error above when you are trying to save a .txt file using Visual Studio Code? Can you share the name of the txt file you tried to create, so I can look for it in the log? (If you don't want to share the name publicly, feel free to chat with me on Keybase, username strib.)
The current file name is test.txt. I tried to save it under that name and it did not work either. It is created but I cannot save it with Visual Studio Code if I make changes to it using that.
Are you running it in cygwin or WSL or something that might not have access to the k:\ drive? I don't think KBFS works nicely in those environments.
Not that I know? Not sure what WSL is, but rings a bell. I don't know how I would run VS Code in a specific environment? (nevermind, that's the Linux subsystem. I don't think I am?)
WSL is "Windows subsystem for Linux". I don't have experience with it, but I'd guess if you were using it, you'd know it.
Sorry I don't have a Windows system available to test, and I'm out of ideas. It seems like VSC can't see the K:\ drive at all for some reason. @zanderz @taruti any ideas?
I do have WSL installed but I rarely use it, don't know how I would have made VSCode use it.
Logs show mounting K: without errors. I just double checked that I can write new files with visual studio code on windows. Maybe also include the exact time so we can narrow down the logs we're looking for?
Sent another log. 09161961d48cb1c4489f441c
I don't know how to check them or the time.
Suspect conflicting drivers causing K: to be hidden, even though the mount was succesfull.
@Tenrys are you running any AV/backup/filesystem software that could be causing conflicts?
I do have WSL installed but I rarely use it, don't know how I would have made VSCode use it.
bash-prompt$ code test.txt
It will open test.txt in VSCode.
@Tenrys What I mean by exact time is to reproduce your problem, note the exact time you experienced it, and then send a log, along with a mention of what time you noted.