Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fail to communicate service/client #239

Closed
DongheeYe opened this issue Nov 20, 2018 · 2 comments
Closed

Fail to communicate service/client #239

DongheeYe opened this issue Nov 20, 2018 · 2 comments

Comments

@DongheeYe
Copy link
Contributor

DongheeYe commented Nov 20, 2018

Bug report

Required Info:

  • Operating System:
    • Ubuntu 16.04
  • Installation type:
    • Source
  • Version or commit hash:
    • master
  • DDS implementation:
    • Fast-RTPS
  • Client library (if applicable):
    • rclcpp

Steps to reproduce issue

  1. Compile latest ros2 from master: colcon build --symlink-install --cmake-args -DSECURITY=ON -DCMAKE_BUILD_TYPE=Debug
  2. Source the workspace: source install/local_setup.bash
  3. Set environments
    ROS_SECURITY_ROOT_DIRECTORY=~/security/keys
    ROS_SECURITY_ENABLE=true
    ROS_SECURITY_STRATEGY=Permissive
  4. Run service_main
    $ ./install/examples_rclcpp_minimal_service/lib/examples_rclcpp_minimal_service/service_main &
  1. Run client_main
    $ ./install/examples_rclcpp_minimal_client/lib/examples_rclcpp_minimal_client/client_main

Expected behavior

The service and client can communicate properly.

Actual behavior

The client send request and waiting forever. (1 in 3 times)

Additional information

It is also occurred in -DSECURITY=OFF. But you can easily reproduce the issue if you build with -DSERCURITY=ON.


Feature request

Feature description

Implementation considerations

@DongheeYe
Copy link
Contributor Author

I figure out the reason and fix it with #238.
Please check the patch.

@dirk-thomas
Copy link
Member

Closing since #238 is supposed to address this.

@dirk-thomas dirk-thomas removed the in review Waiting for review (Kanban column) label Jan 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants