-
Notifications
You must be signed in to change notification settings - Fork 300
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
System.ArgumentOutOfRangeException #2272
Comments
@pluma9 Thanks for reporting this issue. Did you see this in VS Code terminal? Can you please provide repro steps? |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
No, I see this in Windows Terminal (version 1.7.572.0). I'm not sure if this helps, but here's my PSReadLine configuration: Set-PSReadLineOption -BellStyle None
Set-PSReadLineOption -EditMode Vi
Set-PSreadLineOption -PredictionSource HistoryAndPlugin
Set-PSreadLineOption -PredictionViewStyle InlineView
Set-PSReadLineKeyHandler -Function SwitchPredictionView -Chord 'F2' For repro steps, I haven't tried typing those last 200 keys. I encountered this while playing around with a few Powershell commands. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
As for the issue, I see very strange tail in last 200 keys that is " |
Yes. I don't understand why this comes from the user side. He switched to VI mode with hot keys and got an exception? I see so many situations where SetCursorPosition raises an exception the reason for which is impossible to understand, that this suggests that we need to come up with some kind of smart replay so that the problem can always be reproduced. |
@daxian-dbw I see a lot of questions where regular stack trace is not that useful. What if we implement our own stack trace where we include argument values and other useful information? This could make it much easier to reproduce issues. Second suggestion is to implement "Cloud run" as start PSRL - check new version in Cloud - download new version in local cache if presents - run new version, otherwise run pre-installed old version. Of course it should be smarter than this short description. This could get rid of a lot of old versions and outdated issues. |
This comment has been minimized.
This comment has been minimized.
Given that we cannot reproduce the issue, there is no further action can be taken at this point. For now, I will close this issue. @pluma9 if you run into a similar issue again, please report again, with the screenshot and describe the operations that lead to the exception state, as detailed as possible. Thank you! |
Environment
PSReadLine: 2.2.0-beta1
PowerShell: 7.1.2
OS: Microsoft Windows 10.0.18363
BufferWidth: 82
BufferHeight: 52
Last 200 Keys
Exception
The text was updated successfully, but these errors were encountered: