-
Notifications
You must be signed in to change notification settings - Fork 29.4k
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
Error reporter cannot send data directly to GitHub #100054
Comments
I see in this issue (#73921) that it is performance-related, however I don't think this adresses the UX issues that are present (issue template info, system info, etc.) Apologies if this is too close to that issue! |
Hey @peterkos, here's an explanation of why dialog appears: #97171 (comment) The limit is based on number of characters, not bytes, and is unfortunately pretty easy to hit with just system info/extensions. I'm not seeing what you describe with that information not being copied when you click "OK" in the dialog - all of the diagnostic information should be copied to the clipboard at that time. What version of VS Code are you using? |
Thanks for the info! That makes a bit more sense. I'm using VSCode version 1.46.0; also updated my original post. Also I think that was my fault; I tried again (a few times to make sure) and it does indeed copy all info. I must have copied the steps to reproduce myself, overwriting the clipboard 😅 |
I'm going to go ahead and close this, since the copy to clipboard functionality is working |
This still seems like a usability issue to force the user to copy&paste, even though I understand the technical limitation there. (For anyone browsing, to save some digging, see #95165 for discussion on bypassing the limitation.) |
Attempting to send any somewhat-detailed bug report gives this error:
I tried to send the following message:
Two main concerns here.
First, this is around 319 bytes of UTF-8 for "Steps to Reproduce". Is this a GitHub API limitation of some sort? This is very strange and I've never seen an application do this.
Second, I think this is really bad UX:
The text was updated successfully, but these errors were encountered: