At some time need for several branches may appear.
Like separate branch for each testnet.
Small fixes can be added to it, while large changes go to different branch and do not create conflicts.
2 Likes
yes we already have the capacity for multiple testnets and are thoroughly abusing that power 
but its just the script defaults to latest atm.
10 Likes
DO we have a handle yet on how many coins it should take to PUT a 50kb and a 5Mb file?
If I write a script to PUT files from perhaps 50Kb up to 5 Mb, say 20 times each, I don’t want to run out of coins in the middle of the run …
OR: I just cheat and put safe keys create --test-coins --for-cli --preload 10000 at the top of the script… But it may be instructive to see coin consumption as well as times when doing these tests.
Summary
Is that keys create line above still valid syntax? Can’t test it here until the flag fix is in. CBA installing an old sn_node either … 
It works just fine - must be just PUT (maybe GET?) that fails on older CPUs
willie@gagarin:~$ safe keys create --test-coins --for-cli --preload 10000
New SafeKey created: "safe://hyryyyy8roa46e5scjbsc78u3t6xyuwj4tfjhaof6r1ig65ntjjzdzs7k4r"
Preloaded with 10000 testcoins
Key pair generated:
Public Key = e48635e46ecc486cce9e798f9e09d13a8953cc40be24aa6f6c514a6e3bdbaad1
Secret Key = 10d34ae69e8af77bbdde982d492bc68ba5f644c49efe21d6477ee4bff6fd18d9
Setting new SafeKey to be used by CLI...
New credentials were successfully stored in /home/willie/.safe/cli/credentials
Safe CLI now has write access to the network
willie@gagarin:~$ safe keys balance
Checking balance of CLI's assigned keypair...
SafeKey's current balance: 10000.000000000
The smartarse cheeky answer is “learn Rust and fork the code”
I’m sure @happybeing would approve.
I know I’d love to but I have proved to myself that I am no use at Rust
4 Likes
I was getting the illegal instruction (core dump) when trying to upload files with the latest releases.
I built node to see if it fixed the issue - it did not.
I built cli and I can now upload files.
safe keys create --test-coins returned, Error: NetDataError: Failed to PUT Public Blob: Transfer(InsufficientBalance) when trying to upload.
but with safe keys create --test-coins --preload 1000000 --for-cli the upload succeeded.
before I built cli
after
josh@pc1:~$ safe node run-baby-fleming
Storing nodes' generated data at /home/josh/.safe/node/baby-fleming-nodes
Launching local Safe network...
Launching with node executable from: /home/josh/.safe/node/sn_node
Version: safe_network 0.6.1
Network size: 11 nodes
Using RUST_LOG 'safe_network=debug'
Launching genesis node (#1)...
Connection info directory: /home/josh/.safe/node/node_connection_info.config
Genesis node contact info: ["127.0.0.1:53339"]
Common node args for launching the network: ["-vv", "--idle-timeout-msec", "5500", "--keep-alive-interval-msec", "4000"]
Launching node #2...
Launching node #3...
Launching node #4...
Launching node #5...
Launching node #6...
Launching node #7...
Launching node #8...
Launching node #9...
Launching node #10...
Launching node #11...
Done!
josh@pc1:~$ safe keys create --test-coins
New SafeKey created: "safe://hyryyyyym11uxc1u4xi8m3td3hiuptx3bmucox37rkh6npzebx7enefrj4e"
Preloaded with 1000.111 testcoins
Key pair generated:
Public Key = 0b94a6f64a7a7d4ebcc479e566d8bf215cd907e7a4573c26dd017f50241489d2
Secret Key = 63628c6dce97708a987f496b09ed9ba84003e2f1b7416bfc36bddfc613de8ad4
josh@pc1:~$ safe files put ./upload/1.jpeg
Error: NetDataError: Failed to PUT Public Blob: Transfer(InsufficientBalance)
josh@pc1:~$ safe files put ./upload/1.jpeg
Error: NetDataError: Failed to PUT Public Blob: Transfer(InsufficientBalance)
josh@pc1:~$ safe keys create --test-coins --preload 1000000 --for-cli
New SafeKey created: "safe://hyryyyyd467n5wne9kbt6nhd1d5s4x7866wjr4zqa8uu6a3hhpbdfy868ih"
Preloaded with 1000000 testcoins
Key pair generated:
Public Key = 7af745ba091f5063e170721eeda7f4fef5124d5dd83ce7ec679c6846501fc7af
Secret Key = a81f77ab310c4167e167931b273b868849ac0e39580ea57a962f48d52eefbcc5
Setting new SafeKey to be used by CLI...
New credentials were successfully stored in /home/josh/.safe/cli/credentials
Safe CLI now has write access to the network
josh@pc1:~$ safe files put ./upload/1.jpeg
FilesContainer created at: "safe://hyryyrbc5a9k9hr8kxjkadi684cfwbmzdy9k9y3q1ku6rjqu919qrai7ikynra"
+ ./upload/1.jpeg safe://hygoygyqi4b5itq1cpf358k4jrcnqacyarac4eco3djwe6kg3z47k9wjx9h
1 Like
Is that v0.31.1 you built?
What cpu do you have? cat /proc/cpuinfo?
EDIT: I get a core dump with the latest release of sn_cli-0.31.1-x86_64-unknown-linux-musl.zip from https://github.com/maidsafe/sn_cli/releases/tag/v0.31.1
Im building it myself now, see how I go with that
yes
i5-4460 CPU @ 3.20GHz
josh@pc1:~$ safe -V
sn_cli 0.31.1
josh@pc1:~$ safe node bin-version
safe_network 0.6.1
Just in case it matters, I am using both cli & node built from source but it only started working after building cli too.
1 Like
Yep building from source has worked for me
willie@gagarin:~$ safe keys create --test-coins --for-cli --preload 10000
New SafeKey created: "safe://hyryyyybmuazj8k83w9o8icb4hgd8rxp34pyq1h5s5xnr65xs6yhx6amg3w"
Preloaded with 10000 testcoins
Key pair generated:
Public Key = 2b9e2e93a8f9a7e07ab03ae186723db9d340e97376dbc44f6df6f038ff6166cd
Secret Key = 49a1aab4035efd180970ec71d2423e0c5917ae3e3e4efacfc037c45fe57a996e
Setting new SafeKey to be used by CLI...
New credentials were successfully stored in /home/willie/.safe/cli/credentials
Safe CLI now has write access to the network
willie@gagarin:~$ safe files put logviewer_debug.log
FilesContainer created at: "safe://hyryyrbppnz3x5itnwad6i7h43mc4nrk83f8i7mrbningx5ncbmd4bmkw3enra"
+ logviewer_debug.log safe://hy8oycymt95onkmjejbxeuqqgko95aqc3fjts63khb1fu4onyra4bppg94e
willie@gagarin:~$ safe -V
sn_cli 0.31.1
willie@gagarin:~$ safe keys balance
Checking balance of CLI's assigned keypair...
SafeKey's current balance: 9999.999996814
willie@gagarin:~$
Avanti!!!
1 Like
Just cli or did you build both?
1 Like
Just cli…
For those intimidated by this talk of “building from source” – Don’t be.
my steps were
cd into suitable directory - in my case $HOME/projects/maidsafe
git clone https://github.com/maidsafe/sn_cli.git
cd sn_cli
cargo build --release
have a quick cuppa
cp target/release/safe ~/.safe/cli/safe
safe node killall
pkill -e safe
and start from scratch with run-baby-fleming etc
4 Likes
This wouldn’t be hard to add and I’d be happy to help any budding Rust coders who fancy having a go. We could do a joint effort.
You could also apply to the BGF for funding.
The latest sn_node changes to the naming of the logs now makes the standard vdash command
vdash ~/.safe/node/baby-fleming-nodes/sn_node*/sn_node.logtimestamp a bit of guesswork
All of that will likely be fixed or made simple/convenient when dbc is integrated. I wouldn’t waste your time.
2 Likes
I’m simply using --preload 10000 at the start of the script - should be sufficient.
but then thats what Bill said about 640kb…
IBM chief said the world will need no more than 8 (5?) computers (mainframes) back in the 50s
Well Red Dwarf predicted computers in toasters and they ended up being right
6 Likes
I wouldn’t know where to start 
I’m not a programmer
Aye, we’ve switched to the gold-standard tracing lib for a bunch of reasons. Sadly their naming isn’t suuuper cusomtisable off the bat (there’s probably a way to do it w/ digging deeper, but I didn’t yet).
@Josh if you’re seeing InsufficientBalance after a IllegalOp crash, generate yourself fresh CLI keys. Should help 
Glad to see building from latest is working for the illegal op folk 
11 Likes
I’m trying to set this up and am running into an error on step #1
Running Ubuntu… I had thought the command would create the files/directories if they do not exist.
“Warning: /tmp/tmp.QAB9vYnhJ4/sn_cli-latest-x86_64-unknown-linux-musl.tar.gz:
Warning: No such file or directory
0 11.3M 0 1677 0 0 1912 0 1:43:29 --:–:-- 1:43:29 1912
curl: (23) Failure writing output to destination”
Any thoughts? Is there some basic step I have not thought of?
Hey Benjamin,
I think it’s because the testnet is currently offline. the testnets usually last a few days until they gather logs and bugs. there’s no ETA for the next one. but they are coming about once every other week.
1 Like