MarketSquare / MarketSquare/SSHLibrary

Write takes argument from the last Write keyword executed

Open
#427 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
167
Forks
145
PR merge metrics
No merged PRs in 30d

Description

This is a similar, if not identical issue to [issue387](https://github.com/robotframework/SSHLibrary/issues/387).

I have the following keyword sequence:

```
Write source /home/file\n
Read Until Prompt strip_prompt=True
Write rm -rf /path/to/some/other/dir
Read Until Prompt strip_prompt=True
```

The TRACE return of the second Write keyword is:
`TRACE Return: ' source /home/file\r\n'`
and the TRACE return of the second Read Until Prompt keyword is:
`TRACE Return: 'rm -rf /path/to/some/other/dir\r\n'`

So it seems that the argument of the first Write keyword was queued on the remote system, and the second Write keyword argument was returned as the stdout of itself (rm -rf /path/to/some/other/dir had a stdout of rm -rf /path/to/some/other/dir)

Any help is appreciated

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the reported sequence of Write and Read Until Prompt keywords and inspect their TRACE returns, comparing the behavior with issue387. Done means consecutive Write calls no longer return an earlier argument and Read Until Prompt returns the expected remote output.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.