Is that not just a hook for a feature that is coming soon but not quite yet?
Its INFO not ERROR
1 Like
Yeah possibly - I did wonder, but the upload failed/hung anyway.
4 Likes
Yeeeeehaw! Giddyup!
3 Likes
Probably should be a proper error. The jist is that it’s not handled sufficiently to map to a network error message to send to a client/node. So we’re just logging it at the node for now.
@JPL you’re seeing this on upload, not on unlocking the safe itself correct?
Can you provide the previous few lines (I guess from last client msg). 
2 Likes
I think so, it seemed to unlock OK. I’m in Windows and there was no output in cmd on uploading (it just hung) so I’m looking in the logs.
[sn_node] INFO 2021-01-30T11:30:30.618383900+00:00 [src\node\mod.rs:212] Running as Elder: RunAsKeySection(RunAsTransfers(ProcessCmd { cmd: ValidateTransfer(SignedTransfer { debit: SignedDebit { debit: Debit { id: PublicKey::Ed25519(2fc26c..).0, amount: 0.000002188 }, actor_signature: Signature::Ed25519(..) }, credit: SignedCredit { credit: Credit { id: [141, 226, 130, 85, 26, 131, 164, 84, 239, 66, 17, 57, 231, 5, 26, 239, 160, 138, 182, 235, 205, 129, 117, 225, 51, 247, 228, 63, 241, 128, 150, 27], amount: 0.000002188, recipient: PublicKey::Bls(8a5a38..), msg: "asdf" }, actor_signature: Signature::Ed25519(..) } }), msg_id: MessageId(04b42a..), origin: Client(2fc26c..) }))
[sn_node] INFO 2021-01-30T11:30:30.618861300+00:00 [src\node\node_duties\mod.rs:89] Checking duty level: are we an Elder? true
[sn_node] INFO 2021-01-30T11:30:30.619232100+00:00 [src\node\mod.rs:229] unimplemented: Handle errors.. No mapping to sn_messages error is set up for this NodeError Logic error: Key does not exist among locks.
EDIT: I can reproduce on Linux too. Could it be that the safe is not connecting to the network properly and therefore uploads don’t work? GETs such as files ls work OK
3 Likes
Amazing!
Such a small change (11 new lines, 2 removed) but SO MUCH work to discover where the problem is and SO MUCH benefit from having it fixed. Thank you for your work @joshuef and @bochaco 
25 Likes
Aim for Feb 14th for public test net? 1 sprint week 1 just the fixes, 1 week setup and docs, all hands on deck? Forget the new featuring, its about credibility, hitting promise dates. Getting feedback from tech savvy types. just sayin’
r2
4 Likes
I’m busy watching a video about radix the project SPB shared.
In it the CEO Pierce claims that a security audit can cost a million dollars.
Is that absurd or is a reputable audit really that ridiculous?
2 Likes
It’s a new cash cow for many. No audit will insure a system is safe, they only say we could not find anything or a report on potential issues. It’s just society these days, hackers steal, security companies profit etc.
If I recall correctly norton anti virus was fined for producing a fix for a virus before the virus was known 
(implication they wrote viruses).
So audits are impossible to value, but useful. We just need to be careful.
10 Likes
Why am I not surprised
5 Likes
Thank you for the heavy work team MaidSafe! Let’s Safe it together!
I add the translation into Bulgarian in the first post 
8 Likes
nopes, didn’t get a response, but given the Safe Chat video, I think it’s safe to say it’s Fleming release
Sort of, it’s a testnet, when it stabilises then it’s Fleming. Then upgrades and we are off to the races.
8 Likes
I also get the urgency to name it and make a spectacle but it’s not a release until it’s stable. It’s not features we’re testing that may fail on top of a working network, we’re literally testing the network and if that falls apart then you have nothing, a flop. So we have to be a little more careful in this regard.
Ethereum knew blockchain worked so even though their smart contracts might have caused some problems the network itself never went down so it’s hard for us to compare.
Tezos on the other hand did do test net because they had to prove on chain upgrades with no forking and surprise surprise, it wasn’t sexy or flashy or a big spectacle. It started to be when they began naming the upgrades after main net and delivering features that enhanced the capabilities of the Tezos blockchain and smart contracts.
So I like the naming thing and think it’s important but I think it’s also important that we call it Fleming when it’s Fleming. So maybe we don’t make a big deal about test nets yet, when Fleming is imminent then we create hype about it (but close so it’s not more waiting than anyone has gone through). Making hype about Fleming when it’s out will be far easier and also easier for any release after!
3 Likes
Geez @Maidsafe! Stop having morals and put out a press release so people can make profit to buy their lambos!
To contrast this further with Ethereum. Tezos didn’t release these visual ‘cards’ or usable imagery that went along with the name of an upgrade or release like Ethereum did. I think that adding the visual component and putting it front and center on your website and a shareable card for social media is like when someone would go all in on a full page ad in the paper. It makes it more of a statement and a spectacle.
So when we know Fleming is imminent then perhaps we should make the safenetwork.tech landing page a simple and aesthetically appealing imagery that matches the naming convention (Fleming, then Maxwell, whatever is next) in this case Fleming, and have an up front and accessible means to learn what the technological milestones the release achieves, in as few words to make it digestible as possible.
2 Likes
Haa. Quis custodiet ipsos custodes?
So who audits the auditors?
1 Like