-
Notifications
You must be signed in to change notification settings - Fork 104
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
Ensure duplexer stop entails a websocket close #3246
Conversation
Codecov Report
@@ Coverage Diff @@
## main #3246 +/- ##
=======================================
Coverage 65.61% 65.62%
=======================================
Files 619 619
Lines 48887 48894 +7
Branches 4404 4404
=======================================
+ Hits 32076 32085 +9
+ Misses 15310 15307 -3
- Partials 1501 1502 +1
📣 Codecov can now indicate which changes are the most critical in Pull Requests. Learn more |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, with one tiny question.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch!
3dfe652
to
df95af4
Compare
- If immediately stopped, the duplexer might not have closed the connection it made. This will appear as a fault on the server side with a code 1006 (connection closed abnormally), and the server handler will terminate expectedly. This change will ensure that a duplexer cannot be used until a connection has been made, meaning `stop` will have closed the connection. - This fix also revealed a programming error in the prefect ensemble where a failure in running the flow would not be handled properly, such as in the case of cancellation. See also equinor#2759 which discusses failures. - Also renamed tests so that they will not be confused with each other.
Issue
Resolves #3137
If immediately stopped, the duplexer might not have closed the
connection it made. This will appear as a fault on the server side
with a code 1006 (connection closed abnormally), and the server handler
will terminate expectedly.
This change will ensure that a duplexer cannot be used until a
connection has been made, meaning
stop
will close the connection and not fail.Pre review checklist
Adding labels helps the maintainers when writing release notes. This is the list of release note labels.