You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Upstream quality changes from Apex.AI part-2 (#1924)
* Fix for incorrectly handling exit code in wait_until_completion(..)
Signed-off-by: Michael Orlov <morlovmr@gmail.com>
* Address flakiness in test_play_services
- Increase timeout for `expect_messages(..)`
- Also add `player_->wait_for_playback_to_start();` in `setup_player()`
Signed-off-by: Michael Orlov <morlovmr@gmail.com>
* Fix CPP_LINT warnings about missing include headers
Signed-off-by: Michael Orlov <morlovmr@gmail.com>
* Address CPPLint warnings in the rosbag2_storage_sqlite3
Signed-off-by: Michael Orlov <morlovmr@gmail.com>
* Adjust test_rosbag2_storage_api.cpp for bounded strings
- Reduce size of each std_string_msg to fit in 256 byte boundary
Signed-off-by: Michael Orlov <morlovmr@gmail.com>
* Print warnings instead of errors for not found type definitions
Signed-off-by: Michael Orlov <morlovmr@gmail.com>
* Add debug info to flaky `test_play_cancel` in rosbag2_py
Signed-off-by: Michael Orlov <morlovmr@gmail.com>
* Fix for flaky play_respect_messages_timing_after_play_next
Signed-off-by: Michael Orlov <morlovmr@gmail.com>
* Reduce runtime for the `PlayerTestFixture.playing_respects_delay` test
Signed-off-by: Michael Orlov <morlovmr@gmail.com>
* Address review comment by using `delay_margin(0.5s)`
Signed-off-by: Michael Orlov <morlovmr@gmail.com>
* Address linter warnings in the test_transport.py
Signed-off-by: Michael Orlov <morlovmr@gmail.com>
* Use RESOURCES_PATH from envar in test_transport.py
- Fix to avoid failure with remote test execution and to be consistent
with oter similar tests.
Signed-off-by: Michael Orlov <morlovmr@gmail.com>
* Mitigate flakiness in record_all_include_unpublished_false
Increase timeout when waiting to stop discovery at least to the 0.5 sec.
The record_all_include_unpublished_false_includes_later_published is
tend to be flaky due to the insufficient timeout for waiting to stop
discovery thread in the recorder.
Signed-off-by: Michael Orlov <morlovmr@gmail.com>
* Fix linter errors in the `message_definition_encoding.md`
Signed-off-by: Michael Orlov <morlovmr@gmail.com>
* Minor changes in rosbag2_examples_py
Signed-off-by: Michael Orlov <morlovmr@gmail.com>
* Mark MessageProducer<T> as final to address clang16 warnings
- Address clang16 warning:
"destructor called on non-final 'msg_utils::MessageProducer<T>' that
has virtual functions but non-virtual destructor".
Signed-off-by: Michael Orlov <morlovmr@gmail.com>
* Address unused variable warning on the clang16 build
Signed-off-by: Michael Orlov <morlovmr@gmail.com>
* Fix for flaky `test_play_services`
Increase timeouts for service calls in rosbag2_transport
`test_play_services` tests
Signed-off-by: Michael Orlov <morlovmr@gmail.com>
* Fix for record_if_topic_list_service_list_and_all_are_specified
- Flush output from Python print when printing warnings. Some tests rely
on the warning output to be in the std::cout. Without flushing the
warnings may not be captured by tests.
Signed-off-by: Michael Orlov <morlovmr@gmail.com>
* Sort includes alphabetically in the `info.cpp` file
Signed-off-by: Michael Orlov <morlovmr@gmail.com>
* Update rosbag2_cpp/test/rosbag2_cpp/test_service_utils.cpp
Sort includes alphabetically in test_service_utils.cpp
Co-authored-by: Christophe Bedard <bedard.christophe@gmail.com>
Signed-off-by: Michael Orlov <morlovmr@gmail.com>
* Sort includes in test_rosbag2_cpp_get_service_info.cpp
Co-authored-by: Christophe Bedard <bedard.christophe@gmail.com>
Signed-off-by: Michael Orlov <morlovmr@gmail.com>
* Sort includes in rosbag2_py/_info.cpp
Co-authored-by: Christophe Bedard <bedard.christophe@gmail.com>
Signed-off-by: Michael Orlov <morlovmr@gmail.com>
---------
Signed-off-by: Michael Orlov <morlovmr@gmail.com>
Co-authored-by: Christophe Bedard <bedard.christophe@gmail.com>
(cherry picked from commit 6f44ee0)
# Conflicts:
# ros2bag/ros2bag/verb/record.py
# rosbag2_cpp/src/rosbag2_cpp/info.cpp
Copy file name to clipboardExpand all lines: docs/message_definition_encoding.md
+15-7
Original file line number
Diff line number
Diff line change
@@ -16,10 +16,14 @@ This set of definitions with all field types recursively included can be called
16
16
17
17
## `ros2msg` encoding
18
18
19
-
This encoding consists of definitions in [.msg](https://docs.ros.org/en/rolling/Concepts/Basic/About-Interfaces.html#messages) and [.srv](https://docs.ros.org/en/rolling/Concepts/Basic/About-Interfaces.html#services) format, concatenated together in human-readable form with
19
+
This encoding consists of definitions in
20
+
[.msg](https://docs.ros.org/en/rolling/Concepts/Basic/About-Interfaces.html#messages) and
21
+
[.srv](https://docs.ros.org/en/rolling/Concepts/Basic/About-Interfaces.html#services) format,
22
+
concatenated together in human-readable form with
20
23
a delimiter.
21
24
22
-
The top-level message definition is present first, with no delimiter. All dependent .msg definitions are preceded by a two-line delimiter:
25
+
The top-level message definition is present first, with no delimiter. All dependent .msg definitions
26
+
are preceded by a two-line delimiter:
23
27
24
28
* One line containing exactly 80 `=` characters
25
29
* One line containing `MSG: <package resource name>` for that type. The space between MSG: and the
@@ -29,7 +33,7 @@ The top-level message definition is present first, with no delimiter. All depend
29
33
30
34
For example, the complete message definition for `my_msgs/msg/ExampleMsg` in `ros2msg` form is:
31
35
32
-
```
36
+
```ini
33
37
# defines a message that includes a field of a custom message type
Another example is a service message definition for `my_msgs/srv/ExampleSrv` in `ros2msg` form
42
46
43
-
```
47
+
```ini
44
48
# defines a service message that includes a field of a custom message type
45
49
my_msgs/BasicMsg request
46
50
---
@@ -53,16 +57,20 @@ float32 my_float
53
57
54
58
## `ros2idl` encoding
55
59
56
-
The IDL definition of the type specified by name along with all dependent types are stored together. The IDL definitions can be stored in any order. Every definition is preceded by a two-line delimiter:
60
+
The IDL definition of the type specified by name along with all dependent types are stored together.
61
+
The IDL definitions can be stored in any order. Every definition is preceded by a two-line
62
+
delimiter:
57
63
58
64
* a line containing exactly 80 `=` characters, then
59
-
* A line containing only `IDL: <package resource name>` for that definition. The space between IDL: and the package resource name is mandatory. The package resource name does not include a file extension.
65
+
* A line containing only `IDL: <package resource name>` for that definition. The space between IDL:
66
+
and the package resource name is mandatory. The package resource name does not include a file
67
+
extension.
60
68
61
69
### `ros2idl` example
62
70
63
71
For example, the complete message definition for `my_msgs/msg/ComplexMsg` in `ros2idl` form is:
0 commit comments