CLI v0.8.0 expected behaviour?

Playing about with the latest CLI and I got this - is this expected behaviour?

willie@gagarin:~/projects/maidsafe$ safe auth status
Sending request to authd to obtain an status report...
+------------------------------------------+----------------+
| SAFE Authenticator status                |                |
+------------------------------------------+----------------+
| Authenticator daemon version             | <not reported> |
+------------------------------------------+----------------+
| Logged in to a SAFE account?             | Yes            |
+------------------------------------------+----------------+
| Number of pending authorisation requests | 0              |
+------------------------------------------+----------------+
| Number of notifications subscribers      | 2              |
+------------------------------------------+----------------+
willie@gagarin:~/projects/maidsafe$ safe auth -V
safe-auth 0.8.1
4 Likes

Yes, that’s because you are still using authd v0.0.2 I presume? you just need to update your authd with $ safe auth update which reports the version in the response.

3 Likes
willie@gagarin:~/projects/maidsafe$ safe auth update
Checking target-arch... x86_64-unknown-linux-gnu
Checking current version... v0.0.4
Checking latest released version... v0.0.4
Setting execution permissions to installed binary '/home/willie/.safe/authd/safe-authd'...
Update status: `0.0.4`!
willie@gagarin:~/projects/maidsafe$ safe auth status
Sending request to authd to obtain an status report...
+------------------------------------------+----------------+
| SAFE Authenticator status                |                |
+------------------------------------------+----------------+
| Authenticator daemon version             | <not reported> |
+------------------------------------------+----------------+
| Logged in to a SAFE account?             | Yes            |
+------------------------------------------+----------------+
| Number of pending authorisation requests | 0              |
+------------------------------------------+----------------+
| Number of notifications subscribers      | 2              |
+------------------------------------------+----------------+
1 Like

Good, you just need to restart authd so it launches the new version: $ safe auth restart

3 Likes

Doh! …

willie@gagarin:~/projects/maidsafe$ safe auth start
Starting SAFE Authenticator daemon (safe-authd)...
willie@gagarin:~/projects/maidsafe$ safe auth status
Sending request to authd to obtain an status report...
+------------------------------------------+-------+
| SAFE Authenticator status                |       |
+------------------------------------------+-------+
| Authenticator daemon version             | 0.0.4 |
+------------------------------------------+-------+
| Logged in to a SAFE account?             | No    |
+------------------------------------------+-------+
| Number of pending authorisation requests | 0     |
+------------------------------------------+-------+
| Number of notifications subscribers      | 0     |
+------------------------------------------+-------+

Thats better. Sorry to hassle you.

3 Likes

No hassle at all! lovely to see you playing with it only hours after it’s been published!

4 Likes

I’d hate to think you published it and none of us tried to use it…

2 Likes

I presume that I am just like any other developer, when I was a kid and started creating software my big dream was simple: “It would be sooo amazing people using what I just created with my keyboard…”, that’s still what I look forward and dream of even that I could say I achieved that dream…but also as I presume any other developer, I want more! …it’s a strong drug :smiley:

11 Likes

Is it planned that the update will auto-restart authd, or at least ask/prompt?

3 Likes

It surely can be an addition to consider

5 Likes

@bochaco

If the restart is necessary for the upgrade to take effect, I believe that that would be the correct default behavior.

4 Likes

Yeah, I wouldn’t strongly disagree, but I always think of those cases where the CLI is used from scripts, automated/backend systems, which may have different flows for when things should start/stop, etc.

3 Likes