I AM OFFERING YOU FREE SAMPLES FOR COUNTERFEIT BANK NOTES
Whatsapp:+1(424)226-8145) FACE TO FACE DEALS 100% LEGIT
BUY QUALITY BANK NOTES TOP CURRENCIES AVAILABLE
Whatsapp:+1(424)226-8145)GET YOUR VALID DOCUMENTS TO
TOP QUALITY MONEY FOR SALE. DOLLAR, POUNDS, EUROS AND OTHER CURRENCIES
In the Homa module for gRPC there are a few places where the code needs to
iterate over all of the values in a grpc_metadata_batch, but there are
currently cases where my code isn't seeing all of the values. Here is an
example from my code that attempts to log all of the values in a batch. The
(take a look at MetdataMap<>::Log() for an API to get a textual
representation out of *all* the things)
On Thu, Oct 12, 2023 at 4:21 PM Craig Tiller wrote:
> `PeerString` (and some others) are Non-encodable metadata: they're getting
> carried around there because they make sense at the same
`PeerString` (and some others) are Non-encodable metadata: they're getting
carried around there because they make sense at the same times as metadata,
but they don't go out on the wire.
So... being non-encodable Encode() skips them.
There's some logging helpers that will catch them, so they show
Thanks for the response. I tried MetadataMap<>::Log(), but it didn't
iterate over the peer string either (and I verified that the peer string is
present by calling batch.get_pointer(grpc_core::PeerString()). I then
thought perhaps MetadataMap<>::ForEach would do the trick, since its
comment
I have an interesting observation with the grpc async server. So, I have 2
worker threads, A and B, each one has its own queue. I ran a stress test,
initially I see that both the worker threads are serving to clients. After
some time, I don't see any activity from thread A. A thread is not
