AddForwardedPort with ForwardedPortLocal does not throw exception if no connect possible
Open
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 4.4k
- Forks
- 993
- Avg merge
- 9d 21h
- Merged PRs (30d)
- 1
Description
This happens with 2016.1.0-beta-1.
On a connected SSH session I am calling AddForwardedPort() like in the examples with these parameters:
ForwardedPortLocal("127.0.0.1", 25, "127.0.0.1", 25);
(Port 25 is just used as an example here)
- If the service on the remote host is up there is nothing to complain - it just works.
- But if the service on the remote host is down, I do not get any feedback about the unsuccessful forwarding.
I tried polling the 'IsStarted' property with no success.
I subscribed to the exception before calling Start() on the port - also with no success.
Any ideas?
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 at the AddForwardedPort(), ForwardedPortLocal, IsStarted, and Start() entry points described in the report. Reproduce forwarding to an unavailable remote service and trace how connection failures are surfaced; done means an unsuccessful forwarding attempt provides observable exception or failure feedback.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100