Failing to store wallet url at a human readable location

[Southside]

I am trying to store a wallet URL at a human readable location safe://wallet.account and failing miserably and consistently. Here’s my latest attempt.

willie@gagarin:~$ echo $(safe wallet create --json) > tmp.txt
willie@gagarin:~$ cat tmp.txt
"safe://hyryynyo83red8j38d7gk971kiifr9rzdyoqk9dz4xt7m7eg43hpqjwgesob6o"
willie@gagarin:~$ files_container=$(safe files put --json  tmp.txt | jq '.[0]')
willie@gagarin:~$ echo $files_container
"safe://hyryyryw53os66y6d1imeiccsc3h8doesko54m7rzy9xqk5u1fx91tw81ornra?v=hya599e8mt51c5mkx1qphzf93x1pbrt9nu9z1j7oicj6bz884r9fo"
willie@gagarin:~$ wallet_container_location=$(safe nrs add --register-top-name --link $files_container  wallet.account)
Error: 
   0: InvalidXorUrl: path contains empty component

Location:
   sn_cli/src/subcommands/helpers.rs:270

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

What am I doing wrong?
Is this even possible at this time? ie Store a wallet URL for a freshly created wallet which naturally has a zero balance and contains no DBCs whatever.

[chriso]

I think this is the same, or very similar to the issue you raised in this thread.

I’m going to be looking into all these issues now, over the next one/two weeks. I already fixed the update commands yesterday.

Hang tight please.

[Southside]

Thanks @chriso

I’ll move to other things meantime.

[Southside]

@chriso

I already fixed the update commands yesterday.

Yep we get a different error msg now IIRC - A different error msg is ALWAYS a good(ish) sign
Looks like the mechanism is working - just pointing at a 404 - which is totally understandable as there hasnt been a release since last week. Thanks @chriso

willie@gagarin:~/projects/maidsafe/safe_network$ safe update
Error: 
   0: Error performing update: NetworkError: api request failed with status: 404 - for: "https://api.github.com/repos/maidsafe/sn_cli/releases"

Location:
   sn_cli/src/cli.rs:127

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

[happybeing]

The safe update problem was always a 404 AFAIK, at least that’s what I had.

[chriso]

Sorry, my message wasn’t really clear.

I haven’t submitted the fix for PR yet. Will be doing so today.

[Southside]

Sorry I thought we were getting a different error before - TBH its been quite a while since I have used safe update myself as I am usually pulling and building from Github every day or so.

I’ll be glad to see this fixed as it will make the scripts more reliable as we can be sure everyone is on the same versions.