Tom Akehurst

OK, I think I can see how the timeout rule might be problematic. Let me consider how this might be made to work better.

@rfodge can you share some detail about the problem you're seeing? This issue should probably have been closed as the offending `ThreadLocal` has been made inheritable now.

Please can you post the details of the vulnerability and how you're discovering it?

@adeete-zeotap please can you share some more info on how you're detecting this - enough for us to be able to replicate?

I'm definitely up for making this possible. This is how I think it should work: * WireMock itself would gain abstractions and extension points to support stub and log persistence....

Relates to #941

Hi @james-bjss we're making Kubernetes a priority at the moment so this is high on the priority list. It should get worked on in the next release.

I've tried running the test cases you've added here with a breakpoint set in `WireMockExtension` line 176 and it seems this might be a JUnit bug, as sometimes the extension...

To clarify - the tests pass or fail deterministically. What I mean is that there are some nested tests whose extension is handed the nested class as the context by...

Sorry, I didn't explain that very clearly - I just pasted your test case into the project without making any changes to the production code so that I could observe...