-
Notifications
You must be signed in to change notification settings - Fork 923
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
Implement a common method for creating branches #1603
Implement a common method for creating branches #1603
Conversation
Automatic updating of Retain
This pull request introduces 2 alerts when merging 11e458a into 31e4a2b - view on LGTM.com new alerts:
|
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.
Hi @Archie-Miller , technically this is an API update so we may have to wait for the next version (aka.368, no worries, we switch likely very soon)
second, is there sample code how to use this? Even better were a alarm namespace in the ref sample server and/or test cases. There are now client/server fixtures.
/// <returns></returns> | ||
public Dictionary< string, ConditionState >GetBranches() | ||
{ | ||
if (m_branches == null) |
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.
makes me wonder if the access to the Dictionary needsto be synchronized?
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'm not sure of the reason why this might be necessary, but I'm ready to discuss your concerns!
Implement a mechanism to create Alarm Branches, store them, allow AddComment, Acknowledge, and Confirm them.
Updates the Retain flag automatically.
Cleans up branches on Ack/Confirm
Allows servers to retrieve branches to clear them all if necessary.