Updated bug_report.md (#5668)
* Updated bug_report.md * Unified logging to Feedback Hub * Updated anchors * Added feature label to feature_request.md * Update bug_report.md can->may pedantry Co-authored-by: therealkenc <ken@virtru.com>
Craig Loewen committed
Aug 14, 2020 at 08:33 UTC
b02b6219b18536d1ad087fbd574cda28d2745793
3 files changed
+11
-37
.github/ISSUE_TEMPLATE/bug_report.md
+5
-1
@@ -15,6 +15,7 @@ I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING:
15
3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number).
16
4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement.
17
5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement.
18
+6. If I file an issue without collecting logs, the WSL team may close my issue without further explanation or engagement.
19
20
All good? Then proceed!
21
-->
@@ -49,9 +50,12 @@ Whether the issue is on WSL 2 and/or WSL 1: [run `cat /proc/version` in WSL]
50
If you'd like to provide logs you can provide an `strace(1)` log of the failing command (if `some_command` is failing, then run `strace -o some_command.strace -f some_command some_args`, and link the contents of `some_command.strace` in a gist.
51
More info on `strace` can be found here: https://www.man7.org/linux/man-pages/man1/strace.1.html
52
You can use Github gists to share the output: https://gist.github.com/
53
+-->
54
53
-Additionally, For WSL launch issues, please collect detailed logs, instructions here: https://github.com/Microsoft/WSL/blob/master/CONTRIBUTING.md#8-detailed-logs
55
+<!--
56
+Collect WSL logs by following these instructions: https://github.com/Microsoft/WSL/blob/master/CONTRIBUTING.md#8-detailed-logs
57
-->
58
+**WSL logs**:
59
60
# Expected behavior
61
.github/ISSUE_TEMPLATE/feature_request.md
+1
-1
@@ -2,7 +2,7 @@
2
name: Feature request
3
about: Suggest a feature for Windows Subsystem for Linux
4
title: ''
5
-labels: ''
5
+labels: 'feature'
6
assignees: ''
7
8
---
CONTRIBUTING.md
+5
-35
@@ -93,42 +93,12 @@ Common files are:
93
```
94
$ strace -ff -o <outputfile> <command>
95
```
96
+<!-- Preserving anchors -->
97
+<div id="8-detailed-logs"></div>
98
+<div id="9-networking-logs"></div>
99
97
-### 8) Detailed Logs
98
-Some bugs will require more detailed logs to help determine the cause. There is a command to start detailed logging and another to stop. The logs are generated locally into the working directory.
99
-
100
-#### Start collecting logs
101
-
102
-```
103
-logman.exe create trace lxcore_kernel -p "{0CD1C309-0878-4515-83DB-749843B3F5C9}" -mode 0x00000008 -ft 10:00 -o .\lxcore_kernel.etl -ets
104
-logman.exe create trace lxcore_user -p "{D90B9468-67F0-5B3B-42CC-82AC81FFD960}" -ft 1:00 -rt -o .\lxcore_user.etl -ets
105
-logman.exe create trace lxcore_service -p "{B99CDB5A-039C-5046-E672-1A0DE0A40211}" -ft 1:00 -rt -o .\lxcore_service.etl -ets
106
-```
107
-
108
-#### Stop collecting logs
109
-
110
-```
111
-logman.exe stop lxcore_kernel -ets
112
-logman.exe stop lxcore_user -ets
113
-logman.exe stop lxcore_service -ets
114
-```
115
-
116
-#### Generated log files
117
-
118
-The files generated will be in the directory where the above commands ran. The files will be named:
119
-
120
-```
121
-lxcore_kernel.etl
122
-lxcore_service.etl
123
-lxcore_user.etl
124
-```
125
-
126
-#### Submitting logs
127
-
128
-To submit the details logs, attach them to your GitHub issue.
129
-
130
-### 9) Networking Logs
131
-For bugs that are related to networking, you can provide networking logs using the Feedback hub with the following steps.
100
+### 8) Collect WSL logs
101
+To collect WSL logs follow these steps:
102
103
#### Open Feedback Hub and enter the title and description of your issue
104