Howdy, all --

I've been seeing race conditions around mutating methods in IvySettings
resulting in occasional NPEs during IVY-1454 regression testing. We're also
getting issues with ConcurrentModificationExceptions from the logger stack
-- which it seems to me we'd need to move the loggers into thread-local
storage to resolve.

Frankly, there's enough side-effecting code throughout the codebase that
I'm uncomfortable only patching the immediately visible issues. What are
folks' thoughts on putting a big lock around the resolve task, and/or
documenting loudly that Ivy is not supported for concurrent use?

Reply via email to