[00:06] <thumper> davechen1y: ping
[00:09] <davechen1y> ack
[00:09] <davechen1y> thumper: ack
[00:09] <thumper> davecheney: hangout?
[00:09] <davecheney> yy
[00:10] <thumper> davecheney: have you got video working?
[00:10] <davecheney> no video on this x220
[00:10] <thumper> why?
[00:10] <thumper> that is a thinkpad right?
[00:10] <davecheney> you can video, but bodgy sound (via n7) or good sound, and no video
[00:10] <thumper> davecheney: what about skype?
[00:10] <davecheney> sure, lemme install it
[00:10] <davecheney> i had al lthe tools on my mac
[00:11] <davecheney> but it died while I was on vacation
[00:11] <thumper> :(
[00:11] <davecheney> and a long series of sad stories and trips to the apple store have not resulted in it working again
[00:11] <thumper> I've tried to avoid apple hardware as much as possible
[00:11] <thumper> don't want to start down that track
[00:11] <thumper> I do know others that are almost 100% in to it
[00:12] <thumper> like popey and njpatel
[00:12] <davecheney> i think avoiding it is a good idea
[00:12] <davecheney> they use bcm wifi chips which are poorly supported
[00:12] <thumper> so I'm looking for a non-apple macbook air type equivalent
[00:13] <thumper> small, thin, metallic (robust), with good battery life
[00:13] <davecheney> stay away from dells
[00:13] <davecheney> they are all junk
[00:13] <davecheney> the X1 isn't bad
[00:13] <davecheney> lenvovo x1
[00:13] <davecheney> some of the samsung ultrabooks are quite nice
[00:13] <davecheney> byut hard to get in au
[00:13] <thumper> oh, I forgot cheap (ish)
[00:13] <davecheney> so i havne't seen many in the flesh
[00:14] <thumper> I've seen quite a few samsung ultrabooks here
[00:14] <thumper> jb hifi has them here
[00:14] <davecheney> some are ok, some are just weird
[00:14] <davecheney> stay away from sony stuff, that is actually wierd
[00:14] <davecheney> weird
[00:14] <thumper> I had a sony laptop a while back, proprietary hardware, non-open drivers caused a pain
[00:14] <davecheney> yeah, total crap shoot
[00:15] <davecheney> asus make a lot of models
[00:15] <davecheney> its going to have very very stock hardware inside
[00:15] <davecheney> some of them are ok, but for me it is hard to shake their reputation as making cheap and nasty kit
[02:02] <davecheney> thumper: it's lunch o clock now, afk for prob 40-60 mins to get some lunch for me and my misses
[02:30] <thumper> davecheney: ack
[02:30] <thumper> davecheney: let me know when you're back
[02:46]  * thumper afk for a bit
[03:20] <davecheney> thumper: ping
[03:20] <thumper> hey, just otp
[03:21] <davecheney> no wuks
[03:23] <thumper> kk , ready now
[03:23] <thumper> davecheney: skype again?
[03:24] <davecheney> y
[08:02] <rogpeppe> mornin' all
[08:44] <elimisteve> morning
[08:47] <dimitern> hey all, william asked me to tell you there's a power cut in his area at present, in case you wonder where is he
[08:50] <TheMue> dimitern_afk: Thx for the notification. And good morning btw. ;)
[08:51] <elimisteve> any estimates on when juju 2.0 will be out?
[08:51] <elimisteve> good job making so much progress on the Go port, all. Very exciting...
[08:51] <elimisteve> is v2.0 when the Go version will be the primary one that you encourage people to use?
[09:01] <jam> elimisteve: the goal is to have the Go port the default version for 13.04 (Ubuntu Raring)
[09:02] <elimisteve> jam: great, thanks
[10:17] <dimitern> TheMue: morning :)
[10:17] <TheMue> dimitern: Hiya
[10:33] <dimitern> i think it's high time to do something about keeping the channel topic in sync with what's happening in the project, so the people could get an idea quickly, like #launchpad channels
[10:37] <TheMue> dimitern: oh, yes, good hint
[11:14] <rogpeppe> fwereade: yo!
[11:14] <rogpeppe> fwereade: power back then, i guess
[11:14] <dimitern> fwereade: hey
[11:15] <fwereade> rogpeppe, heyhey; and, yeah, a little while ago, but I forgot to open irc again ;0
[11:15] <fwereade> dimitern, heyhey
[11:15] <fwereade> rogpeppe, I'm getting the rpc module tests timing out after 600s
[11:15] <rogpeppe> fwereade: i *just* realised that i forgot to put in the timeouts you requested
[11:15] <fwereade> rogpeppe, haha
[11:15] <rogpeppe> fwereade: am currently editing rpc_test.go!
[11:15] <rogpeppe> fwereade: (as of 5 mins ago...)
[11:16]  * fwereade gets to feel all smug and prophetic ;p
[11:16] <rogpeppe> bah :-)
[11:16] <dimitern> fwereade: do you want to discuss shortly https://codereview.appspot.com/7301085/ ?
[11:19] <fwereade> dimitern, sgtm, I'll start a hangout
[11:20] <dimitern> fwereade: cool
[11:22] <dimitern> fwereade: actually, since it's almost standup time, can we do it around 13h?
[11:22] <jam> allenap: poke
[11:22] <jam> I'm just checking on https://code.launchpad.net/~allenap/juju-core/break-out-juju-store/+merge/142564
[11:23] <jam> and seeing if you need it landed, or if it needs updating, etc.
[11:23] <allenap> jam: Hello.
[11:23] <jam> The last comment was only a few days ago, so I think I can just land it for you/
[11:23] <jam> ?
[11:23] <allenap> jam: I /think/ it's up to date, but I'll check.
[11:23] <fwereade> dimitern, ah, yeah, sure -- might be eating then, but ping me when you're free and we'll figure something out
[11:23] <dimitern> fwereade: sure, no rush
[11:24] <TheMue> lunchtime
[11:25] <niemeyer> rogpeppe: Anything else on https://codereview.appspot.com/7313081/?
[11:26] <rogpeppe> niemeyer: looking
[11:27] <rogpeppe> niemeyer: i think zero is a reasonable length for a file, and i think think PutAll should work with all files
[11:27] <niemeyer> rogpeppe: It's not up to us
[11:27] <niemeyer> rogpeppe: It does work, though
[11:28] <niemeyer> rogpeppe: But we can't test that live
[11:28] <rogpeppe> niemeyer: why not?
[11:28] <niemeyer> rogpeppe: Because it's not up to us whether an upload works with no content or not
[11:28] <allenap> jam: Yes, it's up to date.
[11:29] <rogpeppe> niemeyer: if it doesn't work, we should return an error
[11:30] <niemeyer> rogpeppe: Amazon returns the error
[11:30] <rogpeppe> niemeyer: if the file length is zero, we don't make any calls for amazon to return the error, no?
[11:31] <niemeyer> rogpeppe: Multipart uploads of files of length zero do not work
[11:31] <niemeyer> rogpeppe: I don't know what you're trying to achieve
[11:31] <rogpeppe> niemeyer: i'd like to be able to iterate over all the files in a directory and call PutAll on each one, regardless of the file's size
[11:31] <allenap> jam: Forgot to say: yes, please, I'd be grateful if you could land it :)
[11:32] <rogpeppe> niemeyer: presumably you're allowed buckets holding zero-length files?
[11:32] <niemeyer> rogpeppe: *multipart uploads*.. that's what this CL is about
[11:32] <niemeyer> rogpeppe: and I can understand your desire.. you should file a bug against S3. :-)
[11:33] <rogpeppe> niemeyer: PutAll works with a file that's 1 byte long. i think it should work if it's 0 bytes long, and i don't think it's hard to make it do that.
[11:34] <rogpeppe> niemeyer: perhaps it should use multipart only where necessary.
[11:35] <niemeyer> rogpeppe: PutAll is a method on Multi
[11:36] <rogpeppe> niemeyer: ahem, good point :-)
[11:40] <rogpeppe> niemeyer: well at the least, if multipart uploads of files of length zero don't work, we should return an error in that case.
[11:40] <niemeyer> rogpeppe: Sorry, we're going in circles
[11:40] <rogpeppe> [11:31:00] <niemeyer> rogpeppe: Multipart uploads of files of length zero do not work
[11:41] <niemeyer> rogpeppe: Amazon will say so.. I don't think there's any benefit in us reporting it early
 rogpeppe: Amazon returns the error
[11:41] <rogpeppe> niemeyer: ah, you get the error from Complete?
[11:41] <niemeyer> rogpeppe: It will fail in whatever way Amazon chooses to fail
[11:42] <niemeyer> rogpeppe: Just like everything else
[11:43] <niemeyer> rogpeppe: Look.. I can put an error result there if that makes you happier
[11:43] <rogpeppe> niemeyer: ok, that seems reasonable - perhaps a doc comment rather than an error - amazon may fix it in the future, i suppose.
[11:43] <niemeyer> rogpeppe: It may
[11:44] <rogpeppe> niemeyer: (failing when amazon chooses to fail seems reasonable, i mean)
[11:44] <niemeyer> rogpeppe: Cool
[11:49] <rogpeppe> niemeyer: replied
[11:49] <niemeyer> rogpeppe: Actually, I just found a way to make it work
[11:49] <niemeyer> rogpeppe: I'll fix it
[11:50] <rogpeppe> niemeyer: cool. the less edge cases, the better i like it :-)
[11:50] <niemeyer> rogpeppe: Amazon happily takes it if I upload a part with zero content
[11:50] <niemeyer> rogpeppe: It is an edge case still
[11:50] <rogpeppe> niemeyer: only for goamz, not for the person using it, hopefully
[11:50] <niemeyer> rogpeppe: It is an edge case for the API
[11:51] <niemeyer> rogpeppe: People may not care in most sane cases, though
[11:51] <niemeyer> rogpeppe: The result of len(parts) with no content is 1 rather than 0
[11:52] <rogpeppe> niemeyer: yeah. it seems reasonable that a file should always have at least one part though.
[11:52] <rogpeppe> niemeyer: even if it's zero-length.
[11:52] <niemeyer> rogpeppe: It's an edge case.
[11:53] <rogpeppe> niemeyer: agreed. seems like the least-surprises way forward though.
[11:54] <niemeyer> rogpeppe: As I said, I'll fix it
[11:54] <rogpeppe> niemeyer: cool, thanks.
[12:00] <niemeyer> rogpeppe: np, thanks for the review
[12:01] <niemeyer> In the future we can have an API in Bucket itself which chooses properly whether to upload a multipart or not based on size
[12:01] <niemeyer> But I'd rather fix the overall package API first
[12:14] <rogpeppe> niemeyer: that sounds good
[12:16] <rogpeppe> niemeyer: i thought i remembered that dave cheney made some fixes to gocheck so that c.Logf wasn't racy if called in multiple goroutines. am i imagining things? (i get lots of errors from the race detector, which would be nice not to see)
[12:16] <niemeyer> rogpeppe: Probably lying in the queue
[12:16] <niemeyer> rogpeppe: I'll have a look later
[12:16] <rogpeppe> niemeyer: ok, cool.
[12:17] <rogpeppe> niemeyer: i was initially slightly worried by my 5 data races :-)
[12:18] <niemeyer> rogpeppe: Yeah, quite misleading
[12:20] <rogpeppe> fwereade: fairly trivial. https://codereview.appspot.com/7324046
[12:21] <rogpeppe> fwereade: and i'd like to know where your tests fail with this applied.
[12:36] <jam> allenap: btw, I'm changing the signature of one of the testing/charm.go apis, which effects "store/branch_test.go" and "store/store_test.go".
[12:39] <jam> rogpeppe: so I see the tests hanging as well, and it is nice to not have them hang, but doesn't that mean the test is actually still failing?
[12:39] <rogpeppe> jam: yeah - it shouldn't happen, but tests pass for me.
[12:41] <rogpeppe> jam: until i can reproduce the problem, i'm not going to be able to fix the bug
[12:42] <jam> rogpeppe: http://paste.ubuntu.com/1643683/
[12:42] <jam> rogpeppe: are you running go 1.1 or some variant thereof?
[12:42] <jam> I was running go1 (default on precise) but it turns out lbox doesn't work with it.
[12:42] <rogpeppe> jam: yes - although i think i've run the tests on 1.0.2
[12:43] <jam> So I'm now running go-1.0.3 from ~gopher's ppa
[12:43] <rogpeppe> jam: ah!
[12:43] <rogpeppe> jam: this probably is highly indicative: cannot unmarshal null into Go value of type rpc_test.stringVal
[12:43] <jam> rogpeppe: yeah, it says the same for the struct{} object.
[12:45] <rogpeppe> jam: i guess i only ran the live tests against 1.0.2.
[12:45] <rogpeppe> jam: because i see the same failure.
[12:45] <rogpeppe> jam: thanks.
[12:45] <jam> rogpeppe: yeah, prob just a json change between go std lib and how they handle nil
[12:45] <rogpeppe> jam: yes, i think so
[12:58] <fwereade> rogpeppe, http://paste.ubuntu.com/1643711/
[12:58] <fwereade> rogpeppe, ha, just like jm's
[12:58] <fwereade> rogpeppe, sorry
[12:58] <rogpeppe> fwereade: yeah, i'm on it. it's a go1.1 compatibility issue
[12:58] <rogpeppe> fwereade: np
[13:18] <allenap> jam: Okay, once you've done that, I'll merge the relevant changes into juju-store. Or, do you want to land my branch before making your changes, and I'll fix-up juju-store?
[13:32] <jam> allenap: it doesn't change your branch, it is just going to break juju-store
[13:32] <jam> your branch and mine have both landed.
[13:32] <jam> so you'll just want to touch juju-store
[13:32] <jam> which is generally just removing a parameter.
[13:32] <allenap> jam: Okay, I'll look into that. Thanks for sorting this out!
[13:33] <jam> allenap: lp:~jameinel/juju-core/no-symlinks is the branch, you can look at -r -2
[13:33] <jam> but it is basically just remove: "series" being passed.
[13:41] <TheMue> fwereade, rogpeppe: time for a first review? https://codereview.appspot.com/7323059
[14:01] <rogpeppe> TheMue: will look after lunch
[14:01]  * rogpeppe goes for lunch
[14:01] <TheMue> rogpeppe: Great, thx.
[14:01] <TheMue> rogpeppe: Enjoy.
[14:24] <dimitern> fwereade_: is it usual for the worker/uniter tests to take long?
[14:24] <fwereade_> dimitern, yes, afraid so
[14:24] <fwereade_> dimitern, I wasn't avle to find any particular hotspots
[14:24] <dimitern> fwereade_: ok :)
[14:28] <fwereade_> TheMue, please remind me: how's public storage useful to the local provider?
[14:29] <fwereade_> TheMue, won't it implicitly upload tools anyway, rendering the whole thing redundant?
[14:29] <fwereade_> s/upload/"upload"/
[14:31] <dimitern> fwereade_: *** Test killed: ran too long. ??
[14:31] <fwereade_> dimitern, ok, no, they shouldn't take that long
[14:31] <dimitern> fwereade_: am I doing something wrong?
[14:31] <dimitern> fwereade_: I just run go test ./... in worker/uniter
[14:32] <dimitern> fwereade_: does it need internet access during the tests?
[14:32] <fwereade_> dimitern, no, shouldn't do, and that sounds sane (even if I always run from root -- go test ./worker/uniter/... -- but I doubt that's remotely relevant)
[14:33] <dimitern> fwereade_: hmm, well I'll try running them in order going into each subdir to see which one is to blame
[14:33] <fwereade_> dimitern, I'm just running them myself, because I forget exactly how long they should take -- enough to be annoying, certainly, but nowhere near test timeout limit
[14:33] <dimitern> fwereade_: ah, actually it shows - FAIL	launchpad.net/juju-core/worker/uniter/charm	600.002s
[14:34] <dimitern> fwereade_: all others are ok
[14:34] <fwereade_> dimitern, hmm, very interesting: try that one with -test.v -gocheck.vv
[14:35] <dimitern> fwereade_:  [LOG] 58.01524 JUJU mongod: error command line: unknown option sslOnNormalPorts
[14:35] <dimitern> [LOG] 58.01531 JUJU mongod: use --help for help
[14:35] <dimitern> that's almost immediately at the beginning
[14:35] <fwereade_> dimitern, what mongo build are you using?
[14:35] <dimitern> fwereade_: and it just stays there
[14:35] <dimitern> fwereade_: mongod -v?
[14:36] <fwereade_> dimitern, did you get the special version with ssl support?
[14:36] <dimitern> fwereade_: git version: d1b43b61a5308c4ad0679d34b262c5af9d664267
[14:36] <fwereade_> dimitern, it's in an ec2 bucket somewhere iirc
[14:36] <dimitern> fwereade_: not sure, I might have installed it from the archive
[14:36] <fwereade_> dimitern,     http://juju-dist.s3.amazonaws.com/tools/mongo-2.2.0-precise-amd64.tgz
[14:36] <dimitern> fwereade_: it says 2.2.2
[14:37] <fwereade_> dimitern, you need this build for SSL support, which is not optional
[14:37] <dimitern> fwereade_: how about quantal?
[14:37] <fwereade_> I suspect there's one if you s/precise/quantal/
[14:37] <dimitern> fwereade_: same version?
[14:37] <fwereade_> dimitern, yeah, think so
[14:38] <fwereade_> dimitern, take a look at the bucket in a browser, I think it lists everything for you anyway
[14:38] <dimitern> fwereade_: and I should purge the currently installed mongo as well?
[14:38] <fwereade_> dimitern, up to you, but make sure the tests find the ssl version
[14:38] <dimitern> fwereade_: the bucket reports access denied on dir listing, but direct link works
[14:38] <fwereade_> dimitern, ah ok, maybe that changed
[14:39] <dimitern> fwereade_: where should I put the extracted tarball?
[14:41] <dimitern> fwereade_: anywhere in $PATH should work?
[14:41] <fwereade_> dimitern, yeah, should be fine
[14:43] <dimitern> fwereade_: great, 10x - now the tests pass ok and fast
[14:45] <TheMue> fwereade_: Sorry, phone
[14:46] <fwereade_> TheMue, np
[14:47] <TheMue> fwereade_: Maybe oriented too much at the dummy environ. If I've seen right it also uses two different storage that are returned by Environ.
[14:48] <fwereade_> TheMue, in the doc we agreed to just return an empty storage
[14:48] <fwereade_> TheMue, and I'm confused by the way they appear to share a port..?
[14:49] <fwereade_> TheMue, if we can just do a dumb empty-on-list, err-on-get StorageReader I think that lets us drop all this confusing private/public stuff
[14:49] <TheMue> fwereade_: The URL depends on the environ name and if it is started as private or public. And it is empty.
[14:50] <fwereade_> TheMue, it kinda looks like an awful lot of additional complexity to save two one-line methods on a new type
[14:51] <TheMue> fwereade_: Please note it in the review.
[14:51] <fwereade_> TheMue, will do, just checking in case I was missing something obvious
[14:52] <TheMue> fwereade_: To me the symetric usage of the storage has been more simple.
[15:03] <rogpeppe> fwereade_: meeting?
[15:46] <fwereade_> rogpeppe, a thought: is the set of available arches not the intersection of those available on the provider with those we can find tools for?
[15:47] <rogpeppe> fwereade_: that seems a reasonable thought
[15:47] <fwereade_> rogpeppe, in which case I don't really think it's ok to require that someone recompile the client to use another cloud...
[15:48] <fwereade_> rogpeppe, additional exercise: how are we meant to discover those values from the CLI? I don;t think we can safely assume the existence of an environments.yaml
[15:48] <fwereade_> rogpeppe, sure, we won;t figure out how to drop it *soon*
[15:48] <fwereade_> rogpeppe, but still...
[15:48] <rogpeppe> fwereade_: GUI clients won't have environments.yaml
[15:49] <fwereade_> rogpeppe, indeed
[15:49] <rogpeppe> fwereade_: i didn't mean to suggest we should recompile the client to use another cloud
[15:49] <rogpeppe> fwereade_: one mo, i need to interact in #juju-gui
[15:50] <fwereade_> rogpeppe, I admit, I put those words into your mouth, but I think it's a consequence of specifying the list of "available" architectures on the client
[15:50] <fwereade_> rogpeppe, np
[16:18] <TheMue> fwereade_: Just proposed a change with no more separation between public and private but with using environs.EmptyStorage.
[16:19] <fwereade_> TheMue, awesome
[16:19] <fwereade_> TheMue, whoops, I never actually hit m
[16:19] <fwereade_> TheMue, I'll drop the redundant comments
[16:22] <fwereade_> TheMue, sent a couple, let me know what you think
[16:23] <TheMue> fwereade_: yep, cheers
[16:28] <TheMue> fwereade_: Yep, both makes sense, storage-port (maybe more settings for the storage backend will follow) and the comments. As you see I so far mostly panic, it's just an interface copy for quick compilation. ;)
[16:29] <fwereade_> TheMue, cool, thanks
[17:30] <fwereade_> rogpeppe, is trunk still expected to be broken?
[17:30] <rogpeppe> fwereade_: yes. here's a branch to fix it: https://codereview.appspot.com/7324048
[17:30] <rogpeppe> fwereade_: sorry about the delay.
[17:31] <rogpeppe> fwereade_: it took a little more than i expected.
[17:31] <fwereade_> rogpeppe, no worries, just syncing up
[17:31] <rogpeppe> fwereade_: review appreciated
[17:31] <rogpeppe> dimitern, jam, anyone else: ^
[17:31] <dimitern> rogpeppe: i'll take a look
[17:31] <rogpeppe> dimitern: ta!
[17:36] <fwereade_> rogpeppe, looking good so far; you might be interested in https://codereview.appspot.com/7324049
[17:37] <fwereade_> rogpeppe, LGTM
[17:38] <rogpeppe> fwereade_: thanks
[17:38] <fwereade_> aaaand I'm done for now -- but I might pop back on later
[17:38] <fwereade_> gn all
[17:42] <dimitern> rogpeppe: reviewed
[17:42] <rogpeppe> dimitern: thanks! submitted.
[17:42] <rogpeppe> fwereade_: gn
[18:33] <rogpeppe> right, that's me for the day. first watcher test now failing in a useful way.
[18:33] <rogpeppe> g'night all
[19:57] <thumper> morning
[20:01] <thumper> mramm: morning, you around now
[20:01] <thumper> ?
[20:02] <mramm> thumper: yep
[20:02] <mramm> I was just about to send an e-mail because I will be out most of the day tomorrow
[20:12] <fwereade_> thumper, heyhey -- I have a grumpy daughter who might take a while to get to sleep, but hope to be able to swing by again later
[20:12] <thumper> fwereade_: ok, np
[20:36] <benji> "go install launchpad.net/juju-core/cloudinit: open /usr/lib/go/pkg/linux_386/launchpad.net/juju-core/cloudinit.a: no such file or directory"
[20:37] <benji> that happens when I run "go get -v launchpad.net/juju-core/..."
[20:38] <thumper> hi benji
[20:39] <benji> hi!
[20:39] <thumper> benji: I can't help, but just saying hi
[20:39] <benji> heh
[20:39] <benji> actually, that looks like a permission problem, I guess it should be "sudo go get [...]"
[20:47] <thumper> benji: well, should only need sudo if you don't have a go path set, no?
[20:57] <rogpeppe> benji, thumper: definitely no need to use sudo
[20:57] <thumper> hi rogpeppe
[20:57] <thumper> rogpeppe: why are you still up?
[20:57] <rogpeppe> benji: looks like you might not have GOPATH set
[20:57] <thumper> or online at least
[20:57] <rogpeppe> thumper: i'm not :-)
[20:57] <rogpeppe> thumper: honest
[20:57] <thumper> so this is your irc bot then?
[20:57] <rogpeppe> yup
[20:57] <rogpeppe> rog made me very clever
[20:58] <thumper> are you up for a chat at some stage?
[20:58] <benji> hmm, GOPATH is set
[20:58] <rogpeppe> benji: and exported?
[20:58] <rogpeppe> thumper: definitely
[20:58] <benji> yep
[20:58] <thumper> rogpeppe: when would be good?
[20:58] <thumper> bit of an issue with you being on the other side of the planet
[20:58] <rogpeppe> thumper: when's good for you?
[20:59] <thumper> rogpeppe: ideally between 9 and 5 local :)
[20:59] <thumper> heh
[20:59] <rogpeppe> thumper: what's your time zone?
[20:59] <thumper> UTC+13
[20:59] <rogpeppe> thumper: what time is it now for you/
[20:59] <rogpeppe> ?
[20:59] <thumper> 10am
[20:59] <benji> well, either way "go get -v launchpad.net/juju-core/..." (no sudo) now works, I haven't touched GOPATH since it failed <shrug>
[21:00] <rogpeppe> thumper: 10am thursday?
[21:00] <thumper> yes
[21:02] <rogpeppe> thumper: busy for probably an hour, but should be able to make half an hour or so after that, if you're around all today
[21:02] <rogpeppe> thumper: i'll ping you
[21:02] <thumper> ok
[21:18] <fwereade> thumper, ping
[21:18] <thumper> fwereade: hi
[21:19] <fwereade> thumper, heyhey, I'm free for a chat if you like -- g+?
[21:19] <thumper> fwereade: g+ sounds good
[22:05] <rogpeppe> thumper: ping
[22:05] <thumper> rogpeppe: hey, just talking with fwereade now
[22:05] <rogpeppe> thumper: i could join if you fancy it
[22:06] <rogpeppe> thumper: depends what you're chatting about really
[22:06] <thumper> rogpeppe: propable one on one intially would be better
[22:06] <rogpeppe> thumper: sounds good
[22:07] <rogpeppe> thumper: unfortunately my window of opportunity is short tonight, so maybe we won't make it
[22:07] <thumper> rogpeppe: ok, perhaps tomorrow?
[22:07] <rogpeppe> thumper: possibly, though unlikely.
[22:07] <rogpeppe> thumper: evenings not usually good for me.
[22:07] <thumper> rogpeppe: I could get up early
[22:07] <thumper> 17:00 UTC
[22:11] <rogpeppe> thumper: that sounds possible, yeah
[22:12] <rogpeppe> thumper: i'll schedule it in...
[22:12] <thumper> ok
[22:15] <rogpeppe> thumper: you have an invite :-) (means i might get a reminder...)
[22:15] <thumper> :)
[22:16] <rogpeppe> thumper: if you get off chatting with william tonight, ping us anyway. i might still be around.