You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Let's consider creating a means to make it easier for an end-user to gather all the relevant info a developer would use to debug an issue.
This could be similar in principle to the must-gather tool.
To start, we could publish an IDE command (maybe provide a button) that will help a user by gathering all relevant information needed to debug an issue. This likely becomes a compress the .vscode directory.
Concerns:
We would want to be sure we are not logging by accident any PII data, API Keys are a first concern I worry about. (In theory we do not log this)
If we are to include the optional trace data for request/response written to disk, that would contain the user's source code which they may not be comfortable to share.
The text was updated successfully, but these errors were encountered:
Thank you @savitharaghunathan for suggesting we explore this as a concept.
Let's consider creating a means to make it easier for an end-user to gather all the relevant info a developer would use to debug an issue.
This could be similar in principle to the must-gather tool.
To start, we could publish an IDE command (maybe provide a button) that will help a user by gathering all relevant information needed to debug an issue. This likely becomes a compress the
.vscode
directory.Concerns:
The text was updated successfully, but these errors were encountered: