Dave Enyeart

I believe @ale-linux is familiar with the usage in /common/policydsl/policyparser.go and he could probably advise. The challenge is that this logic is very sensitive to changes, any minor change in...

The drop-in replacement [gitlab.com/tozd/go/errors](https://gitlab.com/tozd/go/errors) does sound enticing. That would be my preference unless somebody volunteers to lead the overall error re-design (Approach 1 above). What do you think @yeasy @ale-linux...

@yeasy I think the reality is that we need to go with the simpler drop-in replacement [gitlab.com/tozd/go/errors](https://gitlab.com/tozd/go/errors) unless somebody volunteers to lead the overall error re-design (Approach 1 above).

@davidkel Remind me, how far did we get with this? Wondering if we should close it now...

@ale-linux I made an initial comment over at https://github.com/hyperledger/fabric/pull/4461#issuecomment-1747668231. I've also opened issue #4468 with more background so that we can discuss a plan in more detail. My suggestion would...

@yeasy What exactly is your proposal here? We had previously decided not to update Fabric module to /v2, since Fabric is not a dependency that other Go projects should pull...

The maintainers can certainly re-evaluate. It will require a specific proposal however. What changes would you like to contribute, what actions need to be taken, and what are the implications?

Let me further explain the rationale of why the maintainers decided not to version the fabric go module: - Fabric codebase pre-dates go modules and therefore doesn't follow typical module...

@Sayalikukkar go ahead and start since the issue has been open a long time, we'd appreciate a pull request. Thanks!

Please edit and clarify the reproduction steps. You mentioned once space was added the orderers were able to restart but "once in a while the orderers go into crash back...