[17:50] <hatch> uiteam lf a review and qa on https://github.com/juju/juju-gui/pull/706
[17:50] <hatch> the diff looks huge but thats just because of a json response object update
[18:28] <hatch> bug #1430242
[18:28] <mup> Bug #1430242: cannot change charm location most of the time <landscape> <juju-gui:Incomplete by hatch> <https://launchpad.net/bugs/1430242>
[18:58] <hatch> wow that bug is very irritating :) 
[19:16] <rick_h_> hatch: you manage to replicate it well enough?
[19:17] <hatch> rick_h_: yep I can replicate it almost at will, and have found where and why it's happening
[19:17] <hatch> rick_h_: https://twitter.com/FromAnEgg/status/576461063941533696
[19:17] <hatch> current status
[19:18] <rick_h_> mutli-user?
[19:18] <hatch> yeah, technically the server is another user
[19:19] <hatch> and - there could be another tab open with another real user
[19:21] <rick_h_> right, but it sounded like this was getting hit aside from multi-user, just setting up a demo
[19:21] <rick_h_> I guess I didn't realize there were multiple clients effecting the annotations in there
[19:21] <hatch> yeah - the root problem is the same, the client has said 'here are my new positions' and then immediately after that goes out, the server says 'here are your positions' 
[19:21] <hatch> because it hasn't been updated 'yet'
[19:22] <hatch> see annotations come wheather there has been a change or not
[19:22] <rick_h_> gotcha, so this is a race during bundle install?
[19:22] <rick_h_> e.g. if you waited for it to settle first you'd be fine?
[19:22] <hatch> whether 
[19:23] <hatch> yeah so I was thinking of a debouncer
[19:23] <hatch> but that still has the problem of 'well which one should win'
[19:23] <hatch> because technically one coming from the server COULD be legit from another user 
[19:23] <rick_h_> well one has a diff right?
[19:23] <hatch> met in standup?
[19:23] <rick_h_> I mean one is the original value and one is a different one?
[19:23] <rick_h_> sure thing