-
Notifications
You must be signed in to change notification settings - Fork 30k
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
Google Drive: Files in explorer are wrongly assumed to be directories #69333
Comments
I cannot open the video. What does looping mean? |
When I click on the file, inside the tab "Open Editor", the file appears, disappears, appears, disappears, etc... I think it's linked to the g:\ partition, created by Google Drive File Stream. |
Please see if you can find any logged output that could help us find the source of the issue:
Thanks! |
@LeNouveau thanks I can see what is going on but I do not have an understanding why this happens:
@isidorn would it be possible to get a new method from explorer service to either:
@LeNouveau could you try to use node.js to stat the path and see if the stat also tells it is a folder? |
@bpasero if you just call |
@isidorn that is not what I see, I do this: Steps:
|
Already on Insider.
Version: 1.32.0-insider (system setup)
Commit: 804373a
Date: 2019-03-01T18:22:35.336Z
Electron: 3.1.3
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Windows_NT x64 10.0.17763
Still have the problem.
Le ven. 1 mars 2019 à 15:47, Benjamin Pasero <[email protected]> a
écrit :
… Can you try to reproduce with our nightly insider builds? You can give our
preview releases a try from: https://code.visualstudio.com/insiders/
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#69333 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADgBIR0P6AZEGra2A0DB7ebDuEGuOjHvks5vST1xgaJpZM4bPZqd>
.
|
@LeNouveau could you try to use node.js to stat the path and see if the stat also tells it is a folder? |
Is it what you expected ?
fs.statSync("Simple gsheet file.gsheet")
Stats {
dev: 428019990,
mode: 33206,
nlink: 0,
uid: 0,
gid: 0,
rdev: 0,
blksize: undefined,
ino: 0,
size: 1,
blocks: undefined,
atimeMs: 1551282892782,
mtimeMs: 1551282892782,
ctimeMs: 1551282892782,
birthtimeMs: 1551282856784,
atime: 2019-02-27T15:54:52.782Z,
mtime: 2019-02-27T15:54:52.782Z,
ctime: 2019-02-27T15:54:52.782Z,
birthtime: 2019-02-27T15:54:16.784Z }
Le sam. 2 mars 2019 à 11:17, Benjamin Pasero <[email protected]> a
écrit :
… @LeNouveau <https://github.com/LeNouveau> could you try to use node.js to
stat the path and see if the stat also tells it is a folder?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#69333 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADgBISSSq0PQuIiw0Zf6_3DvdHm-zw70ks5vSk--gaJpZM4bPZqd>
.
|
@LeNouveau yeah, can you also do |
```
fs.statSync("Simple gsheet file.gsheet").isDirectory()
false
```
Le sam. 2 mars 2019 à 14:51, Benjamin Pasero <[email protected]> a
écrit :
… @LeNouveau <https://github.com/LeNouveau> yeah, can you also do fs.statSync("Simple
gsheet file.gsheet").isDirectory()?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#69333 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADgBIS5hxeqj5SwUQUeXvaNkajEjmvrKks5vSoHZgaJpZM4bPZqd>
.
|
@LeNouveau which node version is that? Can you try with |
@bpasero I just tried to repro and calling |
@isidorn do you get the endless loop with the changes from #69333 (comment) |
|
@bpasero yes I can repro. Sorry for the slow response. |
@isidorn I pushed a change to not move focus into the explorer. I think that is a good change anyway because otherwise focus gets lost from the editor without explicit user choice. |
@LeNouveau can we try another thing with node.js, which is to |
@bpasero cool, thanks. Makes sense to me |
The script : fs = require('fs')
fs.open('Simple gsheet file.gsheet', 'w', 0o666, (err, fd) => {
if (err) {
console.error(err);
} else {
fs.fstat(fd, (err2, stats) => {
if (err2) {
console.error(err2);
} else {
var bufferSize = stats.size,
chunkSize = 512,
buffer = Buffer.alloc(bufferSize),
bytesRead = 0;
while (bytesRead < bufferSize) {
if ((bytesRead + chunkSize) > bufferSize) {
chunkSize = (bufferSize - bytesRead);
}
fs.read(fd, buffer, bytesRead, chunkSize, bytesRead);
bytesRead += chunkSize;
}
console.log(buffer.toString('utf8', 0, bufferSize));
fs.close(fd, (err3) => {
if (err3) {
console.error(err3)
}
});
}
});
}
}) The result :
As it is a |
@LeNouveau any difference if you open with |
@bpasero No, exact same output, with Google Drive File Stream version : 29.1.85.2056 |
Sorry, miss click |
ok super weird, I am out of ideas why we think the files are folders :-/ |
This issue is being closed to keep the number of issues in our inbox on a manageable level, we are closing issues that are not going to be addressed in the foreseeable future: We look at the number of votes the issue has received and the number of duplicate issues filed. More details here. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider. If you wonder what we are up to, please see our roadmap and issue reporting guidelines. Thanks for your understanding and happy coding! |
Can this be reconsidered considering the additional duplicate issues? |
When opening a
*.gsheet
file synchronized with Google Drive, VSCode loops and is partially blocked. I can't use it anymore.A simple reboot solves the looping.
Other behaviour : if a file is already opened, on opening the
*.gsheet
file, I have a message 'File is a Folder', but no looping.For reminder, when clicking on this kind of file, Google Drive redirects us on the web interface.
The file isn't really accessible in local.
Demo of behaviour
Versions :
Steps to Reproduce:
g:\
device should appear.*.gsheet
file.g:\
folder with VSCode.*.gsheet
file.Does this issue occur when all extensions are disabled ? : Yes
The text was updated successfully, but these errors were encountered: