https://bz.apache.org/bugzilla/show_bug.cgi?id=66482
--- Comment #7 from zhougang ---
(In reply to Remy Maucherat from comment #6)
> I've never seen this exception before, so it is probably not very common.
> Restoring the state with a try/finally and propagating this very unexpected
> exception
https://bz.apache.org/bugzilla/show_bug.cgi?id=66482
Remy Maucherat changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://bz.apache.org/bugzilla/show_bug.cgi?id=66482
--- Comment #5 from zhougang ---
(In reply to Remy Maucherat from comment #4)
> Ok, so that makes sense. I checked the code and both read and write can
> throw this undocumented exception (there are other exceptions but they don't
> occur,
https://bz.apache.org/bugzilla/show_bug.cgi?id=66482
--- Comment #4 from Remy Maucherat ---
Ok, so that makes sense. I checked the code and both read and write can throw
this undocumented exception (there are other exceptions but they don't occur,
unlike this one apparently).
The easiest is
https://bz.apache.org/bugzilla/show_bug.cgi?id=66482
--- Comment #3 from Mark Thomas ---
It might be because 01f2cf25b270a84d0daeefc4f215aa2f56e1df99 also changed the
WebSocket implementation to use AsyncIO.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bz.apache.org/bugzilla/show_bug.cgi?id=66482
Remy Maucherat changed:
What|Removed |Added
OS||All
--- Comment #2 from Remy
https://bz.apache.org/bugzilla/show_bug.cgi?id=66482
--- Comment #1 from zhougang ---
Created attachment 38498
--> https://bz.apache.org/bugzilla/attachment.cgi?id=38498=edit
Exception stack
--
You are receiving this mail because:
You are the assignee for the bug.
