A Friendly Programmer
A Friendly Programmer
Sorry it took this long to respond, I'll get on it including a solution I have in mind. Pardon me again.
@denyeart Sincerely speaking, I thought I have responded to this already, Please pardon me. So to the problem at hand, the correction would take place in fabric-chaincode-go itself, which then...
I was waiting for other comments, buh I'll just go ahead, you are very correct with [this](https://github.com/hyperledger/fabric/issues/3650#:~:text=Perhaps%20the%20right%20thing%20to%20do%20is%20bite%20the%20bullet%20and%20make%20the%20breaking%20API%20change%20for%20Fabric%20v3.), it is the only way forward. Also, as you've highlighted, the changes are...
Plus now, it panic as a memory address error, whenever i click the an inline button with callbackdata ` panic: runtime error: invalid memory address or nil pointer dereference [signal...
I'll be awaiting reply, discord username is @tobytobias.
Not again... buh am hoping to take another look at it again.
The sync.Mutex that was dragged into the apiV2 is the problem... function that takes it type and return it... are being flagged by *go vet* as copy of locked values
I'll like to attend to this...
just to clarify, you mean "OrgName"?
Hmmm... should I let it sleep and move on to another instead?