-
Notifications
You must be signed in to change notification settings - Fork 302
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When upgrading from PSReadLine 2.1 to 2.2, Pasting on remote machines gets slow towards end #3879
Comments
Looks like your video may have been cut off as its <1 second for me, however I dont seem to have slow pasting on my Mac PSReadLine version 2.3.4, can you see if 2.3.4 also has this issue? Perhaps there is some delay since you are remoting in? |
Same behavior on 2.3.4. It can't be just a matter of being a remote connection alone, because it works fine on 2.2.0-beta4 and earlier. Also, if it were a relatively consistent delay through the entire paste, I could see that as being "remote" caused. But that's not the case. It's "first chunk = full speed" followed by "last several characters one at a time" But the behavior I'm seeing isn't that. And if I copy/paste the lines so there are 50 lines instead of 5, it's the same exact behavior... all lines go instantly until after the Every published version from 2.2.0-beta5 has this behavior. No published version before it has it. Not sure what the deal is with the video... if you right-click to download it and you view it locally does it also get stuck at the first frame? |
I've tried to test the exact scenario locally (without a remote host) but I can't replicate it exactly on my M1 Mac. If I use the same docker image with Powershell 7.3 or above, it fails because of .Net incompatibility with Rosetta. And if I build a container locally that doesn't require rosetta, it works fine and snappily... except since it's not running on a different platform, I can't rule out the "remote" angle, since I'd need the same platform on both sides. |
I was able to track down a Windows host where I could install Docker and run the same image, and I didn't see the "instant start, slow finish" behavior. So this does seem like something that changed between 2.2.0-beta4 and 2.2.0-beta5 impacted remote session behavior. I just tested is in iTerm2 on my Mac, so it's not Terminal.app specific. I don't have a handy remote host other than RHEL8 based to test with, so I don't know if it's sensitive to Linux distro. |
I wrote up an issue in PowerShell repository before realizing (with the help of a Microsoft Engineer) that the root of the issue lied within the PSReadLine module. Basically we are seeing the exact same think as @wonkifier. If you see my screenshots in the issue linked above, you will see that the websocket messages being sent to and from the pwsh process are significantly different in v2.2.0-beta5 than v2.2.0-beta4. This increase in traffic results in a "lag" to the user which is exacerbated if they are already in a high latency situation (e.g. client is geographically distant from the hosted machine). I plan to review the changes made there to see if I can spot what could have caused this, but my guess is its by-design for some other requirement and so a "fix" might not be entirely trivial. |
Hi Dongbo! I know this code was written a while ago, but I am curious if you could take a look at this issue (also see my write-up in this issue) and see if in of the changes you made here line up with the behavior we are seeing. Appreciate any insight into whether or not this is truly a bug or something by-design that will not be fixed. Thanks |
@mhintzke Thanks for the detailed issue description in PowerShell/PowerShell#24696, especially the screenshots of the before vs. after comparison. I believe this regression is caused by this line of code in the PSReadLine/PSReadLine/Render.cs Line 931 in 9e946af
The PTY on server side should be able to buffer the writes to terminal, but it has to send out all buffered bytes when there is a READ request, such as querying for cursor position. Can you try the changes in daxian-dbw@1071070 (the lagging branch) and see if it mitigates the issue? |
@daxian-dbw This makes sense and would definitely correlate to the usage of "copy/paste" since the cursor will move 1 space each character that is inserted into the terminal. I can definitely give this a try, I will just need some time to build the module and get your change into our system. Appreciate you taking a look for us! I will update here ASAP. |
@daxian-dbw I have tested your changes in our environment and I'm afraid the issue still exists. (see results in image of Get-Module showing 2.4.0 beta version of PSReadLine which is your commit) Here is a GIF of the behavior still. First I copy paste a small string of text and you can see the "lag". Then I remove it and paste in a longer string of text. For some reason, only the last couple of characters appear to be slow. This seems to be constant as I can paste in a very large string and 95% of it will show up instantly, and the last 5% "lag" and come in slowly. For reference, here is the same test using 2.1.0 Please let me know if there is any more I can do to help you troubleshoot! |
Thanks @mhintzke for the follow-up. Can you share another screenshot of the picture 1 (the captured traffic) with the "data" section to be fully displayed? One question, when you paste the string, do you use |
@daxian-dbw Here are 2 screenshots showing the entire set websocket messages from pasting in And here is my best attempt at copying the raw data in case you want to use it at all.
|
Prerequisites
Exception report
N/A
Screenshot
SlowPaste220b5.mov
Environment data
Steps to reproduce
#- Create a text file/window with the following sample contents to copy from
pwsh
Steps I used to change version of PSReadline:
Expected behavior
The entire contents of the past should be "instant", no slowdown at the end.
Actual behavior
Refer to attached video... The first portion of the paste is instant, then the latter portion appears as if it's being typed out by hand
The text was updated successfully, but these errors were encountered: