Endless read
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- node.js, typescript
- Domain
- networking
Research direction
No file or test is named. Start by tracing requestShell and the shell stream lifecycle, then reproduce the example with and without shell.end; done means establishing whether endless pushed output is supported and documenting or correcting the observed behavior.
Written by the indexing model from the issue text.
Description
Hi,
I'm trying to open the shell which writes a command to the host and gets endless push updates.
In command-line it will be like:
~> ssh {user}@{host} -p{port} -T -i {private key path}
~>
~> -- pushed from the host side
~> .....
While trying to do so with your package, like,
const { NodeSSH } = require('node-ssh')
const client = new NodeSSH()
function wait(delay) {
return new Promise(function (resolve) {
setTimeout(resolve, delay)
})
}
var intcommand = JSON.stringify({ ... })
client.connect({
host: {host},
port: {port},
username: {username},
privateKey: {private key path}
})
.then(async function () {
const data = []
const shell = await client.requestShell()
shell.on('data', function (chunk) {
console.log(chunk.toString('utf8'));
data.push(chunk.toString('utf8'))
})
shell.write(intcommand)
await wait(50)
shell.end(cb=>{
console.log('shell ended: ', cb == undefined?'':cb);
})
})
Now.
It retrieves the first raw and close.
How can I push my request to the host and keep it open to consume the endless pushed feed?
it seems that it works only while write the command and call end.
What am I missing here?
Please advise
- Dominant language
- TypeScript
- Stars
- 1k
- Forks
- 94
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from steelbrain/node-ssh
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
steelbrain/node-ssh#487 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
steelbrain/node-ssh#482 · 3 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
steelbrain/node-ssh#474 · 3 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
steelbrain/node-ssh#473 · 1 comment · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
steelbrain/node-ssh#472 ·
All issues in steelbrain/node-ssh
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
cli: `execCargoMetadata` decodes stdout per chunk, corrupting non-ASCII paths across pipe boundariesOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 62/100
lingdojo/kana-dojo#34127 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
osmlab/name-suggestion-index#13104 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100