‘Report issue’ button on ‘Running extensions’ causes tens of duplicate issues

[kachkaev]

• VSCode Version: 1.31.1
• OS Version: macOS 10.14.3

Steps to Reproduce

1. Open Running extensions

2. Press Report Issue. You are now just one step away from creating an army of these: https://github.com/prettier/prettier-vscode/issues?utf8=✓&q=is%3Aissue+Extension+causes+high+cpu+load.

Expected behaviour

I'd like VSCode to search for Extension causes high cpu load in the repo and show Report issue button only if no open issues are found. Otherwise, I'd like it to take me to the exiting issue so that I could +1 it or add a comment. I remember Atom following this logic when there is an unhandled exception coming out of an extension.

[roblourens]

I would close any of these which don't have a profile attached. Personally I find it annoying when I am investigating one issue involving high cpu, and many other people with different issues pile on just because their issue also involves high cpu.

[jrieken]

Yes, this is very good feedback. I have also thought about it and I feel bad for extensions that get spammed this these issues. Totally +1 for closing issues without profiles and also +1 for making performance fixes but by now I think that we should collect perf issues and file them, esp since its often hard to understand and often needs our consulting anyways.

[jrieken]

#71290 and #71381 are both issues with extensions we ship. Ironically we don't encourage users to file issues for them... I would love to be able to simple collect those profile on our behalf but I am unsure if telemetry is fit for that

[jrieken]

We should look at total_count of this https://api.github.com/search/issues?q=is:issue+in:title+repo:prettier/prettier-vscode+state:open+Extension+causes+high+cpu+load

[kachkaev]

I thought one could get the same result via the GitHub's GraphQL endpoint and thus avoid massive overfetching, but unfortunately the only works for authenticated users 😢

https://api.github.com/graphql?query={search(type:%20ISSUE,%20query:%20%22repo:prettier/prettier-vscode%20state:open%20in:title%20Extension+causes+high+cpu+load%22){issueCount}}

Query

{
  search(type: ISSUE, query: "repo:prettier/prettier-vscode state:open in:title Extension+causes+high+cpu+load") {
    issueCount
  }
}

Result

{
  "data": {
    "search": {
      "issueCount": 29
    }
  }
}

You can try this out in the Github GraphQL API explorer. Shame that the authentication requirement renders use of GraphQL inapplicable in this case, but it might be useful elsewhere 🤷‍♂️