-
Notifications
You must be signed in to change notification settings - Fork 175
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
The same node cannot subscribe to messages published by itself #1106
Comments
Hi @jiejieTop,
This function needs to be called after |
Thanks a lot, this works, but why need to explicitly enable? |
Yes, it's following the same logic like socket communication. Normally you don't want to read your own content. We had scenarios in the past were user used the same topics for incoming and outgoing interfaces in different nodes and expected to get triggered by external publishers only. |
Problem Description
The node publishes data and subscribes to this topic in the same node, which will result in the failure to subscribe to the message and fail to enter the callback function. The test example is as follows:
How to reproduce
How did you get eCAL?
Ubuntu PPA (apt-get)
Environment
eCAL System Information
No response
The text was updated successfully, but these errors were encountered: