[14:38] <hatch> frankban sorry for using all the spots in the maintenance lane - I came across a bug which....is impossible :/
[14:39] <frankban> :-/ np hatch, I have my card, and it's not an easy one
[14:39] <frankban> hatch: ping me if you need any help
[14:40] <hatch> yeah I think it's just a solo job unfortunately 
[15:37] <hatch> I found out why we get unit delta errors when destroying services
[15:38] <hatch> the first annotation in the delta removes the service then the second one removes the unit
[15:38] <hatch> ^ frankban is this something we have any control over? 
[15:39] <frankban> hatch: delta errors?
[15:39] <frankban> why errors?
[15:39] <hatch> for the longest time we have had an issue where the unit was being destroyed after the service was so there was a console error
[15:40] <hatch> and it's because the remove service annotation is in the 0 index in the annotation array whereas the unit remove is in the 1 index
[15:41] <hatch> we of course could check for this in the GUI but I'm curious if we can have it fixed in core
[15:42] <frankban> hatch: I believe you don't mean annotations (like x/y annotation), but just the message info returned by the mega watcher, right?
[15:43] <hatch> right, copy and paste this text into the console and you will see what I mean about the order of the messages
[15:43] <hatch> https://gist.github.com/hatched/5d791603bea9f0c50cfb
[15:45] <frankban> hatch: there I see an annotation remove message, then a unit one and then a machine one
[15:46] <hatch> oh crud I pasted the wrong one
[15:46] <hatch> now I have to reproduce it
[15:46] <hatch> heh
[15:47] <hatch> sorry to bother you :) 
[15:59] <frankban> np