-
Notifications
You must be signed in to change notification settings - Fork 44
push_data_ready_event() deadlock (issue-22) #27
Conversation
although we store device names in lower case; the same code might be necessary in other places? needs review
seems it is a dictionary and '.iteritems()' was missing in for loop
long ctr) | ||
{ | ||
SAFE_PUSH(self, attr, name) | ||
self.push_data_ready_event(__att_name, ctr); //__att_name from SAFE_PUSH |
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.
I noticed that push_archive_event
calls attr.fire_archive_event()
. Is there any reason why you're not using something similar, e.g. attr.fire_data_ready_event()
?
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.
It looks like Attribute cpp class only provides these methods:
- Attribute::fire_archive_event
- Attribute::fire_change_event
- Attribute::fire_event
- Attribute::fire_error_periodic_event
I can't see any "fire_data_ready_event" nor anything similar that could be used. Any suggestion?
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.
OK, I was just curious about it.
Has it been tested against the example scenario in issue #22? |
Yes, I tested the solution using the sample code in #22 |
Great! Then it should be safe to merge. |
Thanks! |
I hope this fixes issue-22