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

Clarify Connect error debug property type #199

Merged
merged 1 commit into from
Sep 10, 2024

Conversation

timostamm
Copy link
Member

The protocol spec refers to an "object" for the optional debug data in Error and EndStreamResponse. Since some well-known Protobuf types such as google.protobuf.Timestamp serialize to a JSON value, not an object, the debug data can actually contain any JSON value.

Copy link

vercel bot commented Sep 10, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
connect ✅ Ready (Inspect) Visit Preview 💬 Add feedback Sep 10, 2024 0:54am

@@ -606,7 +606,7 @@ resulting object under the "debug" key. Clients must not depend on data in the
{
"type": "google.rpc.RetryInfo",
"value": "CgIIPA",
"debug": {"retryDelay": "30s"},
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤦🏽‍♂️

@timostamm timostamm merged commit 6ea0a60 into main Sep 10, 2024
7 checks passed
@timostamm timostamm deleted the tstamm/Clarify-Connect-error-debug-property-type branch September 10, 2024 18:46
jhump pushed a commit to connectrpc/conformance that referenced this pull request Sep 11, 2024
Connect clients must not depend on data in the "debug" key when
deserializing details from an Error or EndStreamResponse.

This PR adds a test where the "debug" key contains data that does not
match the error detail, and is not a JSON object (see clarification
regarding the property type here
[here](connectrpc/connectrpc.com#199)).
smaye81 pushed a commit that referenced this pull request Sep 30, 2024
smaye81 pushed a commit that referenced this pull request Sep 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants