-
Notifications
You must be signed in to change notification settings - Fork 59
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
Detect if event loop is being closed from its own thread #204
Labels
Comments
@JerryShea are you still keen on this one? |
From memory there is a deadlock that can happen if this takes place.
We have never heard of it happening in the wild so low priority
…On Thu, 25 Jan 2024, 4:10 pm Tom, ***@***.***> wrote:
@JerryShea <https://github.com/JerryShea> are you still keen on this one?
—
Reply to this email directly, view it on GitHub
<#204 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AG5XOHPJKOXHE4OWFL2F65TYQJ7YTAVCNFSM6AAAAAA2PJWGESVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJQGUZDGNRZGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Higher priority now as we have seen it happen in customer code. We should throw an exception if someone attempts to do this. |
benbonavia
added a commit
that referenced
this issue
Jul 22, 2024
benbonavia
added a commit
that referenced
this issue
Jul 23, 2024
benbonavia
added a commit
that referenced
this issue
Jul 23, 2024
benbonavia
added a commit
that referenced
this issue
Jul 23, 2024
benbonavia
added a commit
that referenced
this issue
Jul 23, 2024
benbonavia
added a commit
that referenced
this issue
Jul 24, 2024
Released in Chronicle-Threads-2.26ea1, BOM-2.26ea28 |
Released in Chronicle-Threads-2.25.10, BOM-2.25.76 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: