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
about: Create a bug report for a bug you found in wechaty
4
-
5
4
---
6
5
7
-
> Important:Please file the issue follow the template, or we won't help you to solve the problem.
8
-
6
+
> Important:Please file the issue follow the template, or we won't be able to help you to solve the problem.
9
7
10
8
## 0. Report Issue Guide
11
9
12
10
1. Please run the following command and check whether the problem has been fixed:
13
-
```
14
-
rm -rf package-lock.json
15
-
rm -rf node_modules
16
-
npm install
17
-
```
18
11
19
-
2. Please search in [FAQ List](https://docs.chatie.io/faq) first, and make sure your problem has not been solved before.
12
+
```sh
13
+
rm -rf package-lock.json
14
+
rm -rf node_modules
15
+
npm install
16
+
```
17
+
18
+
2. Please search in [FAQ List](https://wechaty.js.org/faq) first, and make sure your problem has not been solved before.
20
19
21
20
3. Please search in the issue first, and make sure your problem had not been reported before
22
21
23
22
## 1. Versions
24
-
- What is your wechaty version?
23
+
24
+
> What is your wechaty version?
25
+
25
26
Answer:
26
27
27
-
- Which puppet are you using for wechaty? (padchat/puppeteer/padpro/...)
28
+
> Which puppet are you using for wechaty? (puppeteer/padlocal/service...)
29
+
28
30
Answer:
29
31
30
-
- What is your wechaty-puppet-XXX(padchat/puppeteer/) version?
32
+
> What is your wechaty-puppet-XXX(padchat/puppeteer/) version?
33
+
31
34
Answer:
32
35
33
-
- What is your node version? (run `node --version`)
36
+
> What is your node version? (run `node --version`)
37
+
34
38
Answer:
35
39
36
-
- What os are you using
40
+
> What os are you using
41
+
37
42
Answer:
38
43
39
44
## 2. Describe the bug
40
-
Give a clear and concise description of what the bug is.
45
+
46
+
> Give a clear and concise description of what the bug is.
41
47
42
48
## 3. To Reproduce
43
-
This part is very important: if you can not provide any reproduce steps, then the problem will be very hard to be recognized.
49
+
50
+
> This part is very important: if you can not provide any reproduce steps, then the problem will be very hard to be recognized.
51
+
52
+
**[How to create a Minimal, Reproducible Example](https://stackoverflow.com/help/minimal-reproducible-example)**
44
53
45
54
Steps to reproduce the behavior:
55
+
46
56
1. run '...'
47
57
2. ...
48
58
3. ...
49
59
50
60
## 4. Expected behavior
51
-
Give a clear and concise description of what you expected to happen.
61
+
62
+
> Give a clear and concise description of what you expected to happen.
52
63
53
64
## 5. Actual behavior
54
-
If applicable, add screenshots to help explain your problem. But do not paste log screenshots here.
55
65
66
+
> If applicable, add screenshots to help explain your problem. But do not paste log screenshots here.
56
67
57
68
## 6. Full Output Logs
58
-
Set env `WECHATY_LOG=silly` in order to set log level to silly, then we can get the full log (If you dosen't set log env, log level is info as default, we cannot get the full log)
69
+
70
+
> Set env `WECHATY_LOG=silly`in order to set log level to silly, then we can get the full log (If you dosen't set log env, log level is info as default, we cannot get the full log)
59
71
60
72
**We need full log instead of log screenshot or log fragments!**
61
73
@@ -67,14 +79,12 @@ Show Logs
67
79
```shell
68
80
$ WECHATY_LOG=silly node yourbot.js
69
81
70
-
Question: Paste your FULL(DO NOT ONLY PROVIDE FRAGMENTS) log messages
71
-
Answer:
82
+
-> PASTE YOUR FULL(DO NOT ONLY PROVIDE FRAGMENTS) LOG MESSAGES HERE
0 commit comments