|
| 1 | +name: 🐛 Bug Report |
| 2 | +description: File a bug report. |
| 3 | +labels: ["bug"] |
| 4 | +body: |
| 5 | + - type: markdown |
| 6 | + attributes: |
| 7 | + value: "**Required Info:**" |
| 8 | + - type: input |
| 9 | + id: generative_ai |
| 10 | + attributes: |
| 11 | + label: "Generated by Generative AI" |
| 12 | + description: "If this issue was generated using Generative AI, specify the tool and model used (e.g. GitHub Copilot, Claude Code)" |
| 13 | + validations: |
| 14 | + required: false |
| 15 | + - type: input |
| 16 | + id: os |
| 17 | + attributes: |
| 18 | + label: "Operating System:" |
| 19 | + description: | |
| 20 | + Please try to be specific. |
| 21 | + Run `uname -a` from a terminal and copy/paste its output here. |
| 22 | + This RMW is Linux-only (it uses `epoll`, `eventfd`, `/dev/shm` and `AF_UNIX`). |
| 23 | + value: | |
| 24 | + ``` |
| 25 | + <PUT OS INFO HERE> |
| 26 | + ``` |
| 27 | + validations: |
| 28 | + required: true |
| 29 | + - type: dropdown |
| 30 | + id: ros_distro |
| 31 | + attributes: |
| 32 | + label: "ROS 2 distro:" |
| 33 | + options: |
| 34 | + - jazzy |
| 35 | + - kilted |
| 36 | + - rolling |
| 37 | + - other (please state in Additional information) |
| 38 | + validations: |
| 39 | + required: true |
| 40 | + - type: input |
| 41 | + id: version |
| 42 | + attributes: |
| 43 | + label: "rmw_unix_socket_cpp version or commit hash:" |
| 44 | + description: | |
| 45 | + The version from `package.xml`, or the commit hash you built from (`git rev-parse HEAD`). |
| 46 | + validations: |
| 47 | + required: true |
| 48 | + - type: input |
| 49 | + id: clientlib |
| 50 | + attributes: |
| 51 | + label: "Client library (if applicable):" |
| 52 | + description: | |
| 53 | + **Examples:** *rclcpp*, *rclpy*, ... |
| 54 | + Client libraries are the APIs that allow users to implement their ROS 2 code. |
| 55 | + validations: |
| 56 | + required: false |
| 57 | + - type: dropdown |
| 58 | + id: executor |
| 59 | + attributes: |
| 60 | + label: "Executor (if applicable):" |
| 61 | + description: | |
| 62 | + Wait-set and event delivery behaviour differs noticeably between executors. |
| 63 | + options: |
| 64 | + - SingleThreadedExecutor |
| 65 | + - MultiThreadedExecutor |
| 66 | + - StaticSingleThreadedExecutor |
| 67 | + - EventsExecutor |
| 68 | + - other / not sure |
| 69 | + validations: |
| 70 | + required: false |
| 71 | + - type: dropdown |
| 72 | + id: other_rmw |
| 73 | + attributes: |
| 74 | + label: "Does the same reproducer work with another RMW?" |
| 75 | + description: | |
| 76 | + Re-run with `RMW_IMPLEMENTATION=rmw_fastrtps_cpp` (or `rmw_cyclonedds_cpp`). |
| 77 | + This tells us whether the bug is specific to this RMW or lives further up the stack. |
| 78 | + options: |
| 79 | + - "Yes — it works with another RMW, so the bug looks specific to rmw_unix_socket_cpp" |
| 80 | + - "No — it fails with another RMW too" |
| 81 | + - "Not tested" |
| 82 | + validations: |
| 83 | + required: false |
| 84 | + - type: textarea |
| 85 | + id: qos |
| 86 | + attributes: |
| 87 | + label: "QoS profile (if applicable):" |
| 88 | + description: | |
| 89 | + If you use a non-default QoS profile, post it here (reliability, durability, history, depth). |
| 90 | + Note that some policies are unsupported — see the Limitations section of the README. |
| 91 | + validations: |
| 92 | + required: false |
| 93 | + - type: textarea |
| 94 | + id: doctor |
| 95 | + attributes: |
| 96 | + label: "'ros2 doctor --report' output" |
| 97 | + description: | |
| 98 | + It can help us knowing the details of your ROS environment. |
| 99 | + Please use the command `ros2 doctor --report` and copy paste its output here. |
| 100 | + value: | |
| 101 | + <details><summary>ros2 doctor --report</summary> |
| 102 | +
|
| 103 | + ```console |
| 104 | + <COPY OUTPUT HERE> |
| 105 | + ``` |
| 106 | + </details> |
| 107 | + validations: |
| 108 | + required: false |
| 109 | + - type: textarea |
| 110 | + id: repro |
| 111 | + attributes: |
| 112 | + label: "Steps to reproduce issue" |
| 113 | + description: | |
| 114 | + How do you trigger this bug? Please walk us through it step by step. |
| 115 | + Include all the commands you ran in the exact order you ran them so that anyone can reproduce the bug. |
| 116 | + Remember that every process that should talk to each other needs `RMW_IMPLEMENTATION=rmw_unix_socket_cpp` set. |
| 117 | + placeholder: | |
| 118 | + 1. |
| 119 | + 2. |
| 120 | + 3. |
| 121 | + ... |
| 122 | + validations: |
| 123 | + required: true |
| 124 | + - type: textarea |
| 125 | + id: expected |
| 126 | + attributes: |
| 127 | + label: "Expected behavior" |
| 128 | + validations: |
| 129 | + required: true |
| 130 | + - type: textarea |
| 131 | + id: actual |
| 132 | + attributes: |
| 133 | + label: "Actual behavior" |
| 134 | + description: | |
| 135 | + Include any error output. If a process crashed, a backtrace is very helpful. |
| 136 | + Setting `RCUTILS_LOGGING_SEVERITY=DEBUG` often surfaces the relevant RMW logs. |
| 137 | + validations: |
| 138 | + required: true |
| 139 | + - type: textarea |
| 140 | + id: addinfo |
| 141 | + attributes: |
| 142 | + label: "Additional information" |
| 143 | + description: | |
| 144 | + Please note any additional information to share here. |
| 145 | + e.g) Is the reported bug a regression? If so, what is the last version where it still worked fine? |
| 146 | + How many nodes/topics does your system run, and does the problem depend on that scale? |
| 147 | + validations: |
| 148 | + required: false |
0 commit comments