and just to note random file also sees cat works and files get not…
$ safe files get safe://hbhyyynsxu1eowqanmnn9ymyueiqipukw4k49xtphsumsm851obgxuud79
[2020-04-14T21:22:51Z ERROR safe] safe-cli error: [Error] NetDataError - Failed to get current version: [Error] NetDataError - Failed to get Sequenced Append Only Data: NetDataError("Failed to get Sequenced Append Only Data indices: CoreError(Data error -> Requested data not found - CoreError::DataError -> NoSuchData)")
$ safe cat safe://hbhyyynsxu1eowqanmnn9ymyueiqipukw4k49xtphsumsm851obgxuud79
html, body {background:#f4f4f6;}
img {margin:10px auto; display: block;}
I just did
` willie@gagarin:/tmp$ safe files get safe://cdn/js/vue.min.js
[00:00:00] [########################################] 91.47KB/91.47KB (523.91KB/s, 0s) Transfer
Done. Retrieved 1 files to .
willie@gagarin:/tmp$ cat vue.min.js
/*!
* Vue.js v2.6.11
* (c) 2014-2019 Evan You
* Released under the MIT License.
*/
!function(e,t){“object”==typeof exports& ----- ` and so on for another 90k…
willie@gagarin:/tmp$ safe files get safe://hbwynydsqdt8ophjse766t3qxsck1n95t1bwni7i44usf1ukc4316eokxn
[2020-04-14T22:47:42Z ERROR safe] safe-cli error: [Error] NetDataError - Failed to get current version: [Error] NetDataError - Failed to get Sequenced Append Only Data: NetDataError(“Failed to get Sequenced Append Only Data indices: CoreError(Data error → Requested data not found - CoreError::DataError → NoSuchData)”)
btw, the FilesContainer requirement is doc’ed in the usage help:
$ safe files get --help | grep source
safe files get [FLAGS] [OPTIONS] <source> [dest]
<source> The target FilesContainer to retrieve from, optionally including path to directory or file within
but if I try
willie@gagarin:/tmp$ safe files get safe://cdn/css/southside.css
[00:00:00] [########################################] 236B/236B (2.84KB/s, 0s) Transfer
Done. Retrieved 1 files to .
I have contemplated extending safe files get to work with immutabledata urls also, however the other subcommands of safe files all work with FilesContainer data, so it breaks the paradigm a little. anyway, It might gain that capability in the future.
Success of command depends on which node sends the information last
This is most likely a limitation of the sans-parsec baby-fleming network. We’re already looking at a few things to be solving this without the need for a slow consensus step so hopefully will get it sorted in a fresh iteration.
We should get this noted and clarified on the latest baby-fleming network page’s known limitations. Thanks for diving in and the detail @tfa!
As I understand it that’s likely the same issue. Only that vault having the key balance in the initial… We dont have inter-vault gossip enabled yet (and without parsec it’s not being shared in that fashion. Though not the person on this so not 100% sure TBH. @lionel.faber may be able to shed more light).
for the issues @tfa notes, there’s not much to be done at the mo in terms of testing. We’re working on some things to reenable consensus and gossip so will get sorted in another testnet iteration once we’ve that in. Thanks though @Southside!
Even without PARSEC, the objects (Data structs, balances etc.) should be present in all the vaults. I suspect that the vaults might not have formed a section correctly. Although looking at the commands that you have run, everything seems right.
Could you please confirm that in the vaults logs the routing table size is 7?
One more thing to look out for is the port number being used. I see that you have mentioned a port number for the genesis vault. Could you please check if the other vaults are using separate and different ports?
Thanks!
Yes, I confirm the routing table size is 7 and that the port numbers are all different. You can see them by scrolling the log excerpts in my post to the right: Response from: V4(192.168.1.68:NNNNN).
once we’ve that in. Thanks though