You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While this can be greatly improved (promises, timeout, passing an error), this minimal implementation is still critical in cases where a timeout or error today will cause a shit storm when using change feeds and websocket connections in tests that must be disconnected before the next test runs.
The text was updated successfully, but these errors were encountered:
This thread has been automatically locked due to inactivity. Please open a new issue for related bugs or questions following the new issue template instructions.
lockbot
locked as resolved and limited conversation to collaborators
Jan 9, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
While this can be greatly improved (promises, timeout, passing an error), this minimal implementation is still critical in cases where a timeout or error today will cause a shit storm when using change feeds and websocket connections in tests that must be disconnected before the next test runs.
The text was updated successfully, but these errors were encountered: