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
The following configuration is very similar to the default one but replaces one of the URLs with an unreachable one that would produce a thrown URLError during URLSession's dataTask.
According to my testing the thrown URLError happens pretty quickly and with the current implementation it will make the MergeMany publisher to complete (here)and this way cancelling all remaining/ongoing URL requests. Despite of requiring less then 100% as success threshold only one early-failing request with a thrown error can stop the MergeMany publisher and leave the ConnectivityResult in an incomplete state - that is returned to the subscriber of ConnectivityPublisher.
So in case of the example I provided above only one failed URL request results in a disconnected state despite of setting only 50% as a success threshold.
Could you please check the example and give some feedback if you also consider it as a bug?
The text was updated successfully, but these errors were encountered:
The following configuration is very similar to the default one but replaces one of the URLs with an unreachable one that would produce a thrown URLError during URLSession's dataTask.
According to my testing the thrown URLError happens pretty quickly and with the current implementation it will make the MergeMany publisher to complete (here)and this way cancelling all remaining/ongoing URL requests. Despite of requiring less then 100% as success threshold only one early-failing request with a thrown error can stop the MergeMany publisher and leave the ConnectivityResult in an incomplete state - that is returned to the subscriber of ConnectivityPublisher.
So in case of the example I provided above only one failed URL request results in a disconnected state despite of setting only 50% as a success threshold.
Could you please check the example and give some feedback if you also consider it as a bug?
The text was updated successfully, but these errors were encountered: