You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yeah it doesn't sound like this is needed at all for a Mono publisher. Note that it would be necessary if the MonoToCompletableFuture (which is a Subscriber) was subscribed to eg. a Flux...
What I can do to guide any potential future use of this subscriber with anything else than a Mono is to add a constructor parameter that drives whether or not to cancel in onNext. (and of course Mono.toFuture() would prevent such cancellation).
We have a code like below which does the following:
This works fine. The issue we're facing is when we convert this Mono to a Future like below:
toFuture()
operator cancels the Mono as soon as the Mono completes, which result in the removal of successfully completed file.Code in
toFuture()
operator that cancel the Mono is here.The text was updated successfully, but these errors were encountered: