-
Notifications
You must be signed in to change notification settings - Fork 421
WaitSet::wait
does not return if data was send before WaitSet::attachState
#1855
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
Comments
mossmaurice
pushed a commit
to ApexAI/iceoryx
that referenced
this issue
Jan 24, 2023
…hen attaching states to the WaitSet
mossmaurice
pushed a commit
to ApexAI/iceoryx
that referenced
this issue
Jan 24, 2023
…Set::attachState'
mossmaurice
pushed a commit
to ApexAI/iceoryx
that referenced
this issue
Jan 24, 2023
…eturn bugfix Signed-off-by: Simon Hoinkis <[email protected]>
21 tasks
mossmaurice
pushed a commit
to ApexAI/iceoryx
that referenced
this issue
Jan 25, 2023
…eturn bugfix Signed-off-by: Simon Hoinkis <[email protected]>
mossmaurice
pushed a commit
to ApexAI/iceoryx
that referenced
this issue
Jan 25, 2023
…t::wait' for a 2nd time Signed-off-by: Simon Hoinkis <[email protected]>
Will be closed once merged on |
25 tasks
mossmaurice
pushed a commit
that referenced
this issue
Jan 25, 2023
mossmaurice
pushed a commit
that referenced
this issue
Jan 25, 2023
…2nd time Signed-off-by: Simon Hoinkis <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Required information
Operating system:
Ubuntu 20.04.3 LTS
Compiler version:
GCC 8.4.0
Affected release(s):
master
branchv2.0.2
Observed result or behaviour:
WaitSet::wait
does not return when there is data in the queue akahasData()
/hasRespones()
/hasRequests()
returningtrue
at the time of attaching an object to theWaitSet
and without further notification.Expected result or behaviour:
If data is available in the queue when attached, the
WaitSet::wait
should immediately return.Conditions where it occurred / Performed steps:
The issue was uncovered while working on ros2/rmw_iceoryx#84 with request/response communication. The same problem should also occur with pub/sub communication, but I have not explicitly reproduced that.
iox::popo::Server
iox::popo::Client
iox::popo::Client
from app Bobiox::popo::Server
sends responseìox::popo::WaitSet
iox::popo::ClientState::HAS_RESPONSE
WaitSet::wait
which never returns because theConditionNotifier::notify()
call and its trigger is missing for the data which is already stored in the queueThe text was updated successfully, but these errors were encountered: