<tl/dbr>
Remove extra text from "Contains" statement that breaks the intention
details
Currently this method contains the following code (I assume to allow some time for the separate process to startup and start listening on the specified socket/port
<tl/dbr> Remove extra text from "Contains" statement that breaks the intention
details Currently this method contains the following code (I assume to allow some time for the separate process to startup and start listening on the specified socket/port
I ran into a scenario where my 1st call always failed (see below) but the 2nd one succeeded.
The issue is that the number after the exception for me was different then the hardcoded string (10061) in source code
I resolved this by removing that trailing text
(10061)
in the Contains clause