#instantbird log on 01 26 2014

All times are UTC.

00:17:44 --> FireFly_TB has joined #instantbird
00:45:04 <-- FireFly_TB has quit (Ping timeout)
02:13:06 <-- wnayes has quit (Quit: wnayes)
02:13:53 --> FireFly_TB has joined #instantbird
02:16:23 <-- FireFly_TB has quit (Ping timeout)
02:24:59 --> iamjayakumars has joined #instantbird
02:28:05 <-- iamjayakumars has quit (Quit: )
03:47:11 --> mconley has joined #instantbird
04:59:21 --> nhnt11 has joined #instantbird
05:35:30 <-- Suiseiseki has quit (Ping timeout)
05:50:54 <-- mconley has quit (Input/output error)
05:53:36 --> Suiseiseki has joined #instantbird
06:09:09 <-- nhnt11 has quit (Ping timeout)
06:29:42 --> nhnt11 has joined #instantbird
07:35:03 --> EionRobb has joined #instantbird
07:41:56 <instant-buildbot> build #1243 of win32-nightly-default is complete: Failure [4failed shell_3]  Build details are at http://buildbot.instantbird.org/builders/win32-nightly-default/builds/1243
09:02:39 --> jb has joined #instantbird
09:30:14 <-- EionRobb has quit (Quit: Leaving.)
09:35:31 <-- jb has quit (Ping timeout)
09:39:00 --> FireFly_TB has joined #instantbird
09:40:06 <-- nhnt11 has quit (Ping timeout)
09:45:25 --> nhnt11 has joined #instantbird
09:46:59 <-- FireFly_TB has quit (Quit: FireFly_TB)
09:57:09 <-- nhnt11 has quit (Ping timeout)
09:58:58 --> nhnt11 has joined #instantbird
10:00:40 <-- nhnt11 has quit (Ping timeout)
10:05:24 --> nhnt11 has joined #instantbird
10:05:52 --> jb has joined #instantbird
10:34:49 <-- jb has quit (Ping timeout)
12:23:27 --> jb has joined #instantbird
12:29:24 <-- nhnt11 has quit (Ping timeout)
12:30:38 --> nhnt11 has joined #instantbird
12:57:55 <-- BWMerlin has quit (Ping timeout)
13:06:47 --> BWMerlin has joined #instantbird
13:10:23 <-- jb has quit (Ping timeout)
13:17:19 --> jb has joined #instantbird
13:29:23 <-- jb has quit (Ping timeout)
13:30:47 --> iamjayakumars has joined #instantbird
13:31:43 <-- nhnt11 has quit (Quit: Instantbird 1.6a1pre -- http://www.instantbird.com)
13:31:49 --> nhnt11 has joined #instantbird
13:34:25 --> gerard-majax__ has joined #instantbird
13:43:42 --> clokep has joined #instantbird
13:43:42 * ChanServ sets mode +o clokep 
13:44:58 <-- gerard-majax__ has quit (Ping timeout)
14:00:13 --> gerard-majax__ has joined #instantbird
14:00:35 <-- mrphs has quit (Client exited)
14:00:42 --> mrphs has joined #instantbird
14:17:26 <-- gerard-majax__ has quit (Ping timeout)
14:38:05 <-- iamjayakumars has quit (Client exited)
14:56:33 --> iamjayakumars has joined #instantbird
15:00:18 * stux is now known as stux|away
16:12:10 <-- nhnt11 has quit (Ping timeout)
16:13:29 --> nhnt11 has joined #instantbird
16:13:48 --> gerard-majax__ has joined #instantbird
16:41:21 <-- BWMerlin has quit (Quit: BWMerlin)
16:54:10 --> mconley has joined #instantbird
17:30:54 <clokep> flo-retina: So it seems like the category manager example was changed such that the memory reporter became part of the object (i.e. the object implements nsIMemoryReporter).
17:31:05 <clokep> Is this a reasonable way for us or do we still need a separate memory reported?
17:31:11 <clokep> I'll need to find a different example then.
17:32:06 --> chrisccoulson has joined #instantbird
17:38:19 <-- iamjayakumars has quit (Quit: )
17:45:53 <-- mconley has quit (Input/output error)
18:00:15 --> flo-retina has joined #instantbird
18:00:16 * ChanServ sets mode +qo flo-retina flo-retina 
18:23:23 --> wnayes has joined #instantbird
18:36:53 --> mconley has joined #instantbird
18:39:38 --> Mic has joined #instantbird
18:54:17 <flo-retina> what's the time we wait for the "You are now identified for" message before showing the nickserv prompt?
18:54:33 <flo-retina> I had that prompt again for freenode, there was 7s between the two
18:54:43 <flo-retina> (I thought we waited 10s)
18:55:16 <flo-retina> and I would be curious to know why it's taking that long to get myself identified. I would almost suspect that we are LIST'ing on connect for some reason :(.
18:56:02 <clokep> flo-retina: Off the top of my head It's 10s.
18:56:30 <flo-retina> is it 10s from the prompt, or 10s from the socket connection?
18:57:04 <clokep> By "prompt" do you mean when NickServ says "You are not identified...blah blah"?
18:57:09 <flo-retina> I think we've got a bug somewhere, but I'd like to understand the steps to reproduce so that I can file something useful
18:57:12 <clokep> It should be from that.
18:57:12 <flo-retina> yes
18:57:22 <clokep> Give me a second.
18:58:58 <clokep> flo-retina: http://lxr.instantbird.org/instantbird/source/chat/protocols/irc/ircServices.jsm#215 The comment says "one second", but it's 10,000 in the setTimeout.
18:59:01 <flo-retina> a day if you want; I don't thave the STRs anyway
18:59:48 <flo-retina> there must be an edge case somewhere :(
19:00:09 <clokep> I wonder if a message is slightly different from a different server? :-\
19:08:43 <flo-retina> want a pastebin of the messages in my nickserv conv?
19:09:03 <clokep> Maybe. Do we have a bug open about this?
19:09:58 <flo-retina> I don't know / don't think so
19:10:09 <flo-retina> has anybody managed to create a search URL for our bugs?
19:11:14 <clokep> I haven't. :-\ I've still been searching BIO.
19:11:21 <clokep> I can take a look at the messages though, yeah.
19:11:49 <flo-retina> clokep: http://pastebin.instantbird.com/556420
19:13:01 <clokep> Looks like it matches http://lxr.instantbird.org/instantbird/source/chat/protocols/irc/ircServices.jsm#212 :-S
19:13:47 <clokep> Unless http://lxr.instantbird.org/instantbird/source/chat/protocols/irc/ircServices.jsm#192 isn't working for some reason.
19:15:33 <flo-retina> is that the leaky timer we don't cleanup on disconnect?
19:15:37 <clokep> Or if it's taking more than 10 seconds to parse something or whatever, as you said.
19:15:45 <flo-retina> (the leak shouldn't affect opening the conv though)
19:15:56 <clokep> That sounds kind of familiar.
19:16:01 <flo-retina> well, there's 7s between the 2 displayed timestamps
19:16:59 <flo-retina> I would assume the timestamps are not from when the message arrived on the socket, but from when we parsed it. So I don't think there could have been 10s between parsing the 2 messages
19:17:01 <clokep> Yeah, that's what is confusing me.
19:17:49 <flo-retina> well, something, somewhere is wrong ;).
19:18:08 <clokep> :) I agree.
19:18:53 <-- nhnt11 has quit (Ping timeout)
19:59:01 <-- nathanr has quit (Ping timeout)
19:59:59 --> nathanr has joined #instantbird
20:01:18 --> EionRobb has joined #instantbird
20:14:02 <-- mconley has quit (Input/output error)
20:25:07 <-- Mic has quit (Quit: Instantbird -- http://www.instantbird.com)
20:35:50 --> josefec has joined #instantbird
20:36:45 <-- josefec has quit (Quit: Instantbird 1.5 -- http://www.instantbird.com)
20:59:31 --> mconley has joined #instantbird
21:08:18 <-- mconley has quit (Input/output error)
21:16:38 --> mconley has joined #instantbird
21:27:18 <-- gerard-majax__ has quit (Ping timeout)
21:33:26 <flo-retina> I think I'll need to update that addon to be pinged by keywords.
21:33:47 <flo-retina> I would like to answer GSoC question on #introduction or #developers, but I don't want to have these channels open all the time (I keep them on hold)
21:43:26 * clokep wonders if Florian saw his question from this morning.
21:50:29 <flo-retina> clokep: no, my computer was sleeping this night (usually it stays connected when it stays at home), so I didn't have scrollback and didn't think of checking the logs :-[
21:51:39 <flo-retina> clokep: ah. Probably not, but I can't give a definitive answer without looking at the code
21:59:02 <flo-retina> clokep: is everything else working if you don't compile purpleMemory?
21:59:14 <-- mconley has quit (Input/output error)
21:59:33 <flo-retina> (if purpleMemory is really annoying for you, I could likely handle it during one of the evenings of next week)
22:30:11 --> mconley__ has joined #instantbird
22:36:22 <-- mconley__ has quit (Ping timeout)
22:49:56 --> mconley has joined #instantbird
22:55:49 * flo-retina is still frustrated by whowas giving a timestamp in a random unspecified timezone
22:56:13 <flo-retina> I remember we discussed it before; I don't remember if that was blocked on technical challenges, or finding someone with time to look into it
23:09:07 <clokep> flo-retina: What timestamp?
23:11:41 <instant-buildbot> build #1744 of macosx-nightly-default is complete: Failure [4failed shell_3]  Build details are at http://buildbot.instantbird.org/builders/macosx-nightly-default/builds/1744
23:13:14 <flo-retina> clokep: http://i.imgur.com/TlDoQDj.png
23:13:27 <flo-retina> also, that should say "Offline", not "Unknown"
23:14:00 <-- Even has quit (Ping timeout)
23:14:41 <flo-retina> clokep: the behavior I would like is the status being shown as "Offline", and a line saying "Last online: 22 minutes ago"
23:26:27 <clokep> flo-retina: I see. I don't remember exactly why we can't do that.
23:27:48 <flo-retina> clokep: I think you said that whowas answer is non-standard, or something like that
23:28:03 <clokep> Most likely that.
23:28:44 <flo-retina> which I would be tempted to say is a lame excuse, as the non-standardness if nickserv didn't stop us before ;)
23:29:12 <flo-retina> s/if/of/
23:32:23 <EionRobb> it happens in pidgin, must be doable in instantbird ;)
23:33:04 <flo-retina> EionRobb: really?
23:33:32 <flo-retina> EionRobb: I didn't know Pidgin automatically /whois'ed and then fell back on /whowas when hovering a nick in a conversation :-P.
23:33:34 <EionRobb> http://i.imgur.com/khcjcxk.png
23:34:20 <flo-retina> EionRobb: that screenshot doesn't seem very relevant to this discussion. I'm talking specifically about nicks that aren't online
23:34:24 <EionRobb> no, not in tooltips in the get info
23:34:33 <EionRobb> sure gimme an example for one who's offline
23:34:40 <EionRobb> whois and whowas are treated the same in pidgin
23:34:44 <flo-retina> the nick in my screenshjot ;)
23:35:13 <EionRobb> http://i.imgur.com/l7ls4Np.png
23:35:15 <flo-retina> clokep: is that "Online since" line something we purposefully don't display?
23:35:41 <flo-retina> EionRobb: so it displays the same useless crap as Instantbird ;).
23:36:25 <flo-retina> Btw, I think if the username starts with chatzilla@, and the "name" is "New Now Know How", we should just drop that line. It's noise, not info ;).
23:37:59 <EionRobb> libpurple is listening to the 317 message for the sign on timestamp.  is there a different one for whowas?  I don't see it
23:38:37 <EionRobb> oh, 312?
23:39:41 <flo-retina> clokep: btw, I don't think the "Online since" line is useful (just in case my previous comment was ambiguous)
23:52:21 <clokep> flo-retina: I don't know if we don't display that or where that's coming from w/o researching more.