-
-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
Improve readyState behavior to more reliably report connection state #14727
Labels
enhancement
This issue is a user-facing general improvement that doesn't fix a bug or add a new feature
new feature
This change adds new functionality, like a new method or class
Milestone
Comments
alexbevi
added
enhancement
This issue is a user-facing general improvement that doesn't fix a bug or add a new feature
new feature
This change adds new functionality, like a new method or class
labels
Jul 5, 2024
Going to move this one back because I've been having trouble reproducing this issue in AWS lambda |
vkarpov15
added a commit
that referenced
this issue
Sep 17, 2024
fix(connection): avoid returning `readyState = connected` if connection state is stale
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
enhancement
This issue is a user-facing general improvement that doesn't fix a bug or add a new feature
new feature
This change adds new functionality, like a new method or class
Prerequisites
🚀 Feature Proposal
Since
readyState
updates are based on topology status updates, it's less reliable in stateless environments (such as AWS Lamba) as topology update events may be missed while the execution environment is frozen.This can result in
readyState
tests returning stale state information.Motivation
No response
Example
No response
The text was updated successfully, but these errors were encountered: