Improve the robustness of the TopicEndpointInfo constructor (backport #3013) #3014
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
node_name,node_namespaceandtopic_typemay be nullptr. This will result in initializing a std::string with nullptr, which will cause an exception during construction. This issue is mentioned here ros2/rosbag2#2293.rclcpp/rclcpp/include/rclcpp/node_interfaces/node_graph_interface.hpp
Lines 59 to 62 in c85ff92
Is this user-facing behavior change?
No
Did you use Generative AI?
No
Additional Information
N/A
This is an automatic backport of pull request #3013 done by [Mergify](https://mergify.com).