Skip to content
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

Insteon: Move Failure_Reason into BaseObject from Message #194

Merged
merged 1 commit into from
May 21, 2013

Conversation

krkeegan
Copy link
Collaborator

The active_message must be cleared before calling the failure_callback, otherwise we get into a strange loop with sync and scan links
Once the active_message is cleared, we lose our ability to keep track of the failured message and corresponding failure_reason

To resolve this, moved failure_reason from the message object into BaseObject.

The active_message must be cleared before calling the failure_callback, otherwise we get into a strange loop with sync and scan links
Once the active_message is cleared, we lose our ability to keep track of the failured message and corresponding failure_reason

To resolve this, moved failure_reason from the message object into BaseObject.
krkeegan added a commit that referenced this pull request May 21, 2013
Insteon: Move Failure_Reason into BaseObject from Message
@krkeegan krkeegan merged commit b1bcb85 into hollie:master May 21, 2013
@krkeegan krkeegan deleted the fix_issue_175 branch May 21, 2013 04:02
@hollie hollie mentioned this pull request Jun 15, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant