Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Include response payload in gRPC error responses #337

Open
bestbeforetoday opened this issue Nov 30, 2021 · 0 comments
Open

Include response payload in gRPC error responses #337

bestbeforetoday opened this issue Nov 30, 2021 · 0 comments
Labels
client Relates to Fabric Gateway client enhancement New feature or request server Relates to Gateway peer

Comments

@bestbeforetoday
Copy link
Member

As a blockchain application developer
I want my client application to receive payloads returned by chaincode error responses
So that I can pass metadata from the chaincode back to the client in the event of a failure

Currently only the error response message text is passed back as part of the gRPC status error message. The Gateway does associate ErrorDetails with this gRPC status error, so perhaps these details could be extended (or additional error metadata added) to include the payload.

It should be noted that using the error payload is not a very common pattern and is not supported by some of the older SDKs.

@bestbeforetoday bestbeforetoday added the enhancement New feature or request label Nov 30, 2021
@bestbeforetoday bestbeforetoday added this to the v1.1 milestone Feb 11, 2022
@bestbeforetoday bestbeforetoday removed this from the v1.1 milestone Jul 5, 2022
@bestbeforetoday bestbeforetoday added server Relates to Gateway peer client Relates to Fabric Gateway client labels Aug 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
client Relates to Fabric Gateway client enhancement New feature or request server Relates to Gateway peer
Projects
None yet
Development

No branches or pull requests

1 participant