muralisrini
muralisrini
> My guess on the CVE coming up is that it doesn't affect this lib based on the description. Yes, as far as I could tell, it doesn't affect this...
> Looks like there is some preliminary support in golang.org/x/crypto/ocsp? > > Edit: So looking at the library, the CRL stuff is easy to implement other than the CRL cache,...
> > > Looks like there is some preliminary support in golang.org/x/crypto/ocsp? > > > Edit: So looking at the library, the CRL stuff is easy to implement other than...
@VRamakrishna : _" It occurs when one or more "query" requests are sent to a chaincode just after it starts up, resulting in the chaincode process **crashing**. "_ I expected...
@corecode : yes, I think you are right. I see two inits in the logs.
@VRamakrishna : its a bug in chaincode. You should not see the problem if you mange it so chaincode is started up with one request before sending a flood of...
@VRamakrishna : I meant ensure the chaincode is started with just to 1 query or invoke (so yes, start the chaincode with a data lookup via a query)
@jyellick @tuand27613 @binh To capture the main point - ExecTxs has access to chaincode generated errors but ignores them today. (Summarizing @jyellick comment) this is because we do not know...
Thanks, @prjayach . @binhn, consensus, acutely sensitive that this is reopening discussions in this area... Is adding "not started/succ/fail" field to proto.Transaction is right thing to do ? What this...
Let me assign to myself to look at options.