Longer timeouts stopped working
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 4.4k
- Forks
- 993
- Avg merge
- 9d 21h
- Merged PRs (30d)
- 1
Description
This is very hard to test and describe, however ..
We are using ssh.net (aside of other things) for deploying containers .. such task could take almost hour. In common there are more cascade tasks like this, when some of them fails, whole progress should fail. To be safe, there is 120 minutes command timeout set for every call.
It worked flawlessly, in many cases it properly timeouted after some great internal issue, however, last weeks (let's say since mid of 2017/12), we ran into behaivour where it simply stopped timeouting for this feature. Another calls with shorter timespans (like 5 minutes) timeouts ok.
There wasn't any big changes in code or infrastructure, nor ssh.net update. Using 2016.0 - right now, I've updated to 2016.1 to see if it helps.
So, is there anything I could check or focus on? Is there anyone else experiencing something like this?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported behavior with SSH.NET 2016.1: compare a command using a 120-minute timeout with one using a five-minute timeout, using a long-running deployment-like task. Check whether the longer timeout expires reliably, and document the environment and reproduction steps if it does not.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100