Was going to report partial success with this but just had a suspected mobo failure on my main machne.
Thank you @nbaksalyar the latest git pull now compiles - but ONLY with --features mock-network - dunno if this is intended/expected behaviour
Could not get a myconfig.json file to work
However I can use safe-authenticator-cli and safe-cli to make accounts wallets on the mock network and transfer testcoins.
About to try connecting with safe-drive when the screens went blank and sound of fans spinning down.
I’ll try to replicate on the laptop later and post the relevant error messages/logs from the issues above.
I am failing to create an new account on a fresh git clone of safe-authenticator-cli and safe-cli on my laptop.
does this command line look right?
willie@sputnik:~/projects/maidsafe/safe-authenticator-cli$ cargo run -- --invite-token t --features mock-network --verbose 2>&1 | tee debug.log`
Compiling safe_core v0.32.1 (https://github.com/bochaco/safe_client_libs?branch=temp-experimental#b40de6d0) error[E0432]: unresolved importrouting::Client --> /home/willie/.cargo/git/checkouts/safe_client_libs-78dcb58b240b6e71/b40de6d/safe_core/src/client/core_client.rs:12:5 | 12 | use routing::Client as Routing; | ^^^^^^^^^^^^^^^^^^^^^^^^^^ noClient in the root
|
|
| snip
|
|
error[E0282]: type annotations needed
--> /home/willie/.cargo/git/checkouts/safe_client_libs-78dcb58b240b6e71/b40de6d/safe_core/src/client/mod.rs:1248:46
|
1248 | send(client, request.message_id(), move |routing| {
| ^^^^^^^ consider giving this closure parameter a type
|
= note: type must be known at this point
error[E0282]: type annotations needed
--> /home/willie/.cargo/git/checkouts/safe_client_libs-78dcb58b240b6e71/b40de6d/safe_core/src/client/mod.rs:1290:55
|
1290 | send_mutation(client, message.message_id(), move |routing, dst| {
| ^^^^^^^ consider giving this closure parameter a type
|
= note: type must be known at this point
error: aborting due to 21 previous errors
Some errors occurred: E0282, E0432.
For more information about an error, try `rustc --explain E0282`.
error: Could not compile `safe_core`.
To learn more, run the command again with --verbose. `
Make sure you remove the comment you have in the json config file (// my.config.json). We should handle the error better though, I’ll try to send a PR for that.
excellent - thank you willie@sputnik:~/projects/maidsafe/safe-authenticator-cli$ nano my.config.json willie@sputnik:~/projects/maidsafe/safe-authenticator-cli$ cargo run --features mock-network -- --pretty --config ./my.config.json Finished dev [unoptimized + debuginfo] target(s) in 0.35s Running ``target/debug/safe_auth --pretty --config ./my.config.json Warning! Storing your secret/password in plaintext in a config file is not secure. Logged in the SAFE Network successfully! willie@sputnik:~/projects/maidsafe/safe-authenticator-cli$
Clone and build safe-cli - seems to be OK.
Clone and start safe-authenticator-cli in a separate terminal with cargo run --features mock-network -- --daemon 41805 - seems to be OK. Output ends with:
OK progress of sorts. I can’t get it to recognise my PATH whatever I do (I’m using a MINGW bash console btw), but running it direct from the release folder I get this.
$ ./safe auth
Authorising CLI application...
[2019-08-09T12:33:11Z ERROR safe] safe_cli error: Application authorisation failed: [Error] AuthError - Failed to send request to Authenticator: http://localhost:41805/authorise/bAAAAAAHX24WWUAAAAAABAAAAAAAAAAAANZSXILTNMFUWI43BMZSS4Y3MNEAAQAAAAAAAAAAAKNAUMRJAINGESEAAAAAAAAAAABGWC2LEKNQWMZJONZSXIICMORSAAAIAAAAAAAAAAAAAC: an error occurred trying to connect: No connection could be made because the target machine actively refused it. (os error 10061)
Connection refused.
No connection could be made because the target computer actively refused it. This usually results from trying to connect to a service that is inactive on the foreign host—that is, one with no server application running.
Hmm okay. That sounds reasonably buggy. Would windows have a firewall or something blocking it? Are you able to ping the server otherwise? I’m not super familiar with windows I’m afraid, so not sure what to suggest. And I know @bochaco also isn’t in a windows machine.
Can you please open an issue w/repro steps and we can hopefully get someone to repro that on a Windows box and figure out what’s up.