nats-io / nats-server / 4412

91%

main: 85%

push

travis-ci

<a href="https://github.com/nats-io/nats-server/commit/<a class=hub.com/nats-io/nats-server/commit/3e1728d623f584fa1ff5ecbc8e7a38bfd9a2702e">3e1728d62<a href="https://github.com/nats-io/nats-server/commit/3e1728d623f584fa1ff5ecbc8e7a38bfd9a2702e">&quot;&gt;[FIXED] Some accounts locking issues

- Risk of deadlock when checking if issuer claim are trusted. There
  was a RLock() in one thread, then a request for Lock() in another
  that was waiting for RLock() to return, but the first thread was
  then doing RLock() which was not acquired because this was blocked
  by the Lock() request (see https://github.com/golang/go/commit/</a><a class="double-link" href="https://github.com/nats-io/nats-server/commit/<a class="double-link" href="https://github.com/nats-io/nats-server/commit/e2160cc5713e4954b67ec4eabdb893d2880e10a0">e2160cc57</a>">e2160cc57</a><a href="https://github.com/nats-io/nats-server/commit/3e1728d623f584fa1ff5ecbc8e7a38bfd9a2702e">)

- Use proper account/locking mode when checking if stream/service
  exports/signer have changed.

- Account registration race (regression from https://github.com/nats-io/nats-server/pull/890)

- Move test from #890 to &quot;no race&quot; test since only then could it detect
  the double registration.

Signed-off-by: Ivan Kozlovic <ivan@synadia.com>

54 of 54 new or added lines in 2 files covered. (100.0%)

17372 of 19130 relevant lines covered (90.81%)

76170.18 hits per line