[Question] Exception handling

[BlackBaroness]

Hi! Is there a way to disable exception logging? The problem is AsyncCache itself prints the log

try {
    Caffeine.newBuilder().asLoadingCache<Any, Nothing> {
        throw Exception() 
        // exception prints itself "[com.github.benmanes.caffeine.cache.LocalAsyncCache] Exception thrown during asynchronous load"
    }.get(Unit)
} catch(Throwable e) {
    // we also get the exception here
}

Of course we can disable the whole Caffeine logging via logger configuration, but it would be nice to just avoid logging somehow

[ben-manes]

Unfortunately for async calls, at least in Java, it is common for a fire-and-forget mentality where the exceptions are swallowed and lost with the CompletableFuture chain. The logging was added due to that user error causing frustration and I've seen a few tickets in OSS projects in response to finding these in their server logs that would otherwise be lost. When your ask comes up its been fine to use logger configuration to filter out what was not or some will return a result object instead which also allows them to implement negative caching.

[BlackBaroness]

Unfortunately for async calls, at least in Java, it is common for a fire-and-forget mentality where the exceptions are swallowed and lost with the CompletableFuture chain. The logging was added due to that user error causing frustration and I've seen a few tickets in OSS projects in response to finding these in their server logs that would otherwise be lost. When your ask comes up its been fine to use logger configuration to filter out what was not or some will return a result object instead which also allows them to implement negative caching.

Thanks for your answer, it's perfectly reasonable to have a logging in async loading Caffeine itself, i just was asking about some kind of solution for aedile specifically, since we don't really use fire-and-forget here. We always get the exception thrown and it usually gets logged by the coroutine scope, so maybe aedile should implement some kind of workaround for that