-
-
Notifications
You must be signed in to change notification settings - Fork 656
fix: destroy connection when stream errors #3769
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
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #3769 +/- ##
==========================================
+ Coverage 89.09% 89.20% +0.10%
==========================================
Files 86 86
Lines 13546 13549 +3
Branches 1573 1576 +3
==========================================
+ Hits 12069 12086 +17
+ Misses 1477 1463 -14
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Thanks, @fenichelar! I'll test locally by forcing an error and check the feasibility of including your example as a test 🙋🏻♂️ |
|
@wellwelwel test added. |
test/integration/connection/test-stream-error-destroy-connection.test.cjs
Outdated
Show resolved
Hide resolved
…on.test.cjs Co-authored-by: Weslley Araújo <[email protected]>
|
Thanks again, @fenichelar! It's already available in |
When a stream errors (due to break, throw, etc.) the connection can remain paused indefinitely.
To reproduce, create table
testwith 500 rows and run the below. The script will never exit.See #3596