mirror of
http://git.haproxy.org/git/haproxy.git/
synced 2024-12-11 22:15:14 +00:00
8564f53812
as per the suggestions from Cyril and Willy on the mailing list: Message-ID: <a0010c72-70b8-0647-c269-55c6614627c3@free.fr> and with direct contributions from Tim, this changes large parts of the bug issue template. The Feature template is also updated as well as a new template for Code Reports is introduced. Co-authored-by: Tim Duesterhus <tim@bastelstu.be>
56 lines
1.4 KiB
Markdown
56 lines
1.4 KiB
Markdown
---
|
|
name: Code Report
|
|
about: File a Code Report (for example from coverity or valgrind)
|
|
labels: 'type: code-report'
|
|
---
|
|
|
|
<!--
|
|
|
|
Welcome! - We kindly ask that you:
|
|
|
|
1. Fill out the issue template below - not doing so needs a good reason.
|
|
2. Use the forum or the mailing list if you have a question rather than a bug or feature request.
|
|
|
|
The forum is at: https://discourse.haproxy.org/
|
|
|
|
The mailing list (no need to subscribe) is: haproxy@formilux.org
|
|
Subscribe to the list: haproxy+subscribe@formilux.org
|
|
Unsubscribe from the list: haproxy+unsubscribe@formilux.org
|
|
|
|
Forum and mailing list are correct places for questions about HAProxy or general suggestions
|
|
and topics, e.g. usage or documentation questions! This issue tracker is for tracking bugs and
|
|
feature requests directly relating to the development of the software itself.
|
|
|
|
Thanks for understanding, and for contributing to the project!
|
|
|
|
-->
|
|
|
|
## Code Report
|
|
|
|
<!--
|
|
In this section please provide:
|
|
1. Information about the tool that generated the report (e.g. valgrind-3.11.0 or Coverity).
|
|
2. Provide the full output of the tool in code blocks (```).
|
|
-->
|
|
|
|
Tool: (tool name goes here)
|
|
|
|
```
|
|
(paste your output here)
|
|
```
|
|
|
|
|
|
## Output of `haproxy -vv` and `uname -a`
|
|
|
|
<!--
|
|
Please add the output of haproxy -vv you are currently using here, this helps us
|
|
later to see what has changed in HAProxy when we revisit this issue after some
|
|
time.
|
|
|
|
Put it in code blocks ```:
|
|
-->
|
|
|
|
```
|
|
(paste your output here)
|
|
```
|