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.

Sign up for GitHub

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

Jump to bottom

confuse about the sigint_gc's lifecycle #287

Closed
reed-lau opened this issue Mar 18, 2019 · 0 comments · Fixed by #308
Closed

confuse about the sigint_gc's lifecycle #287

reed-lau opened this issue Mar 18, 2019 · 0 comments · Fixed by #308
Assignees
@sloretz

Comments

@reed-lau
Copy link
Contributor

rclpy/rclpy/rclpy/executors.py

Line 466 in e9cc80c

(sigint_gc, sigint_gc_handle) = \

In my point of view ,the signt_gc (short for sigint guard condition) is an global behaviour. why each time create a new one?

this may be related with #253
@sloretz sloretz mentioned this issue Apr 5, 2019
Merged
@sloretz sloretz self-assigned this Apr 5, 2019
@sloretz sloretz added the in progress Actively being worked on (Kanban column) label Apr 5, 2019
@sloretz sloretz added in review Waiting for review (Kanban column) and removed in progress Actively being worked on (Kanban column) labels Apr 18, 2019
@sloretz sloretz removed the in review Waiting for review (Kanban column) label Apr 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sloretz sloretz

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Every executor gets its own SIGINT guard condition ros2/rclpy
2 participants
@sloretz @reed-lau