Closed claireyywang closed 3 months ago
Out of curiousity, how long did you wait? We have a known issue somewhere where Connext can take a substantial amount of time to cleanup after itself (like 10 seconds or something). I'm wondering if this is a duplicate.
Out of curiousity, how long did you wait? We have a known issue somewhere where Connext can take a substantial amount of time to cleanup after itself (like 10 seconds or something). I'm wondering if this is a duplicate.
I tried again, waited for at least five minutes and got the same result. I had to close the terminal to kill it.
I tried again, waited for at least five minutes and got the same result. I had to close the terminal to kill it.
Sounds like something new :+1:
I came across the same thing. @claireyywang try pressing x
...
The thing is that these demos spin up a separate thread to support stdin
-based user interaction. Because of the way that bit is coded, you have to either Ctrl-C or press x
(to stop the executor) and then press another random key to get yourself out of a blocking getch*()
call.
I fiddled a bit on how to fix it but being cross-platform is going to be time consuming. I'll come back later.
@claireyywang can you push on this issue. @hidmic says the code may need to be refactored to close when doing ctrl-c. We can either backlog this or fix it. Thanks!
@wjwwood sure I'll look into it
Since we don't support rmw_connext_cpp
anymore, I'm going to go ahead and close this out.
Bug report
Required Info:
Steps to reproduce issue
Expected behavior
print
then exit the process
Actual behavior
never exit.