We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I see two issues with powerslim code which can lead to hangup effect:
This code does not have any checks or error handling for the situation when port is busy:
$ps_server = New-Object System.Net.Sockets.TcpListener($args[0])
It means that based on these specifications:
http://fitnesse.org/FitNesse.UserGuide.SliM.SlimProtocol http://fitnesse.org/FitNesse.UserGuide.SliM.SlimProtocol.PortManagement
Fitnesse will start SlimServer and will be waiting probably forever till SlimServer sends Slim Version string
The second problem is with this code:
$ps_fitnesse_client.Client.Poll(-1, [System.Net.Sockets.SelectMode]::SelectRead)
It does wait forever till Socket gets into the reading mode. IMHO waiting time should be restricted by time out.
The text was updated successfully, but these errors were encountered:
I would start with the appropriate logging into file around the problem areas. Then we could detect what really happens.
Sorry, something went wrong.
SergeyZalyadeev
No branches or pull requests
I see two issues with powerslim code which can lead to hangup effect:
This code does not have any checks or error handling for the situation when port is busy:
It means that based on these specifications:
http://fitnesse.org/FitNesse.UserGuide.SliM.SlimProtocol
http://fitnesse.org/FitNesse.UserGuide.SliM.SlimProtocol.PortManagement
Fitnesse will start SlimServer and will be waiting probably forever till SlimServer sends Slim Version string
The second problem is with this code:
It does wait forever till Socket gets into the reading mode. IMHO waiting time should be restricted by time out.
The text was updated successfully, but these errors were encountered: