Sampath Sukesh Ravolaparthi

> Is there a use case you can't achieve with cause or rootCause? No, both `cause` & `rootCause` should solve for the all the usecases. > We prefer relying on...

This is not something that happens during unit testing, but during integration testing, where we want to check if certain business exception has been raised, which could be intercepted by...

This is not if the exceptions are abstracting the underlying cause. Ex: errors for different persistent layers are caught and re-thrown wrapped as an abstract business exception ( empty error,...

I feel a navigation method will be helpful, but it should be something other than `cause` & `rootCause` since they denote immediate cause & root cause. Maybe `forCause`, `forExactCause` navigation...

What are you thoughts on the names `atCause` and `atExactCause` ( or ) `theCause` and `theExactCause`? `assertThat(exception).atCause(MyException.class).hasMessage("...")` `assertThat(exception).theCause(MyException.class).hasMessage("...")`

Am facing the same issue for the same plugin & Gradle version. Observation, the `git.properties` is build alternatively for every clean & build. The following pattern is observed. Note that...

I've tracked the problem to here: https://github.com/mockito/mockito/blob/87e4a4fa85c84cbd09420c2c8e73bab3627708a7/src/main/java/org/mockito/internal/configuration/SpyAnnotationEngine.java#L52-L83 The first time open mocks is run new instances is created here: https://github.com/mockito/mockito/blob/87e4a4fa85c84cbd09420c2c8e73bab3627708a7/src/main/java/org/mockito/internal/configuration/SpyAnnotationEngine.java#L69-L71 But the closable does nothing: https://github.com/mockito/mockito/blob/87e4a4fa85c84cbd09420c2c8e73bab3627708a7/src/main/java/org/mockito/internal/configuration/SpyAnnotationEngine.java#L82 If the next run...

Hey @madkinsz - the main reason it is failing is because - `__prefect_loader__` module isn't available in sys.modules to find the function `bar`. Since the entry `prefect.engine` is called from...

From following function usages - it is either invoked as an app-command or as a subprocess ( via `prefect.engine` );

Let me know if you have any concerns regarding this @madkinsz?