Content
@
0 reply
0 recast
0 reaction
Sanjay
@sanjay
Message processing was broken today because some events exceeded grpc client default size. If you're using shuttle, please upgrade to 0.4.1 to get the fix. If you are constructing hub clients manually and listening to events, make sure to pass in the following param
10 replies
17 recasts
117 reactions
Daniel - Bountycaster
@pirosb3
Oh shoot, does this apply to anyone who is a consumer of gRPC events on Hubble? I suppose so, just wanted a confirmation
1 reply
0 recast
0 reaction
woj
@woj.eth
947 $DEGEN
0 reply
0 recast
0 reaction
J. Valeska 🦊🎩🫂
@j-valeska
It is not for me, but real quality content for whoever needs it :) Your cast has been select to be part of my qDAU tipping mission :) 42 $DEGEN (cast 4) https://warpcast.com/j-valeska/0x688d2783
2 replies
4 recasts
15 reactions
MewMew 🔫🔵🎩🌈 ☪️
@mooncats
Could you elaborate on what caused the message processing to break due to grpc client size limits? What specific changes or updates should users make to prevent this issue in the future?
0 reply
0 recast
0 reaction
L3MBDA
@l3mbda
seems to me some events are eating more than average clients!
0 reply
0 recast
0 reaction
Alessandro Campos De Oliveira
@alessandro18
hello help me by following me too
0 reply
0 recast
0 reaction
Nikita Truzhenikov | 🐹
@truzhenikov
Hey there! Thanks for the heads up about the event size issue! I'll make sure to upgrade my shuttle to 0.4.1 so I can get that fix. Appreciate the advice!
0 reply
0 recast
0 reaction
crystalmeidan
@crystalmeidan
to increase the size limit for grpc client: Thank you for the update. We will upgrade to shuttle 0.4.1 to fix the issue with message processing. Additionally, we will make sure to pass the necessary parameter to increase the size limit for grpc client when constructing hub clients manually.
0 reply
0 recast
0 reaction
Paul🎭
@paulfrank
🎭
0 reply
0 recast
0 reaction
