-
Notifications
You must be signed in to change notification settings - Fork 332
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
8354081
commit b7a64ab
Showing
1 changed file
with
44 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,44 @@ | ||
<!-- | ||
For general questions, please post on discourse: https://discourse.ros.org/c/ng-ros | ||
Not sure if this is the right repository? Open an issue on https://github.com/ros2/ros2/issues | ||
For Bug report or feature requests, please fill out the relevant category below | ||
--> | ||
|
||
## Bug report | ||
|
||
**Required Info:** | ||
|
||
- Operating System: | ||
- <!-- OS and version (e.g. Windows 10, Ubuntu 16.04...) --> | ||
- Installation type: | ||
- <!-- binaries or from source --> | ||
- Version or commit hash: | ||
- <!-- Output of git rev-parse HEAD, release version, or repos file --> | ||
- DDS implementation: | ||
- <!-- rmw_implementation used (e.g. Fast-RTPS, RTI Connext, etc --> | ||
- Client library (if applicable): | ||
- <!-- e.g. rclcpp, rclpy, or N/A --> | ||
|
||
#### Steps to reproduce issue | ||
<!-- Detailed instructions on how to reliably reproduce this issue http://sscce.org/ | ||
``` code that can be copy-pasted is preferred ``` --> | ||
``` | ||
``` | ||
|
||
#### Expected behavior | ||
|
||
#### Actual behavior | ||
|
||
#### Additional information | ||
|
||
<!-- If you are reporting a bug delete everything below | ||
If you are requesting a feature deleted everything above this line --> | ||
---- | ||
## Feature request | ||
|
||
#### Feature description | ||
<!-- Description in a few sentences what the feature consists of and what problem it will solve --> | ||
|
||
#### Implementation considerations | ||
<!-- Relevant information on how the feature could be implemented and pros and cons of the different solutions --> |