Matthias Hanel 2664e964a8 [fixed] issue with concurrent account fetch when account was incomplete (#2067) ...

* [fixed] issue with concurrent account fetch when account was incomplete

This happened when a dummy (expired/incomplete) account was created during
a route operation. The dummy was to avoid fetching the account, which would
cause a lock inversion.
When a non route request required the account, we'd download it as it is
set to expired.
A concurrent request would result in ErrAccountResolverSameClaims which
the caller did not handle.
Fix is to remove ErrAccountResolverSameClaims.

Signed-off-by: Matthias Hanel <mh@synadia.com>

2021-04-06 12:43:10 -04:00

90 KiB

Raw Blame History

View Raw