sameersbn / sameersbn/docker-gitlab
The death cycle of SSH2's command
Open
Nobody has claimed this yet.
wontfix
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
When I use the SSH2 nodejs to connect the SSH service on the Windows and execute the "exec" command, the death cycle occurs, and that's why? I'll appreciate it if you help me deal with it!
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 SSH2 Node.js exec command against the Windows SSH service described in the report and capture where the cycle occurs. Compare the client and server behavior; done means identifying the cause and documenting a verified resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100