Skip to content

Conversation

xumaple
Copy link
Contributor

@xumaple xumaple commented Aug 29, 2025

Motivation

Solution

xumaple and others added 2 commits August 29, 2025 20:32
…yperium#2402)

## Motivation

hyperium#2360 
## Solution


Added the `tls-connect-info` feature which derives from `_tls-any`
feature.

---------

Co-authored-by: Maple Xu <[email protected]>
## Motivation
The `Status` struct is the canonical error message in `tonic`. Printing
it currently prints out a very verbose and difficult-to-read message.

## Solution
Improve `impl, Display for status` by:

* Only printing the `message` if it is non-empty
* Only printing the `metadata` if it is non-empty`
* Always omitting the binary `details` (printing out `details: [22, 51,
50, 48, 51, 53, 98, 57, 50, 55, 50, 55, 100, 54, 101, …]` is not helping
anyone)
Copy link
Member

@LucioFranco LucioFranco left a comment

Choose a reason for hiding this comment

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

I think we need to pin protoc to 31.1 in the CI.yml file for github actions and that should solve the CI issues.

@xumaple
Copy link
Contributor Author

xumaple commented Aug 29, 2025

What's the policy here, that's not something that needs to go into main right? I just make an extra commit here in this branch?

@xumaple xumaple force-pushed the mapxu/status-and-connect-info-into-v014 branch 2 times, most recently from 816e0bb to 38123ad Compare September 2, 2025 16:39
@LucioFranco
Copy link
Member

Okay, I solved this by just ff the v0.14.x branch from master, so we don't need this PR anymore since these commits are already there.

@LucioFranco LucioFranco closed this Sep 2, 2025
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.

4 participants