Questions: If you have a question about how to get one of the test releases working please post on this topic. For anything not about testing and feedback please ask here.
BUGS: If you think you have found a bug, please report as noted below, and be sure to give enough information for the bug to be replicated, such as your operating system, all the steps needed to get to the bug, and sufficient details of what did/didnât happen.
Sometimes copying and pasting text or uploading a screenshot can help a lot. And if you fancy debugging a bit, let me know, it isnât that hard once you have the debugger running!
Reporting BUGs and possible enhancements:
If you have a github account, please go to github.com/theWebalyst/safenetwork-fuse/issues and click âNew Issueâ, but have a look at the existing issues first in case it has already been reported (there a search to help with that).
If you donât have a github account, post on this topic and Iâll pick it up and create an issue for you.
This is the first release for testing so expect bugs! Currently it is only for Linux, but for Windows and Mac OS see the note at the end.
What this does
This gives you read-only access to your SAFE files, public names and services as if they were on your local hard drive (i.e. in ~/SAFE). For more on current and planned capabilities, see the SAFE FUSE topic on the community forum.
Start Peruse or SAFE Browser (any version should work).
Log into your account.
Open a command line console, cd to the folder your created and type ./mount-safe
In another console, type ls ~/SAFE and so on. With luck you will see output similar to the following, but some commands may take a while to complete (see notes below):
NOTES:
to kill it, I recommend the following command
pkill mount-safe; sudo umount ~/SAFE
this is very slow as no attempt has been made to optimise the code so you may find it takes a while to generate the output.
If you want to check the activity, you can run it with extra debug output as follows:
DEBUG=safe-fuse*,safenetworkjs* ./mount-safe
And if you want to capture the output, to help with a bug report for example:
DEBUG=safe-fuse*,safenetworkjs* ./mount-safe 2>&1 | tee debug.log
Bugs and Suggestions
If you want to report a bug or have suggestions for features and improvements see the OP above for how to do this.
If you just need help getting it working, reply to this topic.
Windows and Mac OS
If this release works on Linux I would like somebody (no special skills required) to try packaging this for Windows and/or Mac OS as I donât have access to those at the moment.
Get in touch if youâd like to do this - I can give detailed instructions and help with any issues you encounter so it should be relatively straightforward.
Just tried it on Ubuntu 18.04.1 and Peruse 0.7.0. Iâm getting errors on step #6 when executing ./mount-safe:
tom@tom-ubuntu:~/Apps/safenetwork-fuse-v0.1.0-rc2-linux-x64$ ./mount-safe
ERROR: { Error: ENOENT: no such file or directory, open '/home/tom/Apps/safenetwork-fuse-v0.1.0-rc2-linux-x64/node_modules/@maidsafe/safe-node-app/src/native/mock/libsafe_app.so'
at Object.fs.openSync (fs.js:646:18)
at Object.fs.openSync (pkg/prelude/bootstrap.js:483:32)
at Object.fs.readFileSync (fs.js:551:33)
at fs.readFileSync (pkg/prelude/bootstrap.js:679:36)
at new DynamicLibrary (/snapshot/safenetwork-fuse/node_modules/safenetworkjs/node_modules/ffi/lib/dynamic_library.js:67:21)
at Object.DynamicLibrary (/snapshot/safenetwork-fuse/node_modules/safenetworkjs/node_modules/ffi/lib/dynamic_library.js:33:12)
at Object.ffi.init (/snapshot/safenetwork-fuse/node_modules/safenetworkjs/node_modules/@maidsafe/safe-node-app/src/native/lib.js:20:15)
at new SAFEApp (/snapshot/safenetwork-fuse/node_modules/safenetworkjs/node_modules/@maidsafe/safe-node-app/src/app.js:36:9)
at Object.initializeApp (/snapshot/safenetwork-fuse/node_modules/safenetworkjs/node_modules/@maidsafe/safe-node-app/src/index.js:61:25)
at authorise (/snapshot/safenetwork-fuse/node_modules/safenetworkjs/src/bootstrap.js:0:0)
errno: -2,
code: 'ENOENT',
syscall: 'open',
path: '/home/tom/Apps/safenetwork-fuse-v0.1.0-rc2-linux-x64/node_modules/@maidsafe/safe-node-app/src/native/mock/libsafe_app.so' }
(node:5338) UnhandledPromiseRejectionWarning: Error: SafeContainer initialise failed: _public (Cannot read property 'getContainer' of undefined)
at PublicContainer.initialise (/snapshot/safenetwork-fuse/node_modules/safenetworkjs/src/safe-containers.js:0:0)
at SafenetworkApi.getSafeContainer (/snapshot/safenetwork-fuse/node_modules/safenetworkjs/src/safenetwork-api.js:0:0)
at RootHandler.initRootContainer (/snapshot/safenetwork-fuse/src/safe-vfs/root.js:0:0)
at new RootHandler (/snapshot/safenetwork-fuse/src/safe-vfs/root.js:0:0)
at SafeVfs.mountContainer (/snapshot/safenetwork-fuse/src/safe-vfs/index.js:0:0)
at safeJsApi.bootstrap.then.safeVfs.mountFuse.then._ (/snapshot/safenetwork-fuse/bin.js:0:0)
at <anonymous>
(node:5338) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 6)
(node:5338) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:5338) UnhandledPromiseRejectionWarning: Error: SafeContainer initialise failed: _publicNames (Cannot read property 'getContainer' of undefined)
at PublicNamesContainer.initialise (/snapshot/safenetwork-fuse/node_modules/safenetworkjs/src/safe-containers.js:0:0)
at SafenetworkApi.getSafeContainer (/snapshot/safenetwork-fuse/node_modules/safenetworkjs/src/safenetwork-api.js:0:0)
at RootHandler.initRootContainer (/snapshot/safenetwork-fuse/src/safe-vfs/root.js:0:0)
at new RootHandler (/snapshot/safenetwork-fuse/src/safe-vfs/root.js:0:0)
at SafeVfs.mountContainer (/snapshot/safenetwork-fuse/src/safe-vfs/index.js:0:0)
at safeJsApi.bootstrap.then.safeVfs.mountFuse.then._ (/snapshot/safenetwork-fuse/bin.js:0:0)
at <anonymous>
(node:5338) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 7)
I think that youâve set the system variable NODE_ENV to dev for safe-mount.
Because if you see, in the error message you get, the last subdir of the file path not found is âmock/ââŚ
And because when I test it this way, I get the same result. Without NODE_ENV it works.
Maybe you expect it also to work in dev mode, but that doesnât seem to be supported yet.
Or that also works without NODE_ENV=dev.
ps if you want to check on the running mount-safe if NODE_ENV is set, you could use the following command in another terminal:
Youâre right. I have NODE_ENV set to DEV. Thanks.
UPDATE
Still getting errors after fixing NODE_ENV issue:
tom@tom-ubuntu:~/Apps/safenetwork-fuse-v0.1.0-rc2-linux-x64$ ./mount-safe
Server path not specified, so defaulting to ipc.config.socketRoot + ipc.config.appspace + ipc.config.id /tmp/app.6905
starting server on /tmp/app.6905
starting TLS server false
starting server as Unix || Windows Socket
## socket connection to server detected ##
received event of : auth-uri { id: '6905-cli',
message: 'safe-c2fmzw5ldhdvcmstznvzzq:AQAAAHqoEPgAAAAAAAAAACAAAAAAAAAAzndILF9uhcRZEpo2Si_wPOCtIlUCLuPe7CXPo5aQecAgAAAAAAAAAFlUqVuU0onXyKWkQ3qtzt4tbWn6GYUBA3bRYRq8mEdsIAAAAAAAAABfzJEIRfF_0I5V9C9ha2YEJtVksPTZ1wwbUO0PLm1DD0AAAAAAAAAAyRQMS1g4BRVH-1MKrkFeNnXUPy6Wk2KuQH3B14i-LqVfzJEIRfF_0I5V9C9ha2YEJtVksPTZ1wwbUO0PLm1DDyAAAAAAAAAAuGAAzwyQySml6XTgwU9I_rOAKMK8B7Lu77XJ8-tqWlMgAAAAAAAAAN44CYwkJqc4nH2UY6lB37VKggXvqbJTyBg-O7Cym5VXAAAAAAAAAAAAAAAAAAAAAMrUoDUQYw2S47O_bmo7NaWaipMO7ZkwuJa6Tq8XEIczmDoAAAAAAAAYAAAAAAAAAP5A7WhSKU5qi0Nyws3yxgV_9h9zIEudWgIAAAAAAAAADAAAAAAAAABfcHVibGljTmFtZXOOp9aa1BV6x8GPlYGSn5zQS0AOqzCphLuqkWcQdD0KWpg6AAAAAAAAASAAAAAAAAAA32qixW66VDOakhT08XP3_fYKG5HPs72Pgh1bso77KVQYAAAAAAAAANRdwDxCEGYY-T0LtLIHc_VAHO_KtPC1uAAEAAAAAAAAAAAAAAABAAAAAgAAAAMAAAAHAAAAAAAAAF9wdWJsaWO3YEcoHEJKN5H9vsJ-8f3EHh_PvmvGdBXHYvfQC2FDIZg6AAAAAAAAAAAEAAAAAAAAAAAAAAABAAAAAgAAAAMAAAA' }
socket disconnected 6905-cli
(node:6905) UnhandledPromiseRejectionWarning: Error: SafeContainer initialise failed: _public (Cannot read property 'getContainer' of undefined)
at PublicContainer.initialise (/snapshot/safenetwork-fuse/node_modules/safenetworkjs/src/safe-containers.js:0:0)
at SafenetworkApi.getSafeContainer (/snapshot/safenetwork-fuse/node_modules/safenetworkjs/src/safenetwork-api.js:0:0)
at RootHandler.initRootContainer (/snapshot/safenetwork-fuse/src/safe-vfs/root.js:0:0)
at new RootHandler (/snapshot/safenetwork-fuse/src/safe-vfs/root.js:0:0)
at SafeVfs.mountContainer (/snapshot/safenetwork-fuse/src/safe-vfs/index.js:0:0)
at safeJsApi.bootstrap.then.safeVfs.mountFuse.then._ (/snapshot/safenetwork-fuse/bin.js:0:0)
at <anonymous>
(node:6905) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 4)
(node:6905) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:6905) UnhandledPromiseRejectionWarning: Error: SafeContainer initialise failed: _publicNames (Cannot read property 'getContainer' of undefined)
at PublicNamesContainer.initialise (/snapshot/safenetwork-fuse/node_modules/safenetworkjs/src/safe-containers.js:0:0)
at SafenetworkApi.getSafeContainer (/snapshot/safenetwork-fuse/node_modules/safenetworkjs/src/safenetwork-api.js:0:0)
at RootHandler.initRootContainer (/snapshot/safenetwork-fuse/src/safe-vfs/root.js:0:0)
at new RootHandler (/snapshot/safenetwork-fuse/src/safe-vfs/root.js:0:0)
at SafeVfs.mountContainer (/snapshot/safenetwork-fuse/src/safe-vfs/index.js:0:0)
at safeJsApi.bootstrap.then.safeVfs.mountFuse.then._ (/snapshot/safenetwork-fuse/bin.js:0:0)
at <anonymous>
(node:6905) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 5)
I was using the âdevâ version of Peruse. I got it mounting with the non-dev version, but managed to get it âstuckâ:
tom@tom-ubuntu:~/Apps/safenetwork-fuse-v0.1.0-rc2-linux-x64$ cd ~/SAFE
tom@tom-ubuntu:~/SAFE$ ls
_public _publicNames
tom@tom-ubuntu:~/SAFE$ cd _public
tom@tom-ubuntu:~/SAFE/_public$ ls
tom@tom-ubuntu:~/SAFE/_public$ cd ..
tom@tom-ubuntu:~/SAFE$ ls
_public _publicNames
tom@tom-ubuntu:~/SAFE$ cd _publicNames/
tom@tom-ubuntu:~/SAFE/_publicNames$ ls
tom@tom-ubuntu:~/SAFE/_publicNames$ cd ..
^C^C^C^Z^Z^X^X^C^C
It seems to work fine in the terminal until I double-click on the mounted SAFE icon - after that itâs stuck.
And once itâs stuck, I canât umount it and need to reboot:
tom@tom-ubuntu:~/Apps/safenetwork-fuse-v0.1.0-rc2-linux-x64$ pkill mount-safe
tom@tom-ubuntu:~/Apps/safenetwork-fuse-v0.1.0-rc2-linux-x64$ sudo umount ~/SAFE
[sudo] password for tom:
umount: /home/tom/SAFE: target is busy.
tom@tom-ubuntu:~/Apps/safenetwork-fuse-v0.1.0-rc2-linux-x64$
@tmark have a go with @drawâs suggestion but I think you still have the error you posted, just that youâre not seeing the error message in the second attempt - the behaviour youâre seeing with ls ~/SAFE is as expected given that error. The next command to try would be ls ~/SAFE/_public and I think that will fail with an error.
@bzee and I have it working, probably because we have a particular package installed so we need to track that down but the errors arenât helpful so it might take some effort.
Thanks for the reports, they help a lot @tmark, and thanks for helping out here @draw.
If anyone has success, please also let me know!
The errors @tmark is posting appear quite common although at this time I donât know the cause so Iâll need to investigate next week.
Strangely, @bzee (who has helped a lot getting this far with some tricky problems already) has the branch with safe-node-app v0.9.1 working, but it wonât work for me. And we both have the branch which uses safe-node-app v0.8.1 working (which is the release published here).
All of these errors only happen with the packaged build though (made using pkg as in the safe-cli-boilerplate), so it is possible to run it by installing nodejs and then running node bin.js if anyone is keen to try it out that way - or wants to help debug it of course!
Debugging is pleasant because you can use the Chrome debugger which is very powerful. You can debug any node program this way.
@happybeing, I only run into the hanging situation when using the GUI âFilesâ to try to browse the mounted SAFE drive, which may be due to those unimplemented operations you mention.
Everything seems to be working fine from the terminal, including changing to ~/SAFE and ls inside:
tom@tom-ubuntu:~/Apps/safenetwork-fuse-v0.1.0-rc2-linux-x64$ ls ~/SAFE
_public _publicNames
tom@tom-ubuntu:~/Apps/safenetwork-fuse-v0.1.0-rc2-linux-x64$ ls ~/SAFE/_public
tom@tom-ubuntu:~/Apps/safenetwork-fuse-v0.1.0-rc2-linux-x64$ ls ~/SAFE/_publicNames
tom@tom-ubuntu:~/Apps/safenetwork-fuse-v0.1.0-rc2-linux-x64$ tree ~/SAFE
/home/tom/SAFE
âââ _public
âââ _publicNames
2 directories, 0 files
tom@tom-ubuntu:~/Apps/safenetwork-fuse-v0.1.0-rc2-linux-x64$ cd ~/SAFE
tom@tom-ubuntu:~/SAFE$ ls
_public _publicNames
tom@tom-ubuntu:~/SAFE$ cd _public
tom@tom-ubuntu:~/SAFE/_public$ ls
tom@tom-ubuntu:~/SAFE/_public$ cd ../_publicNames/
tom@tom-ubuntu:~/SAFE/_publicNames$ ls
tom@tom-ubuntu:~/SAFE/_publicNames$ cd ..
tom@tom-ubuntu:~/SAFE$ ls
_public _publicNames
tom@tom-ubuntu:~/SAFE$
Itâs not really a bug, but because you are trying to create a file in your SAFE drive which isnât possible yet - will be working on that soon I hope.
This early code is a bit ropey in places Iâm afraid, so you have to behave if you donât want to break it
My babelfish is malfunctioning, I thought you said PEBKAC.
Oh, and I see I misread your post and look forward to the bug report about your public names not showing up. Thatâs an odd one assuming they are valid names (lower case alpha numeric with 3 to sixty something characters)?
, if you want to edit this âwikiâ post): update this to point to the current âdive inâ instructions.
Currently it is only for Linux, but for Windows and Mac OS see the note at the end.
