Open 3cooper opened 3 years ago
This is somehow caused by running the tests via VSCode. If I run from the command line, I do not get the same issue. Can anyone provide a hint as to why this would be? Is it a permissions thing where VSCode has access to the files but can't run scandir? Makes me wonder if there is something in my return from getAttr return that is causing this.
I have a file system implemented using Fuse-Native that I can navigate via OS X Finder. I am making a tester for the file system to ensure it works after making changes. I am trying to get the contents of a directory using a script in Node.js, but it is failing.
Example dir:
/Users/me/Documents/fusemount/virtualDir
The error:
'EPERM: operation not permitted, scandir '/Users/me/Documents/fusemount/virtualDir'
The code I am using:
When I run this I have successful requests for:
access('\')
getAttr('\virtualDir')
getAttr('\')
The debug console shows:
I have not implemented the following operations:
releaseDir
ftruncate
fgetAttr
utimens
fsync
fsyncDir
My
statfs
operation is returning the same information found in the readme for this project.getAttr
returns the following for folders:Any help would be great. Thanks.