I haven’t used the safenet network in a while again (a year?) and I have to say it’s looking a lot better than last time with all the files put in ~/.safe these days.
But I can’t seem to add files at the moment.
> files put ./dist/ --recursive
[Error] NetDataError - Failed to store Public Sequence data: Data error -> Access denied - CoreError::DataError -> AccessDenied
Does any know what I’m doing wrong?
I am logged in.
> auth status
Sending request to authd to obtain a status report...
+------------------------------------------+--------+
| SAFE Authenticator status | |
+------------------------------------------+--------+
| Authenticator daemon version | 0.0.11 |
+------------------------------------------+--------+
| Logged in to a SAFE account? | Yes |
+------------------------------------------+--------+
| Number of pending authorisation requests | 0 |
+------------------------------------------+--------+
| Number of notifications subscribers | 0 |
+------------------------------------------+--------+
I just tried this and got the same error so I’m not sure what the problem is but I assume there’s been a change to the released software which has broken something.
It should be possible to build an earlier version and use that. It may be simpler to wait for the next working update but I don’t know when that will be as they have been making widespread changes recently.
By the way, you can check the individual vault logfiles:
ls ~/.safe/vault/baby-fleming-vaults/*/safe_vault.log
You must either run a local test (safe vault run-baby-fleming) or join the shared section test, but the latter is not running so that is not an option at the moment.
Just to be clear, there were many! Everyone is still here as well but there have been some big changes such as the removal of PARSEC for BLS-DKG, CRDT data types and tree data type, addition of Asynchronous Trustworthy Transfers and small bits of farming. A LOT has changed since even the last test net that was only a couple months ago. So the reason no one would be testing rn is just in anticipation for the upcoming changes.
@folaht you just need to make sue your CLI is authorise with write access, try to login again but with this additional flag:
$ safe auth login --self-auth
We plan to improve the Access Denied error message to suggest this same solution. Once you authorised the CLI try to upload the files to your local network again.
Yes, a local network is the same as a shared one, the only difference it’s that we run the shared section/network on the cloud with public IPs for people to join/connect-to. Thus, you need write access for your apps like CLI.
[2020-09-07T16:07:43Z INFO safe_api::api::authd_client::authd_client_api] SAFE login action was successful: Logged in successfully!
Logged in successfully
So using -t is both creating the account and logging the safe cli in.
This is confirmed by then doing:
$ safe auth status
Sending request to authd to obtain a status report...
+------------------------------------------+--------+
| SAFE Authenticator status | |
+------------------------------------------+--------+
| Authenticator daemon version | 0.0.11 |
+------------------------------------------+--------+
| Logged in to a SAFE account? | Yes |
+------------------------------------------+--------+
| Number of pending authorisation requests | 0 |
+------------------------------------------+--------+
| Number of notifications subscribers | 0 |
+------------------------------------------+--------+
Put a single file works:
$ echo test > junk.txt
$ safe files put junk.txt
FilesContainer created at: "safe://hnyynyqs7hoqkndrtbiwfgztpn8uxqowu4o1jfjsix3yeooeg8ctuk3omgbnc"
+ junk.txt safe://hbhydyda6qp75zybw7rcnpxuxebwbqfrakjbnkyrf17mus71cnigp51r1e
Put a directory containing two files:
$ safe files put -r junk/
FilesContainer created at: "safe://hnyynyxw5p5ewjhkubkf9mmixbgtoqdgjau8zec5m614rbayarot64ku6sbnc"
+ junk/netstat.txt safe://hbhydynyzp5e9b8wdd3eoi95be4u68t4poxbbjzok6gqwtad78epfwy6m6
+ junk/test.txt safe://hbhydyda6qp75zybw7rcnpxuxebwbqfrakjbnkyrf17mus71cnigp51r1e