Skip to content
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 stability of node specs #266

Merged
merged 5 commits into from
Jun 10, 2024
Merged

Improve stability of node specs #266

merged 5 commits into from
Jun 10, 2024

Conversation

kthomas
Copy link
Contributor

@kthomas kthomas commented Jun 9, 2024

This PR ensures all subscriptions are drained before exiting.

Also, node.Stop() was a method added solely for use by the spec suite. It has been removed in favor of using signals. This should dramatically increase stability of the spec suite.

@kthomas kthomas requested a review from a team as a code owner June 9, 2024 13:44
@autodidaddict
Copy link
Contributor

I'm not sure I fully understand what the benefit is from manually draining subscriptions one by one? When the NATS connection is closed, its subscriptions go away. If the server times out a client connection, that connection's subscriptions go away.

Is there a scenario or a use case (or than a test) that explicit subscription draining addresses?

@kthomas kthomas merged commit 24f51e2 into main Jun 10, 2024
4 checks passed
@kthomas kthomas deleted the fix/sub-draining branch June 10, 2024 14:40
@kthomas kthomas changed the title Ensure subscriptions drain Improve stability of node specs Jun 10, 2024
@kthomas kthomas mentioned this pull request Jun 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants