Skip to content
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

Support filing issues against extensions within the issue reporter #45673

Closed
RMacfarlane opened this issue Mar 13, 2018 · 5 comments
Closed

Support filing issues against extensions within the issue reporter #45673

RMacfarlane opened this issue Mar 13, 2018 · 5 comments
Assignees
Labels
issue-reporter Issue reporter widget issues on-testplan plan-item VS Code - planned item for upcoming
Milestone

Comments

@RMacfarlane
Copy link
Contributor

Add the ability to report issues with installed extensions

@RMacfarlane RMacfarlane added plan-item VS Code - planned item for upcoming issue-reporter Issue reporter widget issues labels Mar 13, 2018
@RMacfarlane RMacfarlane added this to the March 2018 milestone Mar 13, 2018
@RMacfarlane RMacfarlane self-assigned this Mar 13, 2018
@DonJayamanne
Copy link
Contributor

Would it be possible to provide some extension points to this.
E.g. if a user is reporting an issue against extension x, then extension x can request additional information from the user.

This is very useful at least for the Python Extension, where we'd like to determine the version of Python the user has.

@RMacfarlane
Copy link
Contributor Author

@DonJayamanne Yes, this would be a great place for extension points! Ideally the info sent from the reporter and even the UI should be extensible. I don't think the first pass of this feature will have this as there needs to be more planning on what the API looks like.

Do you have any other examples of additional information that would be useful?

@DonJayamanne
Copy link
Contributor

These are some of the information we generally request. I believe all of the following are generic and would apply to all extensions (possibly making them optional).

  • When debugging we ask users to upload their launch.json
  • We ask users to upload their workspace settings settings.json
  • We try to identify whether a user is working in a multi-root workspace
  • We ask for errors that are displayed in the console window (Help -> Toggle Developer Tools)

Finally here are some questions specific to the Python extension:

  • Python version (& distribution if applicable, e.g. Anaconda): XXX
  • Type of virtual environment used (N/A | venv | virtualenv | conda | ...): XXX
  • Relevant/affected Python packages and their versions: XXX
  • Output for Python in the Output panel (ViewOutput, change the drop-down the upper-right of the Output panel to Python)

@brettcannon
Copy link
Member

The stuff we currently request in our issue template covers what we typically ask for. Basically we ask for platform info, a bunch of Python-specific details, code that reproduces the issue, and then the usual Output and Console stuff. After that we often ask for a person's settings.json and launch.json. And finally after that sometimes a screenshot or video of what's occurring.

@RMacfarlane
Copy link
Contributor Author

@DonJayamanne @brettcannon Thanks for the additional info! I've filed #46726 to track this.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue-reporter Issue reporter widget issues on-testplan plan-item VS Code - planned item for upcoming
Projects
None yet
Development

No branches or pull requests

3 participants