Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Issue Reporter: Support configuring data sent to extensions

See original GitHub issue

Continuation of https://github.com/Microsoft/vscode/issues/45673

Now that users can choose to file on extensions, extension authors should be able to specify additional data to include in the report. This could potentially include

User settings
launch.json information
Metadata about the workspace (is it multiroot)
Console errors
Data specific to the extension

Issue Analytics

State:
Created 5 years ago
Reactions:17
Comments:5

Top GitHub Comments

2reactions

rkeithhillcommented, Jul 8, 2018

To add to what @RMacfarlane says, the PowerShell extension would love to supply the PowerShell version info in this issue report. We’d (and I suspect most extension authors) would like to see a list of all loaded extension versions. There is sometimes “interface” between extensions and having this information can help determine if what a user is seeing might be a result of this.

Here is an example of the PowerShell version info and extension info we generate with our extension’s bug report command:

PowerShell Information

Name	Value
PSVersion	5.1.17134.137
PSEdition	Desktop
PSCompatibleVersions	1.0 2.0 3.0 4.0 5.0 5.1.17134.137
BuildVersion	10.0.17134.137
CLRVersion	4.0.30319.42000
WSManStackVersion	3.0
PSRemotingProtocolVersion	2.3
SerializationVersion	1.1.0.1

Visual Studio Code Extensions

Visual Studio Code Extensions(Click to Expand)

Extension	Author	Version
cmake	twxs	0.0.17
code-settings-sync	Shan	2.9.2
cpptools	ms-vscode	0.17.6
csharp	ms-vscode	1.15.2
debugger-for-chrome	msjsdiag	4.7.0
EditorConfig	EditorConfig	0.12.4
githistory	donjayamanne	0.4.1
gitlens	eamodio	8.4.1
html-snippets	abusaidm	0.2.1
PowerShell	ms-vscode	1.7.0
sass-indented	robinbentley	1.4.9
theme-cobalt2	wesbos	2.1.6
tslint	eg2	1.0.33
vscode-eslint	dbaeumer	1.4.12

If we had this and there was a way to invoke the issue reporter programmatically, we would redirect bug report command to pop the issue reporter and probably, over time phase out our bug report command in favor of the built-in one.

1reaction

bwateratmsftcommented, Nov 19, 2020

The Docker extension along with several Azure extensions managed by @EricJizbaMSFT and @StephenWeatherford would really benefit from this as well.

Top Results From Across the Web

3. Turn on Chrome browser reporting - Google Support

Click Settings and then Users & browsers. Select your top-level organizational unit, so that all child organizations will inherit the policy.

App Extension Programming Guide: Handling Common ...

Describes how to develop an app extension, which is an executable that adds functionality to other apps.

Enterprise Reporter 3.2.1 - Configuration Manager ... - Quest Support

You can globally configure Enterprise Reporter to send information collected about Active Directory and Computers, NTFS, Azure Active Directory, Azure Resources ...

Reporting on scenario runs — Dataiku DSS 11 documentation

You can instruct a reporter to send messages at any point of a scenario run: ... Once configured, the integration with DSS supports...

Tracking license usage in multicluster environment with ... - IBM

License Service Reporter is an extension of License Service that aggregates the license usage data from multiple clusters. The collective highest license ...