Closed 1gezhanghao closed 1 year ago
same problem to chaincode.Approve(...)
The problem looks to be that status.Convert()
just checks if the error itself has the required GRPCStatus()
method, whereas the error returned wraps the underlying error and so does not directly implement this method. It might be better if the gRPC status functions dealt with wrapped errors better, but the simplest fix is likely to just not wrap the error in the admin API.
It looks like this was recently fixed in grpc-go. Updating the grpc dependency version should resolve it, but it would be good to also have a unit test to confirm.
@bestbeforetoday grpc-go:v.1.55.0 worked, tks
when a chaincode not approved by all orgs, do
chaincode.Commit(...)
,it will give a errorfailed to commit chaincode: rpc error: code = Aborted desc = failed to collect enough transaction endorsements, see attached details for more info
then i try parse the attached details info by
ParseAttachedInfo(.)
, but details length is 0the peer0.org1.example.com give logs as follows
it sames
chaincode.Commit(...)
missing the attached details