chore(bump): grpc-js to 1.9.11 #350
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thank you for reporting this @jokesterfr, we are working on integrating these changes in #351 |
|
Thank you, will keep track of #351 then. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A lot of stability fixes happened on grpc-js recently, I just want to make sure the EventStore client is up to date with these fixes.
I'm experiencing frequent issues with
Error: 14 UNAVAILABLE: Server Is Not Readyon ES 23.10, which I guess is related to socket exhaustion due to mis disconnection of the client. Frequently on the server side we have 0 connections in the$ES_URL/subscriptions/${ES_STREAM}/${ES_GROUP}/infoAPI response, while the Node.js client states that it is still connected.Probably related to:
Customer Support Tracking reference: 110968