User Experience for the CLIs

adding another 50 didnt solve it either

2023-08-19T11:56:15.727476Z  INFO sn_testnet: Launching node 97 of 97...
willie@gagarin:~/projects/maidsafe/safe_network$ Logging to directory: "/home/willie/.local/share/safe/node/12D3KooWBwgdPPf92xdcnnifWzqAZjqK5rG6d8VwNEa6Fq8r9Yqk/logs"
RPC Server listening on 127.0.0.1:12097

willie@gagarin:~/projects/maidsafe/safe_network$ SN_LOG=all /usr/local/bin/safe files upload /fgfs/Aircraft/A320-family/
Built with git version: b041beb / main / b041beb
Instantiating a SAFE client...
🔗 Connected to the Network                                                                                                                                                  Loaded wallet from "/home/willie/.local/share/safe/client/wallet" with balance Token(99999636480)
Preparing (chunking) files at '/fgfs/Aircraft/A320-family/'...
Making payment for 4608 Chunks that belong to 976 file/s.
Error: Transfer error Not enough balance, 99.999636480 available, 316096398.846066688 required

Caused by:
    Not enough balance, 99.999636480 available, 316096398.846066688 required

Location:
    sn_cli/src/subcommands/wallet.rs:305:26

Still the (ridiculous) amount required is going down - so the basic theory is correct

EDIT: adding another 150 nodes caused this box to bork – so back to square one.

3 Likes

It’s the Scottish version of economics. We have created a greedy network :smiley: :smiley:

6 Likes

Right - I am confused again…

This worked fine before…

I delete everything in /home/willie/.local/share/safe/

and run
RUST_LOG=safenode,safe cargo run --bin testnet --features local-discovery -- --build-faucet --interval 1000

and this happens

Finished dev [unoptimized + debuginfo] target(s) in 0.16s
     Running `target/debug/testnet --build-faucet --interval 1000`
2023-08-19T18:37:32.723546Z  INFO sn_testnet: Delaying for 1 seconds before launching other nodes
Logging to directory: "/home/willie/.local/share/safe/node/12D3KooWNu1Vddad8XHBSgnNzTijFYgueYdckPr8hrPMj5gdG7Xo/logs"
thread 'main' panicked at 'Failed to listen on the provided address: Other(Custom { kind: Other, error: Left(Left(Os { code: 98, kind: AddrInUse, message: "Address in use" })) })', sn_networking/src/lib.rs:199:14
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Connecting to node's RPC service at https://127.0.0.1:12001 ...

and then eventually

Checking peer id and network knowledge of node with RPC at 127.0.0.1:12001
Connecting to node's RPC service at https://127.0.0.1:12001 ...
The application panicked (crashed).
Message:  Mismatch in node's PID between logs and RPC response
Location: /home/willie/projects/maidsafe/safe_network/sn_testnet/src/check_testnet.rs:106

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.

So peek at the log for the first node and it contains

As local-discovery feature is disabled,

oh really? the command line was
RUST_LOG=safenode,safe cargo run --bin testnet --features local-discovery -- --build-faucet --interval 1000

WTF???

1 Like