Escalations should not be run at boot
Reported by Paul Jones | July 21st, 2011 @ 04:56 PM
Escalations currently trigger when the application boots, due to the fact DifferenceMessage issues differences with the TriggeredByScan marker. This shouldn't occur, and we should mark differences triggered by system boot as such.
Comments and changes to this ticket
-
Ben Hood July 21st, 2011 @ 05:02 PM
(from [4ec0a3d0b2f1bcb0e8ae33a9a4ce83f443b64618]) [#310] Pair Actor difference messages generated as a result of a difference call are marked with TriggeredByBoot. https://github.com/lshift/diffa/commit/4ec0a3d0b2f1bcb0e8ae33a9a4ce...
-
Paul Jones July 21st, 2011 @ 05:02 PM
- Assigned user changed from “Paul Jones” to “Ben Hood”
- State changed from “open” to “resolved”
Ready for QA
-
Ben Hood July 21st, 2011 @ 05:25 PM
(from [9728624230ce6f2ce4fbc5f482dd10a46924544a]) Merge pull request #48 from lshift/310
[#310] Pair Actor difference messages generated as a result of a differen https://github.com/lshift/diffa/commit/9728624230ce6f2ce4fbc5f482dd...
-
-
Ben Hood July 21st, 2011 @ 05:26 PM
- State changed from “resolved” to “closed”
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
A Real Time Differencing Tool.
Ben Hood