Can I play around with a safe network testnet?

Another CLI crash

the crash report is for the brainy devs to opine on but Im going to take a wild stab and suggest that my attempts at formatting the output of safe files put is causing some indigestion

willie@gagarin:/tmp$ cat /tmp/report-d4539e89-003e-4ba6-9045-45bec39a62dc.toml
name = 'sn_cli'
operating_system = 'unix:Ubuntu'
crate_version = '0.25.3'
explanation = '''
Panic occurred in file '/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/prettytable-rs-0.8.0/src/lib.rs' at line 194
'''
cause = 'Cannot print table to standard output : Broken pipe (os error 32)'
method = 'Panic'
backtrace = '''

   0: 0x7fe0cd90b5ee - prettytable::TableSlice::print_tty::h8e36ffcab6a6bec4
   1: 0x7fe0cce196bf - safe::subcommands::files::files_commander::{{closure}}::hc8d258dc68b444f7
   2: 0x7fe0ccdf70c7 - safe::cli::run_with::{{closure}}::h09f0b26e4414dfbc
   3: 0x7fe0ccd89019 - <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll::h078becce977db4ba
   4: 0x7fe0cce6a7d2 - std::thread::local::LocalKey<T>::with::hd16e14ced8bae5bd
   5: 0x7fe0cccc4a1f - tokio::runtime::enter::Enter::block_on::h54522673e7bea9d7
   6: 0x7fe0ccc67765 - tokio::runtime::thread_pool::ThreadPool::block_on::h7c43d0cdb013a89e
   7: 0x7fe0ccee901b - tokio::runtime::Runtime::block_on::he50578512431431f
   8: 0x7fe0cccd566e - safe::main::hb20983804401d7d6
   9: 0x7fe0ccd3fdd3 - std::sys_common::backtrace::__rust_begin_short_backtrace::h882c9bdca0f619e3
  10: 0x7fe0ccd3fe2d - std::rt::lang_start::{{closure}}::h6f81a7bc24c4a84e
  11: 0x7fe0cd94f369 - core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once::h5ebb83e980356edd
                at /rustc/2fd73fabe469357a12c2c974c140f67e7cdd76d0/library/core/src/ops/function.rs:259
                 - std::panicking::try::do_call::hed50049424ee3d72
                at /rustc/2fd73fabe469357a12c2c974c140f67e7cdd76d0/library/std/src/panicking.rs:379
                 - std::panicking::try::h3c1728c72c9519f4
                at /rustc/2fd73fabe469357a12c2c974c140f67e7cdd76d0/library/std/src/panicking.rs:343
                 - std::panic::catch_unwind::h8846e729982505ff
                at /rustc/2fd73fabe469357a12c2c974c140f67e7cdd76d0/library/std/src/panic.rs:431
                 - std::rt::lang_start_internal::h28500d1c33144b32
                at /rustc/2fd73fabe469357a12c2c974c140f67e7cdd76d0/library/std/src/rt.rs:51
  12: 0x7fe0cccd5732 - main'''

This based purely on the fact it only seems to happen when I try to mess with the normal output of safe files put and the Panic occurred in prettytable-rs-0.8.0 which sounds like a formatting/display library to me

I wont promise to eat socks but I am prepared to be wrong :slight_smile:

2 Likes

eli5 how to use a differnet version of node? huelp!

  1. also made a pull request! I added DEST_DIR folder creation with timestamp
2 Likes

Thanks for that PR :slight_smile:

for node version management you could try try GitHub - nvm-sh/nvm: Node Version Manager - POSIX-compliant bash script to manage multiple active node.js versions

1 Like

another pull request, a minor change, instead of making lots of folders in tmp, now all folders are inside the main folder

1 Like

thanks but I still dont know how to use this to get safe node 0.41.2

1 Like

Download the zip file and extract the contents (sn_node) into the ~/.safe/node folder (you’ll need to create the folder first).

Looks like a new version (0.42.3) has just been released.

https://github.com/maidsafe/sn_node/releases/tag/v0.42.3

with sn_node into .safe/node I get this error when:

running safe auth start

safe auth start
Error: Failed to start authd

Caused by:
AuthdError: Failed when invoking sn_authd executable from ‘/home/sm00thie/.safe/authd/sn_authd’

You need to do safe node run-baby-fleming first

2 Likes

Im still getting messaging errors with the latest node v0.42.3

Last useable version for me was 0.41.2

see issue raised at https://github.com/maidsafe/sn_node/issues/1500

Sorry Chris - MAJOR confusion on my part

node is a JS framework, much beloved of @happybeing and other brainy folks
sn_node is the SAFE component which is rather confusingly also known as “node” in the SAFE community.

To roll back to sn_node v0.42.1 I did this:–
Install everything as normal

  1. safe node killall
  2. pkill -e sn_authd
  3. pkill -e safe
  4. rm -rf ~/.safe
  5. curl -so- https://sn-api.s3.amazonaws.com/install.sh | bash
  6. safe node install
  7. safe auth install
  8. check versions
willie@gagarin:~$ safe -V
sn_cli 0.25.3
willie@gagarin:~$ safe node bin-version
sn_node 0.42.3
willie@gagarin:~$ safe auth bin-version
sn_authd 0.7.3

THEN download https://github.com/maidsafe/sn_node/releases/download/v0.41.2/sn_node-0.41.2-x86_64-unknown-linux-musl.zip and unzip it somewhere else - NOT in ~/.safe

go to ~/.safe/node and mv sn_node sn_node0.42.3
Go to where you unzipped the old 0.42.1 and mv sn_node ~/.safe/node/

Let me know how you get on.

Thank you I will have a look at this.
I have changed the working directory from /tmp to /home/$USER/tmp to preserve data between reboots. Eventually I hope to extend the script to collect data from all the timestamped run data subdirs, collate it and send it to somewhere TBD

I said this would happen [smug English face].

2 Likes

I’m sorry but that is not half condescending enough… Please try harder

2 Likes

Would using a poor imitation of a Scottish accent wind you up sufficiently… jimmy?

2 Likes

Only if it is really poor.
Dunno whats going on today at all at all but I am uncommonly serene.

I have this vague feeling of guilt about short-changing my adoring public.

2 Likes

My specialty.

1 Like

I have heard worse.
As long as you are saying “can I buy you a pint, Willie and would you like a nice malt to go with it?” you can use any accent you like.

1 Like
1 Like

I wish I’d known better than go and learn English in Dixie. Now Ireland or Scotland - that would have been something! Sadly, I’ve never even visited.

2 Likes

2 posts were split to a new topic: British imperialism