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

Fix 'broken promise' error in parameter client #44

Closed
esteve opened this issue Jun 19, 2015 · 0 comments · Fixed by #47
Closed

Fix 'broken promise' error in parameter client #44

esteve opened this issue Jun 19, 2015 · 0 comments · Fixed by #47
Assignees

Comments

@esteve
Copy link
Member

esteve commented Jun 19, 2015

No description provided.

@esteve esteve self-assigned this Jun 19, 2015
@esteve esteve added the in progress Actively being worked on (Kanban column) label Jun 19, 2015
@esteve esteve mentioned this issue Jun 23, 2015
@esteve esteve added in review Waiting for review (Kanban column) and removed in progress Actively being worked on (Kanban column) labels Jun 23, 2015
@tfoote tfoote added in progress Actively being worked on (Kanban column) and removed in review Waiting for review (Kanban column) labels Jun 23, 2015
@esteve esteve added in review Waiting for review (Kanban column) and removed in progress Actively being worked on (Kanban column) labels Jun 24, 2015
@esteve esteve changed the title Fix 'promise already statisfied' error in parameter client Fix 'broken promise' error in parameter client Jun 24, 2015
@esteve esteve removed the in review Waiting for review (Kanban column) label Jun 25, 2015
mauropasse pushed a commit to mauropasse/rclcpp that referenced this issue Feb 15, 2021
…id-ptr

Check validity of executor pointer
nnmm pushed a commit to ApexAI/rclcpp that referenced this issue Jul 9, 2022
* Add remote (inter-process) services test for rcl and change default QoS profile for services.
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

Successfully merging a pull request may close this issue.

2 participants