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
{{ message }}
This repository has been archived by the owner on Aug 3, 2020. It is now read-only.
Currently the relay service immediately acknowledges a client connection closure request. This however leads to a race condition where clients think they've been cleaned up, but in reality not yet.
This becomes obvious during testing (iris-go: req/rep), that one test influences another. If they are run individually, all is ok. If multiple one after the other, new requests get assigned to stale old connections.
The text was updated successfully, but these errors were encountered:
Currently the relay service immediately acknowledges a client connection closure request. This however leads to a race condition where clients think they've been cleaned up, but in reality not yet.
This becomes obvious during testing (iris-go: req/rep), that one test influences another. If they are run individually, all is ok. If multiple one after the other, new requests get assigned to stale old connections.
The text was updated successfully, but these errors were encountered: