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
Should Future.failedFuture always return a failed future?
At present failedFuture(null) returns a succeeded future.
Agree that we should never call failedFuture with null, but it can happen by accident ... and depending on the complexity of the system, finding the root cause can take some time.
Also perhaps, calling Future.fail(null) should really set the cause to NoStackTraceThrowable.
The text was updated successfully, but these errors were encountered:
A question from our team:
Should
Future.failedFuture
always return a failed future?At present
failedFuture(null)
returns a succeeded future.Agree that we should never call failedFuture with null, but it can happen by accident ... and depending on the complexity of the system, finding the root cause can take some time.
Also perhaps, calling
Future.fail(null)
should really set the cause toNoStackTraceThrowable
.The text was updated successfully, but these errors were encountered: