Merge commit '28ea478' into release-v0.3.32
commit
c785c0e889
@ -1,33 +0,0 @@
|
||||
---
|
||||
name: Mitogen 0.2.x bug report
|
||||
about: Report a bug in Mitogen 0.2.x (for Ansible 2.5, 2.6, 2.7, 2.8, or 2.9)
|
||||
title: ''
|
||||
labels: affects-0.2, bug
|
||||
assignees: ''
|
||||
|
||||
---
|
||||
|
||||
Please drag-drop large logs as text file attachments.
|
||||
|
||||
Feel free to write an issue in your preferred format, however if in doubt, use
|
||||
the following checklist as a guide for what to include.
|
||||
|
||||
* Which version of Ansible are you running?
|
||||
* Is your version of Ansible patched in any way?
|
||||
* Are you running with any custom modules, or `module_utils` loaded?
|
||||
|
||||
* Have you tried the latest master version from Git?
|
||||
* Do you have some idea of what the underlying problem may be?
|
||||
https://mitogen.networkgenomics.com/ansible_detailed.html#common-problems has
|
||||
instructions to help figure out the likely cause and how to gather relevant
|
||||
logs.
|
||||
* Mention your host and target OS and versions
|
||||
* Mention your host and target Python versions
|
||||
* If reporting a performance issue, mention the number of targets and a rough
|
||||
description of your workload (lots of copies, lots of tiny file edits, etc.)
|
||||
* If reporting a crash or hang in Ansible, please rerun with -vvv and include
|
||||
200 lines of output around the point of the error, along with a full copy of
|
||||
any traceback or error text in the log. Beware "-vvv" may include secret
|
||||
data! Edit as necessary before posting.
|
||||
* If reporting any kind of problem with Ansible, please include the Ansible
|
||||
version along with output of "ansible-config dump --only-changed".
|
||||
@ -1,33 +0,0 @@
|
||||
---
|
||||
name: Mitogen 0.3.x bug report
|
||||
about: Report a bug in Mitogen 0.3.x (for Ansible 2.10.x)
|
||||
title: ''
|
||||
labels: affects-0.3, bug
|
||||
assignees: ''
|
||||
|
||||
---
|
||||
|
||||
Please drag-drop large logs as text file attachments.
|
||||
|
||||
Feel free to write an issue in your preferred format, however if in doubt, use
|
||||
the following checklist as a guide for what to include.
|
||||
|
||||
* Which version of Ansible are you running?
|
||||
* Is your version of Ansible patched in any way?
|
||||
* Are you running with any custom modules, or `module_utils` loaded?
|
||||
|
||||
* Have you tried the latest master version from Git?
|
||||
* Do you have some idea of what the underlying problem may be?
|
||||
https://mitogen.networkgenomics.com/ansible_detailed.html#common-problems has
|
||||
instructions to help figure out the likely cause and how to gather relevant
|
||||
logs.
|
||||
* Mention your host and target OS and versions
|
||||
* Mention your host and target Python versions
|
||||
* If reporting a performance issue, mention the number of targets and a rough
|
||||
description of your workload (lots of copies, lots of tiny file edits, etc.)
|
||||
* If reporting a crash or hang in Ansible, please rerun with -vvv and include
|
||||
200 lines of output around the point of the error, along with a full copy of
|
||||
any traceback or error text in the log. Beware "-vvv" may include secret
|
||||
data! Edit as necessary before posting.
|
||||
* If reporting any kind of problem with Ansible, please include the Ansible
|
||||
version along with output of "ansible-config dump --only-changed".
|
||||
@ -0,0 +1,62 @@
|
||||
name: Bug report
|
||||
description: Report a bug in Mitogen 0.3.x (for Ansible 2.10 and above)
|
||||
labels:
|
||||
- affects-0.3
|
||||
type: bug
|
||||
|
||||
body:
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: Description
|
||||
description: >
|
||||
When does the problem occur?
|
||||
What happens after?
|
||||
How is this different?
|
||||
Did it previously behave as expected?
|
||||
placeholder: |
|
||||
When I do X, Y happens, but I was expecting Z because ...
|
||||
Before version 1.2.3 it worked as expected.
|
||||
validations:
|
||||
required: true
|
||||
|
||||
- type: input
|
||||
attributes:
|
||||
label: Mitogen version
|
||||
placeholder: 0.3.31, 0.3.3-9+deb12u1
|
||||
validations:
|
||||
required: true
|
||||
|
||||
- type: input
|
||||
attributes:
|
||||
label: Ansible version (if applicable)
|
||||
placeholder: 2.18.11
|
||||
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: OS and environment
|
||||
description: >
|
||||
What operating system version(s), Python version(s), etc. are you using?
|
||||
placeholder: |
|
||||
Controller (master): Debian 13, Python 3.14
|
||||
Targets (slaves): Ubuntu 20.04/Python 2.7, RHEL 10, ...
|
||||
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: Steps to reproduce
|
||||
description: >
|
||||
Instructions, code, or playbook(s) recreate the beahviour
|
||||
value: |
|
||||
Steps:
|
||||
1. Set config `foo = 42` in somefile.cfg
|
||||
2. Run the following Python or Playbook with `cmd --option bar ...`
|
||||
|
||||
```
|
||||
Code or playbook here
|
||||
```
|
||||
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: Anything else
|
||||
description: >
|
||||
Include any other details you think might be relevant or helpful.
|
||||
Examples might include logs, unusual settings, environment variables, ...
|
||||
@ -1,10 +0,0 @@
|
||||
path_classifiers:
|
||||
library:
|
||||
- "mitogen/compat"
|
||||
- "ansible_mitogen/compat"
|
||||
queries:
|
||||
# Mitogen 2.4 compatibility trips this query everywhere, so just disable it
|
||||
- exclude: py/unreachable-statement
|
||||
- exclude: py/should-use-with
|
||||
# mitogen.core.b() trips this query everywhere, so just disable it
|
||||
- exclude: py/import-and-import-from
|
||||
Loading…
Reference in New Issue