CompletionStage exceptions leak into Mutiny API

[FroMage]

I just got a CompletionException via the Mutiny API, which wraps any exception thrown inside a CompletionStage pipeline. I believe this is very annoying because it means I must wrap all my Uni into an exception mapper that unwraps these silly exception wrappers into their original causes.

Can we make sure the Mutiny API unwrap those when we create a Uni from a CompletionStage?

[cescoffier]

So basically:

Uni.createFrom().completionStage(() -> {

    // ...
	CompletionStage<X> stage = ...

}) 
// automatically added
.onFailure(CompletionException.class).apply(ce -> ce.getCause());

[cescoffier]

Actually, another approach (much better):
In: io.smallrye.mutiny.operators.UniCreateFromCompletionStage#forwardFromCompletionStage

private static <O> void forwardFromCompletionStage(CompletionStage<? extends O> stage,
            UniSerializedSubscriber<? super O> subscriber) {
        subscriber.onSubscribe(() -> stage.toCompletableFuture().cancel(false));
        stage.whenComplete((res, fail) -> {
            if (fail != null) {
                if (fail instanceof CompletionException) {
                    subscriber.onFailure(fail.getCause());
                } else {
                    subscriber.onFailure(fail);
                }
            } else {
                subscriber.onItem(res);
            }
        });
    }

[FroMage]

Yes that's what I had in mind.

[FroMage]

Thanks