Copying and pasting a comment raised an exception, until I ran Clear-Host

[rhymeswithmogul]

Backtrace

Oops, something went wrong. Please report this bug with the details below.
Report on GitHub: https://github.com/PowerShell/PSReadLine/issues/new

Environment

PSReadLine: 2.0.0-beta4
PowerShell: 7.0.0-preview.3
OS: Microsoft Windows 10.0.18362
Last 200 Keys

 A s s i g n Spacebar a l e r t s @ C L I E N T D O M A I N Spacebar t o Spacebar t h i s . Enter
 Ctrl+Enter ( G e t - A c c e p t e d D o m a i n Spacebar | Spacebar S e l e c t Spacebar - E x p a n d P r o p e r t y Spacebar D o m a i n N a m e ) Spacebar | Spacebar F o r E a c h - O b j e c t Spacebar { Enter
 Ctrl+Enter Spacebar Spacebar Spacebar Spacebar S e t - M a i l C o n t a c t Spacebar " a l e r t s " Spacebar - E m a i l A d d r e s s e s Spacebar @ { A d d = " a l e r t s @ $ _ " } Spacebar - E r r o r A c t i o n Spacebar S t o p Enter
 Ctrl+Enter } Enter
 Ctrl+Enter

Exception

System.ArgumentOutOfRangeException: The value must be greater than or equal to zero and less than the console's buffer size in that dimension. (Parameter 'top')
Actual value was 63.
   at System.ConsolePal.SetCursorPosition(Int32 left, Int32 top)
   at Microsoft.PowerShell.PSConsoleReadLine.MoveCursor(Int32 newCursor)
   at Microsoft.PowerShell.PSConsoleReadLine.MoveToLine(Int32 numericArg)
   at Microsoft.PowerShell.PSConsoleReadLine.PreviousLine(Nullable`1 key, Object arg)
   at Microsoft.PowerShell.PSConsoleReadLine.InsertLineAbove(Nullable`1 key, Object arg)
   at Microsoft.PowerShell.PSConsoleReadLine.ProcessOneKey(PSKeyInfo key, Dictionary`2 dispatchTable, Boolean ignoreIfNoAction, Object arg)
   at Microsoft.PowerShell.PSConsoleReadLine.InputLoop()
   at Microsoft.PowerShell.PSConsoleReadLine.ReadLine(Runspace runspace, EngineIntrinsics engineIntrinsics, CancellationToken cancellationToken)

Environment data

PS version: 7.0.0-preview.3
PSReadline version: 2.0.0-beta4
os: 10.0.18362.1 (WinBuild.160101.0800)
PS file version: 7.0.0.0
BufferWidth: 254
BufferHeight: 63

Steps to reproduce or exception report

Get a nice, full scrollback buffer. Then, paste the text ### Assign alerts@CLIENTDOMAIN to this. into PowerShell 7.0.0-preview3. This one block of code always causes the same problem:

### Assign alerts@CLIENTDOMAIN to this.
(Get-AcceptedDomain | Select -ExpandProperty DomainName) | ForEach-Object {
    Set-MailContact "alerts" -EmailAddresses @{Add="alerts@$_"} -ErrorAction Stop
}

There are some more lines of code before that that all ran fine. However, that comment line caused PSReadLine to fail. The code afterwards ran just fine.

Weirdly enough, after running Clear-Host, everything appeared to be fine. I could paste that in all day.

This might (or might not) be a bug in Windows Terminal. It appeared to work fine when I opened PowerShell 7 with pwsh-preview.

[msftrncs]

@rhymeswithmogul, I have experienced some very weird behavior when pasting in Windows Terminal, but my first suggestion is that you should update to PSReadLine 2.0.0-beta5 from PowerShellGallery, and then see if issues still occur.

Of interesting note here, is that the 'actual value' was equal to the buffer size, and not negative, which has been the normal error in the past.

[rhymeswithmogul]

Nope, the same behavior occurs under 2.0.0-beta5.

[msftrncs]

I seem to be getting the same error if I paste using the right click (sometimes) things that causes the window to scroll off the bottom. This is in addition to weird behavior such as additional blank lines being inserted, including below the final prompt.

What I pasted was:

filter val_2_base33 ([int]$digits = 1) {
    # convert value to base 33 (VIN) string representation
    [int]$value = $_
    [string]$result = ''
    [int]$digs = 0
    while (++$digs -le $digits -or $value -gt 0) {
        $result = '0123456789ABCDEFGHJKLMNPRSTUVWXYZ'[$value % 33] + $result
        $value = [math]::Truncate($value / 33)
    }
    $result
}

Problem doesn't seem to happen if using CTRL-V.

[msftrncs]

I am leaning on this being a Windows Terminal issue...

[rhymeswithmogul]

I am leaning on this being a Windows Terminal issue...

That's what I'm thinking now, too. Right-clicking to paste into pwsh-preview works fine, as does pasting with Control-V in Windows Terminal like you found out.

It's only when you right-click to paste into Windows Terminal and it scrolls the screen that the error occurs. When it happens, you also see extra (or the wrong kind of?) line breaks on the screen, which show up as Enter Ctrl+Enter in the backtrace.

I don't think there's anything PSReadLine can do to work around this, or inform the user that this is a known issue. Hopefully Microsoft fixes it on their end.

[nickdurcholz]

I ran into this as well. Has anyone filed an issue with https://github.com/microsoft/terminal ? I searched for PSReadLine and ArgumentOutOfRange exception, but didn't find anything...

[msftrncs]

I have posted an issue there, but I think there might be some bugs in PSReadline that could use to be solved. In this case, the exception is occurring because PSReadline is attempting for 'render' past the bottom of the screen.

This exception can be easily reproduced in such terminals, by just pressing CTRL-ENTER or CTRL-J until the new lines extend to the bottom of the terminal,

[msftrncs]

This is being tracked as microsoft/terminal#1091.

[msftrncs]

I am able to reproduce the exception report in VS Code using the method I outlined above. In VS Code, I disabled the default CTRL-J keybinding so it could be exposed to the terminal, which then sends a CTRL-ENTER combination instead, and when the cursor flows off the top of the screen, the exception is reported. Its too bad both VS Code and Windows Terminal send CTRL-ENTER in place of CTRL-J.

[msftrncs]

I am able to reproduce the exception report in VS Code using the method I outlined above. In VS Code, I disabled the default CTRL-J keybinding so it could be exposed to the terminal, which then sends a CTRL-ENTER combination instead, and when the cursor flows off the top of the screen, the exception is reported. Its too bad both VS Code and Windows Terminal send CTRL-ENTER in place of CTRL-J.

Note, the lines below the cursor must be empty, if they are not, it will just beep when the buffer becomes full.

[msftrncs]

Note, the lines below the cursor must be empty, if they are not, it will just beep when the buffer becomes full.

I think I have determined the conditions for the reproduction to be more consistent. The cursor must be on the prompt line, or the first line after the prompt, with the buffer (screen) already full of lines, so that the prompt line is at the top. Using CTRL-ENTER (CTRL-J in Windows Terminal or VS Code Terminal), the first time you get a beep, and the prompt line disappears, and the second time the ArgumentOutOfRangeException occurs. If the cursor is anywhere else, no exception. The content on the buffer doesn't seem to matter.

Also, another quirk potentially related to this, is that if the cursor is in the second line of the buffer, when CTRL-ENTER occurs, the cursor is moved to the first line (prompt line). That's exactly where the cursor is when the exception occurs, its on the second line because the prompt scrolled off the top.