Unexpected error in VS Code terminal using PSReadLine”

[Muskan250-pixel]

Prerequisites

• Write a descriptive title.
• Make sure you are able to repro it on the latest released version
• Search the existing issues, especially the pinned issues.

Exception report

Oops, something went wrong.  Please report this bug with the details below.
Report on GitHub: https://github.com/lzybkr/PSReadLine/issues/new
-----------------------------------------------------------------------
Last 5 Keys:
 & Space " C :

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 name: left
   at System.Console.SetCursorPosition(Int32 left, Int32 top)
   at Microsoft.PowerShell.Internal.VirtualTerminal.set_CursorLeft(Int32 value)
   at Microsoft.PowerShell.PSConsoleReadLine.ReallyRender(RenderData renderData, String defaultColor)
   at Microsoft.PowerShell.PSConsoleReadLine.ForceRender()
   at Microsoft.PowerShell.PSConsoleReadLine.Insert(Char c)
   at Microsoft.PowerShell.PSConsoleReadLine.SelfInsert(Nullable`1 key, Object arg)
   at Microsoft.PowerShell.PSConsoleReadLine.ProcessOneKey(ConsoleKeyInfo key, Dictionary`2 dispatchTable, Boolean ignoreIfNoAction, Object arg)
   at Microsoft.PowerShell.PSConsoleReadLine.InputLoop()
   at Microsoft.PowerShell.PSConsoleReadLine.ReadLine(Runspace runspace, EngineIntrinsics engineIntrinsics)
-----------------------------------------------------------------------

Screenshot

I encountered an error in the terminal while running my code in Visual Studio Code.

The error message that appeared was:

"Oops, something went wrong. Please report this bug with the details below."

After this message showed up, my code still ran successfully. The terminal gave this exception before executing the code properly.

I’m using the integrated PowerShell terminal in VS Code. The error doesn’t seem to stop the code from running, but I wanted to report it just in case it points to a deeper issue.

Thanks in advance for your help!

Environment data

EditMode                               : Windows
AddToHistoryHandler                    : 
HistoryNoDuplicates                    : True
HistorySavePath                        : C:\Users\Raunak Ji\AppData\Roaming\Microsoft\Windows\PowerShell\PSReadLine\ConsoleHost_history.txt
HistorySaveStyle                       : SaveIncrementally
HistorySearchCaseSensitive             : False
HistorySearchCursorMovesToEnd          : False
MaximumHistoryCount                    : 4096
ContinuationPrompt                     >> 
ExtraPromptLineCount                   : 0
...

Name                           Value
----                           -----
PSVersion                      5.1.19041.5737
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.19041.5737
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

Steps to reproduce

1.Open Visual Studio Code.
2. Open the PowerShell terminal in VS Code (via the Terminal menu or Ctrl +blacktick shortcut).
3. Type or paste the code you want to execute in the PowerShell terminal.
4. Press Enter to run the code.
5. You should see an error message similar to:

"Oops, something went wrong. Please report this bug with the details below."
6. Observe: Despite the error message, the code will still run successfully

Expected behavior

The code should run without displaying any error message. The terminal should execute the code and show the expected output without any interruptions or error prompts.

Actual behavior

"Oops, something went wrong. Please report this bug with the details below."

Despite this error message, the code still runs successfully, and the expected output is displayed.

[Muskan250-pixel]

No Comment

[github-actions]

This issue was already fixed (see #1306). Please upgrade to the 2.3.5 version of PSReadLine from PowerShell Gallery.
See the upgrading section for instructions. Please let us know if you run into the same issue with the latest version.