mirror of
https://github.com/google/nomulus.git
synced 2025-05-07 23:38:21 +02:00
552940a816
'afterFinalFailure' is called just before rethrowing a non-retrying error from
the retrier. This can happen either because the exception shouldn't be retried,
or because we exceeded the maximum number of retries.
The same thing can be done by catching that thrown error outside of the
retrier:
retrier.callWithRetry(
callable,
new FailureReporter() {
@Override
void afterFinalFailure(Throwable thrown, int failures) {
// do something with thrown
}
},
RetriableException.class);
is (almost) the same as:
try {
retrier.callWithRetry(callable, RetriableException.class);
} catch (Throwable thrown) {
// do something with thrown
throw thrown;
}
("almost" because the retrier might wrap the Throwable in a RuntimeException,
so you might need to getCause or getRootCause. Also - there is the
"beforeRetry" I ignored for the example)
Removing "afterFinalFailure" also makes the FailureReporter in line with Java 8
functional interface - meaning we can more easily create it when we do need to
override "beforeRetry".
-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=189972101
|
||
|---|---|---|
| .. | ||
| BUILD | ||
| CidrAddressBlockTest.java | ||
| CollectionUtilsTest.java | ||
| ComparingInvocationHandlerTest.java | ||
| ConcurrentTest.java | ||
| DateTimeUtilsTest.java | ||
| DiffUtilsTest.java | ||
| DomainNameUtilsTest.java | ||
| HexDumperTest.java | ||
| PosixTarHeaderSystemTest.java | ||
| PosixTarHeaderTest.java | ||
| RequestStatusCheckerImplTest.java | ||
| RetrierTest.java | ||
| SerializeUtilsTest.java | ||
| SqlTemplateTest.java | ||
| TaskEnqueuerTest.java | ||
| TeeOutputStreamTest.java | ||
| TypeUtilsTest.java | ||
| UrlFetchUtilsTest.java | ||