Skip to content

concurrent resolves share one subscribe

Latest
Latest

Choose a tag to compare

View all tags
@dmitry-lebedev dmitry-lebedev released this 18 Oct 08:19
v0.45.1
cef5092

Concurrent resolves of one entity no longer leave a dead API client in the cache.

Fixed

  • Two concurrent GetServiceAsync calls for one entity could cache an API client that threw ObjectDisposedException on every call; concurrent resolves now share one subscribe and one live client.
  • A cross-entity subscribe racing GetServiceAsync on the same entity no longer kills the API client either.
  • DisconnectAsync / supersede restart during an in-flight subscribe fails that resolve with OperationCanceledException instead of caching the dropped connection afterwards.
Assets 3
Loading