I doubt that many people use shell mode.
But maybe we should,? One on my list for the next test net…might not make any difference, but worth a try
What is this shell mode you are referring to?
You enter shell mode running safe
with no arguments. You can then run other commands like files get
without repeating the safe command
I didn’t realize that was possible. What are some of the advantages? I’m just used to Bash.
Advantages: not having to type ‘safe’ and now, each command being a bit more efficient (not having to re-establish network connection).
Disadvantages: can’t use other commands until you exit the Safe shell. Tab completion or up/down arrows to repeat previous commands doesn’t work (h/t @Southside).
Add tab completion doesn’t work - or rather I have not managed to get it to work
up/down arrows to repeat previous commands doesn’t work
Is there a way to run a SAFE daemon? which acts like a socks5 proxy for safe calls?
that way you could just add some ENV and the bash command can detect and route to the daemon instead of spawning a connection
I think that UDP “connections” are not so heavy as TCP.
So such change will not save much resources.
Also console commands are used mainly for testing purposes.
When commands will be produced by browser, then it will be a good place for implementing of such optimization.
Many other PR’s in as well, and we have a release with them now!
So, looking forward for the Playground / Comnet, though I may not be able to participate myself.
Busy bees Ants!
Forgive my ignorance but does that mean dbcs are now in play?
Probably not quite yet, but definitely getting there.
I think the homage to bitcoin and Monero are nice Easter eggs.
https://github.com/maidsafe/sn_dbc/pull/135/commits/e7ca167b392819bb4aeeccf6da0334346cef1c19
happening now: making the tests pass for a new release that fixes a big bug that drops connections!
@joshuef are you working from home on a Saturday? you really want to squash that bug!!!
haha. I do.
Though I’m mostly at it because I had a terrible nights sleep. Woke up at like 5 and couldn’t get down again, so may as well poke at the CI a wee bit . The changes for that are often small, but the jobs still take a bit to run, so good to dip in make a change and dive out again.
That’s the changed merged, so just waiting on the release run to be okay now and we can see where we are. (though I may not be about to launch a playground till later the day, let’s see)
if there is release i may boot dreamnet real quick to test it, but i had no luck with log script, i dont use aws and it doesnt rin correctly for local backend
Well… the run went fine, but there was no release as no change detected . Which is odd… There’s a feat
commit in the sn
dir, which should trigger it.
Damn. This smart_release
crate we use is not that smart.
I’m going to take a nap now, may dig in there later.
But main
should be buildable w/ the node conn retry if you wanted to give that a spin.