FYI - testing found some issues with the blunt-force approach. I’ve just pushed some changes to mitigate this. There are a few loops that should, rightfully, not reset the thread interrupt state.
-Jordan > On Jan 13, 2016, at 3:52 PM, John Vines <[email protected]> wrote: > > It's not an explicit worry, just a general 'tread lightly' feeling. If > testing shows that it's not a problem (which I would expect to be the case) > then it's probably fine. > > On Wed, Jan 13, 2016 at 3:37 PM Jordan Zimmerman <[email protected]> > wrote: > >> >>> Only concern I have is around behavior of curator >>> owned/managed threads (caches and the like). >> >> What’s the worry? Can you explain? >> >> -Jordan
