Johan Haleby

We _should_ be able to do something like this (once support for it is implemented): ```kotlin await untilException() ```

@olasundell I've started implementing in a new branch called [wait-for-exceptions](https://github.com/awaitility/awaitility/tree/wait-for-exceptions). It's very much a proof of concept at this point and you can use it like this: ```java IOException exception...

Thanks a lot for your input, it's really invaluable! I'll definitely take your inputs into account when I continue with the implementation and if you don't mind I'll poke you...

Very good catch, I was not aware of this. Implementing a the `ThreadPoolExecutor` directly is probably a good idea. Thanks for reporting, for the explanation and hint to potential fix...

@tko007 Thanks for the PR (and sorry for the long delay). While I see the usefulness of these functions I'm a bit hesitant to add them to the library. These...

Could you share your test?

Thanks for the PR. Out of curiosity, what is the use case you're trying to solve? Why do you need different implementations of `ConditionFactory` for dev and CI?

AssertionErrors are handled in a special way in order to integrate with other libraries such as AssertJ and thus you can't catch them. Why would you need to do this?

Hmm maybe awaitility could wrap assertion errors internally so that they can be ignored. But I worry about backward incompatibilities if we do this...

That would indeed be a possibility, but we also have to wonder if it's worth the extract complexity of introducing this? Maybe it would.