[01:56] hi [01:57] howdy [02:21] The private team blogpost is so confusing! [02:24] heh, all the privacy stuff tends to lean that way I think. It's a hard thing to solve/get right [02:25] I read twice and it took me 5 minutes to understand what the blog post meant. [02:25] I'm still not confident yet. [13:50] lifeless: a day later than promised: https://code.launchpad.net/~jml/testtools/assert-raises-lambda/+merge/90574 [13:58] * jml gone [21:24] lifeless, around by any chance? [22:56] fsvo [23:01] hi lifeless [23:01] I'm a bit confused by oops-tools currently [23:02] I can trigger an oops at http://ec2-107-22-26-52.compute-1.amazonaws.com/pkgme/+oops and I can see it go across amqp and it's apparently inserted in to the db at http://ec2-107-20-69-109.compute-1.amazonaws.com/?oopsid=OOPS-884555d8407b0fe9fc62ce0f34094370 but it says there's no matching oopses [23:03] select * from oops_oops where oopsid = ' [23:03] OOPS-884555d8407b0fe9fc62ce0f34094370' [23:03] ; [23:03] (e.g. have a direct poke at the DB) [23:03] james_w: what consumer are you using to pull it off of amqp ? [23:03] amqp2disk [23:04] hmm, maybe it's a setup issue actually [23:06] (1 row) [23:13] ok, so if a literal lookup matches, in the DB, it is inserted [23:13] and the view should always be searching on the literal string regardless of any heuristics [23:18] ah, I think it was running amqp2disk with a relative pathname [23:19] the exists() check was failing [23:21] http://ec2-107-20-69-109.compute-1.amazonaws.com/?oopsid=OOPS-c470f2678fd5ff65b48a522ae1a35816 [23:22] yes [23:22] nice [23:23] shiny shiny [23:23] it seems like timeline/oops-tools need to be generalised at bit? [23:23] oops-tools assumes that everything is sql? [23:24] well [23:24] the UI certainly claims it does [23:24] and it does the %s %d substitution on everything [23:25] OTOH thats working quite well for LP for e.g. librarian downloads and so on - mapping different librarian requests to one pattern for aggregation [23:25] if you would like to make it better, would definitely love to see that [23:29] I need to work out why the sql hooks aren't working here [23:30] http://ec2-107-20-69-109.compute-1.amazonaws.com/?oopsid=OOPS-304f3e703162fa09f30065c7d582c890 is from when they were [23:32] it seems like you're finding this a bit tricky to debug / sort out [23:32] if you have suggestions for making that process easier, +1 [23:37] well, it's complicated by the fact that my internet is crappy today and I'm doing this remotely [23:37] plus timeline_django is pretty damn hacky, so it's going to be fragile