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
Copy file name to clipboardExpand all lines: docs/troubleshooting.md
+2-3
Original file line number
Diff line number
Diff line change
@@ -173,6 +173,8 @@ Logs provide context for what was happening when the issue occurred.
173
173
(<kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd>)
174
174
with `PowerShell: Open PowerShell Extension Logs Folder`.
175
175
176
+
> NOTE: Don't forget to also attach the [Language Server Protocol payload logs](#provide-language-server-protocol-payload-logs)!
177
+
176
178
- You can attach your logs to an issue by zipping them and drag/dropping
177
179
them onto your open issue description in the browser.
178
180
@@ -182,9 +184,6 @@ Logs provide context for what was happening when the issue occurred.
182
184
183
185
#### Provide Language Server Protocol payload logs
184
186
185
-
> NOTE: This currently only applies to the PowerShell Preview extension and only if you have version
186
-
> 2019.11.0 or higher.
187
-
188
187
The PowerShell extension works mostly from sending and receiving messages from [PowerShell Editor Services](httos://github.com/PowerShell/PowerShellEditorServices).
189
188
In some cases, getting to the bottom of a bug will require looking at the payloads of these messages. To do this:
0 commit comments