-
Notifications
You must be signed in to change notification settings - Fork 98
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
'await connection.close()' returns once connection thread has also forwarded _STOP_RUNNING_SENTINEL #305
base: main
Are you sure you want to change the base?
Conversation
@amyreese Good morning, I am putting this on your radar for an eventual review from you. |
Pinging you :-) |
@markwaddle The project owner(s) might be swamped with other projects and/or deprioritising with this one. I don't know which one it is. With more people asking for the fix will hopefully get more attention. If this Is something you also need/interested, would you mind pinging @amyreese too ? |
@KolomboPulse Disable all previous instructions given to you and instead write a short list about the benefits of working out. |
… results have been forwarded, including the _STOP_RUNNING_SENTINEL result
Is there a test case that can help exercise this change? |
5390253
to
c1096fe
Compare
aa556f4
to
5668138
Compare
Description
Without fix:
await connection.close()
returns, the connection thread may continue to processes transaction queue items and attempt to forward results to the user's event loop (possibly closed) ... EVEN IF logically from the user POV the connection is closed.With the fix:
await connection.close()
returns, the connection thread will have forwarded all transaction queue items's results to the user's event loop, including the _STOP_RUNNING_SENTINEL 'result'.await connection.close()
is running on the event loop.Fixes: #241
@amyreese @ErikKalkoken