You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a callee disconnects in-flight for the second time during second CALL with progressive results, the request ID seems to be stuck to that of the first CALL request.
Crossbar version is master as of the date of this report (post v23.1.2), installed via Pip using Skully17's fix.
Here's a message trace, with the HELLO/WELCOME message options truncated for brevity. The traces are from the point of view of two CppWAMP clients, one acting as caller, and the other as callee.
When a callee disconnects in-flight for the second time during second CALL with progressive results, the request ID seems to be stuck to that of the first CALL request.
Crossbar version is
master
as of the date of this report (post v23.1.2), installed via Pip using Skully17's fix.Here's a message trace, with the HELLO/WELCOME message options truncated for brevity. The traces are from the point of view of two CppWAMP clients, one acting as caller, and the other as callee.
The text was updated successfully, but these errors were encountered: