-
Notifications
You must be signed in to change notification settings - Fork 116
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
Delay lock on message callback setters #657
Conversation
Signed-off-by: Miguel Company <MiguelCompany@eprosima.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@MiguelCompany I think this fixes subscription problem, but the same fix should be applied to on_new_response_m_
and on_new_request_m_
as well?
Signed-off-by: Miguel Company <MiguelCompany@eprosima.com>
Signed-off-by: Miguel Company <MiguelCompany@eprosima.com>
@fujitatomoya You are right. I've pushed the changes and also changed the PR description accordingly |
@fujitatomoya Do you think this can be merged? |
@Mergifyio backport humble |
* Delay lock on SubListener::set_on_new_message_callback. Signed-off-by: Miguel Company <MiguelCompany@eprosima.com> * Delay lock on ClientListener::set_on_new_response_callback. Signed-off-by: Miguel Company <MiguelCompany@eprosima.com> * Delay lock on ServiceListener::set_on_new_request_callback. Signed-off-by: Miguel Company <MiguelCompany@eprosima.com> Signed-off-by: Miguel Company <MiguelCompany@eprosima.com> (cherry picked from commit d109187)
✅ Backports have been created
|
* Delay lock on SubListener::set_on_new_message_callback. Signed-off-by: Miguel Company <MiguelCompany@eprosima.com> * Delay lock on ClientListener::set_on_new_response_callback. Signed-off-by: Miguel Company <MiguelCompany@eprosima.com> * Delay lock on ServiceListener::set_on_new_request_callback. Signed-off-by: Miguel Company <MiguelCompany@eprosima.com> Signed-off-by: Miguel Company <MiguelCompany@eprosima.com>
* Delay lock on SubListener::set_on_new_message_callback. Signed-off-by: Miguel Company <MiguelCompany@eprosima.com> * Delay lock on ClientListener::set_on_new_response_callback. Signed-off-by: Miguel Company <MiguelCompany@eprosima.com> * Delay lock on ServiceListener::set_on_new_request_callback. Signed-off-by: Miguel Company <MiguelCompany@eprosima.com> Signed-off-by: Miguel Company <MiguelCompany@eprosima.com> (cherry picked from commit d109187)
* Delay lock on SubListener::set_on_new_message_callback. Signed-off-by: Miguel Company <MiguelCompany@eprosima.com> * Delay lock on ClientListener::set_on_new_response_callback. Signed-off-by: Miguel Company <MiguelCompany@eprosima.com> * Delay lock on ServiceListener::set_on_new_request_callback. Signed-off-by: Miguel Company <MiguelCompany@eprosima.com> Signed-off-by: Miguel Company <MiguelCompany@eprosima.com> (cherry picked from commit d109187) Co-authored-by: Miguel Company <miguelcompany@eprosima.com>
This should fix #646 by calling
get_unread_count
before taking the lock on the mutexon_new_message_m_
.It provides similar fixes for the callback setter on subscriptions, services, and clients.