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
In my project, I like to be able to test what is going on if the connection is down with the remote service, such as here the Storage service.
However, when I try such a test (with a remote down service, using fake implementation service not started), I figured out that I can wait forever (or very long) before the connection is definitively in error and then getting the error from my code.
I did not find any way to configure for instance the ConnectTimeout.
By creating manually the service, inspired from StorageProducer, I am able to adjust this case. I don't think all are needed, but at least the more important.
In my project, I like to be able to test what is going on if the connection is down with the remote service, such as here the Storage service.
However, when I try such a test (with a remote down service, using fake implementation service not started), I figured out that I can wait forever (or very long) before the connection is definitively in error and then getting the error from my code.
I did not find any way to configure for instance the ConnectTimeout.
By creating manually the service, inspired from StorageProducer, I am able to adjust this case. I don't think all are needed, but at least the more important.
The text was updated successfully, but these errors were encountered: