=== kadams54 is now known as kadams54-away === kadams54-away is now known as kadams54 [17:50] uiteam lf a review and qa on https://github.com/juju/juju-gui/pull/706 [17:50] the diff looks huge but thats just because of a json response object update [18:28] bug #1430242 [18:28] Bug #1430242: cannot change charm location most of the time

[18:58] wow that bug is very irritating :) === kadams54 is now known as kadams54-away [19:16] hatch: you manage to replicate it well enough? [19:17] rick_h_: yep I can replicate it almost at will, and have found where and why it's happening [19:17] rick_h_: https://twitter.com/FromAnEgg/status/576461063941533696 [19:17] current status [19:18] mutli-user? [19:18] yeah, technically the server is another user [19:19] and - there could be another tab open with another real user [19:21] right, but it sounded like this was getting hit aside from multi-user, just setting up a demo [19:21] I guess I didn't realize there were multiple clients effecting the annotations in there [19:21] 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] because it hasn't been updated 'yet' [19:22] see annotations come wheather there has been a change or not [19:22] gotcha, so this is a race during bundle install? [19:22] e.g. if you waited for it to settle first you'd be fine? [19:22] whether [19:23] yeah so I was thinking of a debouncer [19:23] but that still has the problem of 'well which one should win' [19:23] because technically one coming from the server COULD be legit from another user [19:23] well one has a diff right? [19:23] met in standup? [19:23] I mean one is the original value and one is a different one? [19:23] sure thing === kadams54-away is now known as kadams54 === kadams54 is now known as kadams54-away