bug_report.yml 3.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687
  1. name: Bug report
  2. description: "Submit Xray-core bug"
  3. body:
  4. - type: checkboxes
  5. attributes:
  6. label: Integrity requirements
  7. description: |-
  8. Please check all of the following options to prove that you have read and understood the requirements, otherwise this issue will be closed.
  9. options:
  10. - label: I confirm that I have read the documentation, understand the meaning of all the configuration items I wrote, and did not pile up seemingly useful options or default values.
  11. required: true
  12. - label: I provided the complete config and logs, rather than just providing the truncated parts based on my own judgment.
  13. required: true
  14. - label: I searched issues and did not find any similar issues.
  15. required: true
  16. - label: The problem can be successfully reproduced in the latest Release
  17. required: true
  18. - type: textarea
  19. attributes:
  20. label: Description
  21. description: |-
  22. Please provide a detailed description of the error. And the information you think valuable.
  23. If the problem occurs after the update, please provide the **specific** version
  24. validations:
  25. required: true
  26. - type: textarea
  27. attributes:
  28. label: Reproduction Method
  29. description: |-
  30. Based on the configuration you provided below, provide the method to reproduce the bug.
  31. validations:
  32. required: true
  33. - type: markdown
  34. attributes:
  35. value: |-
  36. ## Configuration and Log Section
  37. ### For config
  38. Please provide the configuration files that can reproduce the problem, including the server and client.
  39. Don't just paste a big exported config file here. Eliminate useless inbound/outbound, rules, options, this can help determine the problem, if you really want to get help.
  40. ### For logs
  41. Please set the log level to debug and dnsLog to true first.
  42. Restart Xray-core, then operate according to the reproduction method, try to reduce the irrelevant part in the log.
  43. Remember to delete parts with personal information (such as UUID and IP).
  44. Provide the log of Xray-core, not the log output by the panel or other things.
  45. ### Finally
  46. After removing parts that do not affect reproduction, provide the actual running **complete** file, do not only provide inbound or outbound or a few lines of logs based on your own judgment.
  47. Put the content between the preset ```<details><pre><code>``` ```</code></pre></details>``` in the text box.
  48. If the problem is very clear that only related to one end (such as core startup failure/crash after correctly writing the config according to the documents), N/A can be filled in for unnecessary areas below.
  49. - type: textarea
  50. attributes:
  51. label: Client config
  52. value: |-
  53. <details><pre><code>
  54. </code></pre></details>
  55. validations:
  56. required: true
  57. - type: textarea
  58. attributes:
  59. label: Server config
  60. value: |-
  61. <details><pre><code>
  62. </code></pre></details>
  63. validations:
  64. required: true
  65. - type: textarea
  66. attributes:
  67. label: Client log
  68. value: |-
  69. <details><pre><code>
  70. </code></pre></details>
  71. validations:
  72. required: true
  73. - type: textarea
  74. attributes:
  75. label: Server log
  76. value: |-
  77. <details><pre><code>
  78. </code></pre></details>
  79. validations:
  80. required: true