-
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
Do I need to open issues on these crashes or do you get telemetry ? #3091
Comments
This is an issue with the VSCode editor service. Close this one as a duplicate of PowerShell/vscode-powershell#3701 |
Thanks @daxian-dbw I was mainly interested if you would be getting telemetry of these crashes? or if it's still helpful in many cases to open an issue? |
@brwilkinson PSReadLine itself doesn't collect any telemetry due to privacy concerns, so yes, it would be very helpful if you can open an issue when PSReadLine emits an exception report 😄 Thank you in advance! In theory, we may consider adding telemetry in future, but the telemetry data cannot contain any of the "Last 200 keys" as is shown in the exception report because that's sensitive data. Also, we won't have the additional information like the screenshot and repro steps. Those information as well as the interactions with the issue author are all very helpful for the issue investigation. |
Thanks Dongbo, that makes sense. |
Prerequisites
Exception report
Screenshot
Terminal was idle
Environment data
Steps to reproduce
install PSReadLine: 2.2.0-beta4
This is just crashing and looping on it's own, even when I am not running a command.
Expected behavior
not crash
Actual behavior
crash
The text was updated successfully, but these errors were encountered: