Flushing the send buffer?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 9.9k
- Forks
- 2.1k
- PR merge metrics
- No merged PRs in 30d
Description
Are there any methods for flushing the send buffer? I'm seeing that recv() gets the previously sent command as echo'd by the remote character by character rather than as one slurp. Curious how that can be avoided. Adding a small delay before recv() fixes this, but that's obviously not optimal.
I was looking for some sort of flush method, but I'm not finding one.
Thanks
Contributor guide
No contributing guide indexed for this repository
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
The issue names Paramiko's send buffer and recv() but no repository files or tests. Start by tracing the send/recv path and reproducing the character-by-character echo without the delay. Done means establishing the intended buffering behavior and, if a change is warranted, adding a focused regression test or documenting the supported handling.
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
- 25/100