=== StoneTable is now known as aisrael === stokachu_ is now known as stokachu === \b is now known as benonsoftware === wgrant_ is now known as wgrant === Ursinha_ is now known as Ursinha === kadams54 is now known as kadams54-away === mwhudson_ is now known as mwhudson === mwhudson is now known as Guest80728 [08:33] fwereade: you would remember that we discussed writing something like that, but I don't think we ever actualyl did [08:33] jam, ah right :) [08:33] fwereade: what are you doing around now ? :) [08:34] jam, taking the opportunity to code a little while (almost) nobody's around ;p [08:34] understood [08:36] jam, (although if you fancy reviewing either of my branches (or just conversing on the open issues in the first one) I'd be most grateful === mwhudson is now known as mwhudson__ === mwhudson__ is now known as mwhudson [09:38] jam, hey, I thought I needed something like this: http://paste.ubuntu.com/11749789/ ...but it turns out it's not quite as simple as that [09:39] jam, but that general structure looks very familiar [09:41] jam, do you think there's a place for a worker that just serializes ops onto a single goroutine and lets us focus on the op implementation? [09:41] jam, possibly I should be calling them commands not ops? === kadams54 is now known as kadams54-away === Beret- is now known as Beret === Tribaal_ is now known as Tribaal === kadams54 is now known as kadams54-away === kadams54 is now known as kadams54-away === _thumper_ is now known as thumper [22:29] Bug #1467331 opened: configstore lock should use flock where possible [22:38] Bug #1467331 changed: configstore lock should use flock where possible [22:41] Bug #1467331 opened: configstore lock should use flock where possible [23:20] wallyworld: https://github.com/juju/juju/pull/2613 [23:20] wallyworld: review board seems to be not picking up new pulls [23:21] thumper: will look after standup [23:37] thumper: lgtm [23:37] wallyworld: cheers [23:38] wallyworld: the other thought I had was the 1 second timeout [23:38] wallyworld: do you think they might be hitting that? [23:39] thumper: which timeout? is that mentioned in the bug report? [23:40] no... but it is the timeout that that fslock uses [23:40] the lock is only held during the duration of a read or write of the file [23:40] so I originally thought 1s should be more than enough [23:40] however if there are many ops running concurrently, they are serialized through this file [23:41] so perhas 2s? [23:41] I'm not sure [23:41] could just leave it as it is for now [23:41] I suppose [23:41] pretty sure we never hit this before [23:42] * thumper asks the bot to merge [23:42] will forward port to master [23:42] damn it is going to be cold at the gym [23:42] * thumper psychs himself up [23:42] thumper: yeah leave it for now if we haven't seen it before. but if the system has lots to do. may be a factor. i had to introduce reties to lxc ops due to i/o ontention recently [23:50] meh, just noticed bug 1464356 [23:50] Bug #1464356: TestCloudInit fails [23:50] * thumper off to the gym