All times are UTC.
00:05:01 <flo-retina> btw, we need to get our l10n story fixed :( 00:05:25 <clokep> Is l10n stuff not working? 00:05:41 <flo-retina> not at all, since the moz22 update 00:05:57 <flo-retina> the --disable-compile-environment configure flag doesn't work (on linux at least) 00:06:18 <clokep> Oh> :( I didn't know that. 00:07:06 <flo-retina> clokep: http://buildbot-l10n.instantbird.org/builders/translate/builds/696/steps/compile/logs/stdio 00:16:10 <clokep> :-/ Well hopefully...we can figure that out? :) 00:19:50 <flo-retina> clokep: well, I have guesses about what the problem is 00:20:14 <flo-retina> clokep: what puzzles me is that our configure currently looks exactly like c-c's, and the mozilla-central has the same issue (if my guess is right) 00:20:25 <clokep> :-/ 00:20:32 <clokep> Could it be an environment difference? 00:56:25 <-- dew has quit (Ping timeout) 00:56:27 --> dew1 has joined #instantbird 00:59:11 <-- clokep has quit (Quit: Instantbird 1.5a1pre -- http://www.instantbird.com) 01:01:39 <flo-retina> clokep: the point of --disable-compile-environment is that it shouldn't check for stuff in your environment ;). 01:01:59 <flo-retina> it should work even if you don't have any compiler installed. 01:02:07 <flo-retina> So looking for a .h file is obviously wrong. 01:37:39 <-- dew1 has quit (Ping timeout) 02:29:43 --> mconley has joined #instantbird 03:27:25 <-- wnayes has quit (Quit: wnayes) 03:33:06 --> dew has joined #instantbird 03:39:00 <-- mconley has quit (Input/output error) 04:50:02 --> jb has joined #instantbird 05:49:50 <instantbot> firstname.lastname@example.org requested review from florian@instantbird .org for attachment 2784 on bug 2117. 05:49:52 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=2117 nor, --, ---, qheaden, ASSI, /invite should print a system message to show it's done something 06:03:27 <-- jb has quit (Ping timeout) 06:10:46 <-- EionRobb has quit (Quit: Leaving.) 06:13:35 --> mconley has joined #instantbird 06:13:36 <instant-buildbot> build #957 of macosx-nightly-default is complete: Success [build successful] Build details are at http://buildbot.instantbird.org/builders/macosx-nightly-default/builds/957 06:36:03 <-- dionisos has quit (Ping timeout) 06:55:47 --> jb has joined #instantbird 06:56:08 --> EionRobb has joined #instantbird 07:38:29 <-- mconley has quit (Input/output error) 07:56:40 <-- flo-retina has quit (Ping timeout) 08:07:16 --> nhnt11 has joined #instantbird 08:15:34 <-- nhnt11 has quit (Quit: Instantbird 1.5a1pre -- http://www.instantbird.com) 08:15:48 --> nhnt11 has joined #instantbird 08:40:00 --> aleth has joined #instantbird 08:40:00 * ChanServ sets mode +h aleth 08:54:55 <-- jb has quit (Ping timeout) 09:09:06 --> mconley has joined #instantbird 09:14:10 <-- mconley has quit (Ping timeout) 09:47:23 --> flo-retina has joined #instantbird 09:47:24 * ChanServ sets mode +qo flo-retina flo-retina 09:48:09 * flo-retina wonders why is Instantbird downloaded a complete (37+MB) update, then said "the integrity of the update couldn't be verified", then downloaded a partial update of less than 400kB. 09:48:18 <flo-retina> I know nhnt11 has already described this behavior 09:48:23 <flo-retina> it still puzzles me though :-S 09:49:01 <-- flo-retina has quit (Quit: Instantbird 1.5a1pre -- http://www.instantbird.com) 09:49:16 --> flo-retina has joined #instantbird 09:49:16 * ChanServ sets mode +qo flo-retina flo-retina 09:49:42 <flo-retina> hmm, and I think it just crashed. But without opening the crash reporter :-S 09:49:57 <flo-retina> hmm, no, instantbot's log says "Quit: Instantbird 1.5a1pre" 09:50:00 <flo-retina> even more strange 09:50:11 <-- flo-retina has quit (Quit: Instantbird 1.5a1pre -- http://www.instantbird.com) 09:50:31 --> flo-retina has joined #instantbird 09:50:31 * ChanServ sets mode +qo flo-retina flo-retina 09:50:42 <aleth> flo-retina: I filed a bug about that update behaviour a while ago 09:50:57 <flo-retina> wow 09:50:58 <flo-retina> steps to reproduce are trivial 09:51:12 <aleth> bug 1919 09:51:19 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=1919 nor, --, ---, nobody, NEW, Updates whose integrity could not be verified can still be applied 09:51:23 <flo-retina> in the pref window, go to advanced->update->Show Update History. Triple click on the "Details" link. Boom, your Instantbird is gone 09:51:33 <flo-retina> not sure if this is only with "details" links of failed updates or for all of them 09:51:34 <aleth> Wow 09:52:11 <aleth> Triple click? 09:52:15 <flo-retina> if the rainy week-end wasn't over, I would investigate right away 09:52:19 <-- aleth has quit (Quit: Ciao) 09:52:37 --> aleth has joined #instantbird 09:52:38 * ChanServ sets mode +h aleth 09:52:41 <flo-retina> well, yeah, "click more than twice". 09:52:50 <aleth> You weren't kidding :P 09:52:55 <flo-retina> no, I wasn't 09:53:02 <aleth> Bizarre. 09:53:06 <flo-retina> although that could be an April fool joke ;) 09:53:13 <aleth> Especially as clicking once doesn't do anything ;) 09:53:22 <flo-retina> aleth: did you click on a "detail" link of a failed update, or a successful one? 09:53:29 <aleth> A successful one. 09:53:30 <flo-retina> aleth: twice didn't seem to do anything either 09:53:37 <flo-retina> that's why I clicked frenetically :-D 09:54:24 <aleth> Clicking once gives "No chrome package registered for chrome://navigator/content/navigator.xul" 09:54:37 <-- aleth has quit (Quit: Ciao) 09:54:48 --> aleth has joined #instantbird 09:54:48 * ChanServ sets mode +h aleth 09:55:00 <aleth> And then it still crashes, when you close that window... 09:55:26 <instantbot> New Instantbird (UI) bug 2127 filed by email@example.com. 09:55:28 <flo-retina> is that in the error console? 09:55:29 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=2127 cri, --, ---, nobody, NEW, Triple clicking the Details links of the Update history dialog quits Instantbird 09:55:30 <flo-retina> I didn't get any window 09:55:31 <aleth> flo-retina: Yes 09:55:32 <flo-retina> nothing happened 09:55:43 <aleth> By "window" I meant the update history window 09:56:04 <flo-retina> should I mark that 1.5-blocking so that we are sure to remember to investigate? 09:56:15 <flo-retina> That doesn't seem tied to a specific release though; could have been there for years :-S 09:56:29 <aleth> Nothing visible happens when you click. Probably it tries to open a browser, that generally doesn't work without patching. 09:56:34 <aleth> Surprised about the crash though :-S 09:58:09 <flo-retina> aleth: do you have DOM Inspector installed? 09:58:13 <aleth> Yes 10:00:06 <flo-retina> I think I saw it causing the navigator.xul warning a few times 10:01:10 <flo-retina> no, I get this warning too, and I don't have DOMi installed on this profile 10:01:35 <flo-retina> so I guess the problem is: http://mxr.mozilla.org/mozilla-central/source/xpfe/appshell/src/nsXULWindow.cpp#1753 10:02:04 <flo-retina> interestingly, Tb sets that pref to messengercompose.xul :-D 10:03:14 <flo-retina> indeed, click the "details" link in Tb opens the compose window :-D 10:05:54 <flo-retina> ah, I was almost sure we would mid-air :-/ 10:07:29 <flo-retina> aleth: interesting detail: after clicking *once* the Details link and getting the warning in the console, I can't focus the update history dialog any more. It looks like there's an (invisible) modal dialog above it. 10:08:44 <flo-retina> closing the update history dialog with the Escape key works (doesn't crash) 10:15:16 <flo-retina> wow, 6 failed nightlies due to random disconnections :( http://buildbot.instantbird.org/waterfall 10:15:30 <aleth> Opening the compose window is very TB somehow :D 10:15:34 <flo-retina> my connection is much faster than my parents' but maybe it isn't really more reliable :( 10:16:21 <-- nhnt11 has quit (Input/output error) 10:16:32 --> clokep has joined #instantbird 10:16:32 * ChanServ sets mode +o clokep 10:16:33 --> nhnt11 has joined #instantbird 10:16:36 <aleth> Could one make the process more tolerant of brief disconnects? 10:16:40 <nhnt11> Wow 10:16:53 <nhnt11> I was following those STR to crash Ib 10:16:58 <nhnt11> and it crashed at the first step 10:17:05 <nhnt11> (opening the pref window) 10:17:06 <nhnt11> :( 10:17:49 <-- nhnt11 has quit (Quit: Instantbird 1.5a1pre -- http://www.instantbird.com) 10:18:01 --> nhnt11 has joined #instantbird 10:19:22 <-- clokep has quit (Quit: Instantbird 1.5a1pre -- http://www.instantbird.com) 10:19:27 --> clokep has joined #instantbird 10:19:27 * ChanServ sets mode +o clokep 10:19:48 <-- nhnt11 has quit (Quit: Instantbird 1.5a1pre -- http://www.instantbird.com) 10:20:36 --> nhnt11 has joined #instantbird 10:20:49 <-- Tonnes has quit (Ping timeout) 10:21:09 <clokep> Well that was fun. :) 10:21:57 <nhnt11> Funny that it seems to be properly quitting 10:22:10 * nhnt11 is intrigued 10:22:35 <flo-retina> aleth: by "the process" it seems you mean "buildbot" 10:22:49 --> Tonnes has joined #instantbird 10:22:57 <flo-retina> nhnt11, clokep: are you all trying to quit Instantbird by triple clicking? :-P 10:23:03 <nhnt11> yeah 10:23:08 <flo-retina> nhnt11: was the contacts window closed? 10:23:13 <clokep> flo-retina: Not trying. ;) 10:23:16 <nhnt11> yeah the first time. 10:23:27 <nhnt11> Wait 10:23:28 <aleth> It's clearly an easter egg ;) 10:23:28 <nhnt11> no it wasn't 10:23:31 <flo-retina> opening the pref window on mac nightlies is known to frequently crash if the contacts window was closed. 10:23:36 <nhnt11> I know 10:23:41 <flo-retina> And it can't be reproduced on debug builds; which makes it super painful :( 10:23:51 <-- nhnt11 has quit (Input/output error) 10:24:13 <flo-retina> seems like a crash :-S 10:24:30 --> nhnt11 has joined #instantbird 10:24:50 <flo-retina> clokep: there's some OTR related talk on the pidgin mailing list lately. They seems mostly serious about integrating it in a way that doesn't cause UI problems. 10:24:51 <nhnt11> I just opened preferences with the buddy list open. 10:24:53 <nhnt11> Boom. 10:25:16 <flo-retina> Maybe we should play the copycats on this? 10:25:20 <clokep> flo-retina: Yes I saw that. :) 10:25:26 <clokep> The code is still GPL IIRC. ;) 10:25:36 <flo-retina> really? 10:25:40 <flo-retina> I thought it was LGPL :-S 10:26:09 <clokep> Hm, maybe. 10:26:39 <flo-retina> " The Off-the-Record Messaging Library is licensed under version 2.1 of the GNU Lesser General Public License. The Off-the-Record Toolkit, the pidgin-otr plugin, and the OTR proxy are licensed under version 2 of the GNU General Public License. " 10:27:48 <nhnt11> flo-retina: http://log.bezut.info/instantbird/today#m139 Do you mean this is not seen in stable builds, or that it's something that has crept up since the last stable release? 10:28:14 <flo-retina> nhnt11: see next line. I mean it can't be reproduced in debug builds 10:28:29 <flo-retina> nhnt11: it's been our top crasher for years 10:28:46 <nhnt11> Years :O 10:28:58 <flo-retina> nhnt11: I/we even managed to get some attention on it and to get it fixed. Except after having a build with the fix included, we still crash as often :(. 10:29:20 --> jb has joined #instantbird 10:29:32 <-- jb has quit (Input/output error) 10:30:06 <nhnt11> :( 10:30:12 <clokep> flo-retina: Well sounds like their plan is to use lots of modal dialogues. ;) 10:30:28 <aleth> clokep: Really? 10:30:36 <aleth> That's not an UI problem? 10:30:38 <clokep> aleth: Are you really surprised? ;) 10:30:51 <flo-retina> clokep: no. It sounds like the plan is to make it "just work" 10:31:07 <flo-retina> clokep: although I would be surprised if a modal dialog didn't appear in the way at some point :) 10:31:38 <flo-retina> especially as the "not now" option is discussed :-D 10:31:41 <clokep> It looked to me like they're saying "Once you receive the OTR string, pop up some window asking if the user wants to use OTR" 10:31:56 <clokep> (And possibly after that, pop up a configuration window?) 10:32:22 <flo-retina> the other guy replied that there's nothing to configure before first using it though ;) 10:32:51 <flo-retina> aleth: not quite sure of what you are saying re bug 1316 10:32:55 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=1316 nor, --, ---, nobody, NEW, Input/output error on quit when closing Instantbird 10:32:55 <clokep> Can we use LGPL code? 10:33:08 <clokep> (In MPL) 10:33:50 <aleth> flo-retina: I'm not quite sure either, apart from that it seems that often on shutdown we don't actually send the QUIT message properly 10:33:53 <flo-retina> aleth: it looks to me like 1316 hasn't been reproduced in a while, so the fix that was checked in likely worked. And that fix is very likely responsible for the QUIT we are sending, which explained why I needed that follow up 10:34:04 <flo-retina> aleth: have you seen that recently? 10:34:16 <flo-retina> clokep: possibly 10:34:44 <aleth> flo-retina: I'm not sure, but there is certainly a lot of Input/output error around e.g. here http://log.bezut.info/instantbird/130826/ 10:35:05 <aleth> Ah wrong link, sorry 10:35:07 <flo-retina> clokep: would need to check with gerv. But I think you can use LGPL code without making your whole app LGPL. 10:35:54 <clokep> I see. 10:35:57 --> jb has joined #instantbird 10:37:01 <aleth> flo-retina: I was going to link to e.g. http://log.bezut.info/instantbird/130817/ but you may well be right as it seems (looking at a couple of random days) that mcon ley and nhn t11 are the only ones frequently quitting with that error 10:37:55 <clokep> http://www.mozilla.org/MPL/2.0/combining-mpl-and-gpl.html 10:39:06 <flo-retina> aleth: I don't think Mike uses JS-IRC. 10:39:24 <aleth> And nhnt 11 does often have a bad connection. 10:39:24 <clokep> mconley doesn't use IB / TB, he uses LimeChat IIRC. 10:39:39 <flo-retina> aleth: or recently said he crashed ;) 10:39:54 <nhnt11> aleth: My connection isn't bad at all on campus ;) 10:40:36 <aleth> So hopefully that bug has indeed gone :) 10:40:39 <flo-retina> aleth: http://log.bezut.info/instantbird/130817/#m154 is strange though. He didn't join immediately before 10:40:48 <flo-retina> aleth: yeah, I think we should resolve it as FIXED 10:41:07 * clokep agrees. 10:42:29 <instantbot> firstname.lastname@example.org set the Resolution field on bug 1316 to FIXED. 10:42:31 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=1316 nor, --, ---, nobody, RESO FIXED, Input/output error on quit when closing Instantbird 10:42:45 <flo-retina> thanks 10:43:03 <aleth> Shame we can't wean m conley off Limechat ;) Maybe he has heavily customized it... 10:43:11 <flo-retina> btw, restoring the on-hold status works so well that I barely noticed it today 10:43:26 <flo-retina> I just wondered how come I had only 2 tabs, and the 3rd appeared 10 or so seconds after 10:43:49 <flo-retina> aleth: whoever goes to the same summit location should try and convince him ;) 10:43:58 <flo-retina> clokep: maybe? :) 10:44:04 <flo-retina> s/:// 10:44:20 <clokep> flo-retina: I can try... 10:44:27 <clokep> Does this mean I should disable hide auto-joins? :P 10:44:35 <flo-retina> clokep: it's now pointless 10:44:44 <aleth> clokep: No, because you haven't got a new nightly yet? 10:44:45 <clokep> flo-retina: Well once there's a Windows nightly it's pointless. 10:45:00 <flo-retina> clokep: well, it's pointless on the second nightly with the feature ;) 10:45:09 <flo-retina> as you need the list of hidden convs to be recorded once 10:45:27 <-- jb has quit (Ping timeout) 10:45:29 <flo-retina> clokep: do you know why it takes so much time to auto-join all the IRC channels when reconnecting an account? 10:45:54 <flo-retina> I wonder if it's IRC-related, or the performance of our conversation UI (especially displaying the participants) 10:46:06 <flo-retina> I find it annoying that the channels don't appear all at once when reconnecting 10:46:22 <clokep> flo-retina: I'm unsure what you mean, do you mean that certain channels appear much later or that all IRC channels are sent later? 10:46:38 <flo-retina> clokep: some channels appear several seconds later 10:46:44 <clokep> IRC sends a TON of messages (probably a few hundred) when you log in, the JOIN message responses don't get handled until all that is done. 10:47:09 <aleth> flo-retina: Maybe what you'd really want is for the tabs to be opened immediately? 10:47:28 <aleth> (even if it takes a while for them to actually work? :-S) 10:47:28 <flo-retina> aleth: I think what I would really want is all the tabs of auto-joined convs to open at the same time 10:49:54 <flo-retina> I guess I should just throw the profiler at it 10:50:49 <aleth> flo-retina: I remember last time I "profiled" (don't have the real thing) the opening of #developers the participants handling in conversation.xml was surprisingly not the main factor 10:51:21 <flo-retina> aleth: it could be the time the server spends sending us the list of participants for all the channels 10:52:03 <clokep> flo-retina: The conversation is opened before that, IIRC. 10:56:56 <flo-retina> clokep: isn't it opened when receiving :flo-retina!Instantbir@moz-87C33FDA.kimsufi.com JOIN :#instantbird 10:56:56 <flo-retina> ? 10:58:20 <clokep> Yes. Which should be before the participants, IIRC. 10:58:40 <clokep> I think it'll be opened the first tim ehte conversation is referenced. 10:59:26 <aleth> You're both right, in that by the time initConvUI is called, usually most of the participants have been received from the server (unless you are on #ubuntu or something) 11:00:30 <clokep> It could possibly also depend on the order a server decides to send us messages. 11:00:58 <aleth> It's just that adding the conv and then the conv binding to the DOM etc takes time too. 11:00:58 <flo-retina> clokep: here are timestamps from my debug log http://pastebin.instantbird.com/305955 for the :flo-retina!Instantbir@moz-87C33FDA.kimsufi.com JOIN :<channel> lines 11:01:39 <aleth> flo-retina: Isn't it just that the server handles the JOINs we send in sequence? 11:01:49 <flo-retina> That's 6s between #instantbird and my last channel. 11:01:59 <clokep> Yes. 11:02:20 <aleth> Sounds reasonable for IRC. 11:02:29 <clokep> I don't think there's anything ew can do. 11:04:13 <flo-retina> do we request the list of participants, or is it sent our way automatically upon joining? 11:04:31 <clokep> Automatically. 11:04:33 <flo-retina> I wonder if there isn't some automatic throttling because the server is sending us too much data at once. 11:04:43 <clokep> I'd be surprised if there isn't. 11:05:19 <-- clokep has quit (Quit: Instantbird 1.5a1pre -- http://www.instantbird.com) 11:05:27 <flo-retina> as I join 7 channels in the first second, and then one per second 11:08:37 <flo-retina> I'm afraid the DEBUG line we moved is now causing plenty of debug log span for isupport messages :( 11:10:05 <aleth> That's not unexpected. 11:10:38 <aleth> There's a reason I was reluctant to move it ;) 11:11:49 <aleth> Maybe there's a way to improve that though? 11:13:49 <flo-retina> yeah, get rid of that call 11:13:58 <flo-retina> and DEBUG when we parse the message instead 11:14:09 <flo-retina> at http://lxr.instantbird.org/instantbird/source/chat/protocols/irc/irc.js#683 11:14:53 * flo-retina doesn't have any idea of how he the "channels aren't all joined at once" situation could be improved 11:15:24 <flo-retina> I guess putting useful channels at the beginning of the auto-join list would make it less visible 11:15:44 <flo-retina> but the Channel mode +ntr set by concrete.mozilla.org. that appears after we are done joining everything is still visible :-/. 11:16:10 <aleth> I don't see how we could improve that either. 11:16:55 <aleth> Other than trickery like changing the UI around when the convs are added to the list to "on request" rather than "on join". 11:17:24 <flo-retina> what does that mean? 11:17:35 <flo-retina> or is this about participants? 11:18:08 <flo-retina> anyway, I'll go grab some food and try to focus on "real" work this afternoon :) 11:18:10 <aleth> flo-retina: I mean in principle we could open a tab (or conv on hold item) before the conv is joined. 11:18:34 <aleth> That's not great because it would basically have to display a throbber or something... 11:25:17 <aleth> Hmm it might be better UX though as the conv binding etc could be added to the DOM while we negotiating with the server 11:25:28 <aleth> Especially combined with a tab opening animation or such... 11:28:02 <-- gerard-majax has quit (Ping timeout) 11:42:09 <flo-retina> aleth: wouldn't we want to display a "left" icon on the tab if we aren't actually in it yet? Wouldn't that make the left icon blink? :-/ 11:42:59 <aleth> flo-retina: There's a difference between "left" (which is a state) and "currently trying to join" (which is temporary) 11:44:18 <aleth> But yeah, it would require some careful modifications of the way we currently start conversations 11:44:32 <aleth> On the other hand nhnt11 was going to look into this anyway? :D 11:44:48 <aleth> (after gsoc) 11:52:01 <flo-retina> what's "this"? (the thing nhnt11 will look into) 11:52:11 <flo-retina> I don't think he'll fix IRC servers to suck less ;) 11:52:37 --> clokep_ has joined #instantbird 11:52:42 <aleth> No, his interest was in focusing newly joined conversations. 11:53:05 <aleth> Seems unrelated at first, but it depends on how you choose to improve it... 11:53:16 <nhnt11> flo-retina: I wanted to change the join chat api to make it so that a conversation tab is opened immediately, and the prplConversation is returned just like createConversation 11:53:48 <nhnt11> (It would display a system message saying "Joining #room" or something) 11:53:54 <aleth> nhnt11: And if you do that, you'll need a throbber or something on the tab to show it can't be used yet. 11:55:01 <nhnt11> Yeah.. 11:55:13 <nhnt11> definitely not trivial to implement 11:55:34 <nhnt11> not even sure if it's the best idea 11:55:38 <aleth> But flo wouldn't notice anymore that some of those convs on hold aren't actually all joined at the same time ;) 12:01:35 <flo-retina> aleth: I notice frequently the "left" icon on half my tabs, when my account is supposedly already reconnected 12:02:10 <flo-retina> nhnt11: to fix the join chat returning nothing issue, I was thinking that we could return a stub prplIConversation that would just automatically queue all the stuff we do with it 12:02:28 <flo-retina> actually, it's imWindows.jsm that would need to queue the focus/hide calls. 12:02:40 <aleth> flo-retina: Hmm, that's an interesting symptom of the same issue. Points at a third "connecting" throbber state to be the right way to go 12:02:58 <flo-retina> as long as we reserve an id immediately, and assign the same id to the conversation once it's finally created, that should work. 12:03:35 <nhnt11> Hmm 12:04:09 <nhnt11> That issue doesn't bother me nearly as much as the delay between pressing "Enter" and a tab showing up though 12:04:19 <aleth> nhnt11: You would show the tab immediately 12:04:31 <nhnt11> yeah 12:04:54 <nhnt11> And the delay doesn't bother me either, except for when you open an awesometab, join a channel, and the whole window closes and another window opens 12:05:00 <aleth> Which might actually help for snappiness, as I suggested earlier 12:05:10 <nhnt11> There are many solutions to this that we've already brainstormed though :) 12:05:22 <aleth> Yup :) 12:05:23 <flo-retina> nhnt11: what about keeping the join chat dialog (or the awesome tab) open with a throbber in it? 12:05:38 <nhnt11> like morphing the awesometab to the conversation tab.. but this leads us back again to having a conversation (stub) 12:05:41 <aleth> flo-retina: That's the most annoying solution I think 12:05:44 <nhnt11> flo-retina: I don't like that 12:05:57 <nhnt11> I'd prefer if the conversation tab opened and there was a throbber /there/ 12:05:58 <flo-retina> "you open an awesometab, join a channel, and the whole window closes and another window opens" wow, I never thought of that :( 12:05:59 <aleth> All the disadvantages of a throbber and none of the advantages ;) 12:06:26 <nhnt11> flo-retina: That's the reason I started thinking about this so much :) 12:06:37 <flo-retina> alright, open the conversation tab then 12:06:49 <flo-retina> nhnt11: keeping the join chat dialog open is useful only for the wrong password case 12:07:02 <nhnt11> Is that an important case though? 12:07:14 * nhnt11 doesn't know how we handle wrong passwords right now 12:07:18 <aleth> Really we would hope Join chat would be less important anyway post-awesometab 12:07:56 <flo-retina> nhnt11: I think we just display a system message in the conversation tab to insult the user 12:08:07 <nhnt11> Heh 12:08:09 <flo-retina> aleth: by less important you mean "removed"? ;) 12:08:18 <aleth> "Display a system message" is our version of modal dialogs ;) 12:08:23 <aleth> flo-retina: Yes please :) 12:08:37 <flo-retina> aleth: it's our version of non-modal monolog ;) 12:08:54 * nhnt11 should get into his zone where he writes more code than he has all week and churns out patches 12:09:05 <nhnt11> flo-retina: lol 12:09:07 <flo-retina> aleth: I think our version of "modal dialog" is rather a notification bar 12:09:36 <flo-retina> nhnt11: for me that's called "rainy week-end" 12:09:38 <aleth> flo-retina: I meant in the sense of "something we do too often as a shortcut because a better UX seems too much work" ;) 12:09:41 <clokep_> nhnt11: Go for it. :) I think there's lot sof things t odo. :-D 12:09:53 <flo-retina> I likely wrote more code during the week-end than during the whole week before it 12:10:37 * aleth hopes nhnt11 will get into the zone so he can try that add-on in a working state ;) 12:10:44 <nhnt11> Alright so I'm going to get some badly needed sleep soon and then code through the night 12:10:50 <nhnt11> aleth: It's still not working??? 12:11:06 <aleth> No, as discussed, it dies on .whatever 12:11:13 <nhnt11> Ah yeah 12:11:21 <nhnt11> I can get you a working version in a few mintues 12:11:34 <aleth> or maybe get some sleep first ;) 12:12:19 <nhnt11> aleth: Nah, I think I already fixed the addon 12:12:25 <nhnt11> It was a bit hackish but it'll do for you to test :) 12:12:31 * flo-retina wonders if auto-scroll is somehow broken for Bubbles after the mutation observer changes :-S. 12:12:48 <flo-retina> it's the second time today that I see a conversation not scrolled to the bottom automatically :( 12:15:52 <nhnt11> aleth: Could you try this please? http://puu.sh/4bgDZ.xpi 12:16:29 * nhnt11 should've added more error handling 12:17:02 <nhnt11> But that would slow it down possibly.. 12:17:17 <nhnt11> Is dump much faster than Cu.reportError? 12:17:22 <aleth> It's more important to do that later in the part you put in your patch... 12:17:34 <aleth> Oh, that kind of error handling 12:17:43 <aleth> dump should be faster, yes 12:17:54 <nhnt11> Yeah I meant having some feedback that it's working/failed 12:17:57 <nhnt11> Ok 12:18:07 <nhnt11> When I used Cu.reportError it took ~20-30 seconds 12:18:20 <nhnt11> That's 20 times as long, so if you have years' worth of logs.. 12:18:55 <aleth> Well, I've started it, not sure it's doing anything... we'll see. 12:19:00 <nhnt11> Ok :) 12:22:53 --> gerard-majax has joined #instantbird 12:23:08 <flo-retina> nhnt11: IIRC Cu.reportError is much slower if you have an Error Console (as stuff needs to be displayed). If you don't, there's just some data being stored somewhere in memory. 12:24:24 <aleth> nhnt11: It's still broken. 12:24:32 <aleth> This time it's failing on json log files of length 0 12:24:52 <aleth> It would be really nice if it actually produced error messages ;) 12:25:15 <nhnt11> yeah alright 12:25:26 <nhnt11> (Why would you have log files of length 0? :S) 12:25:50 <aleth> bug 1649 12:25:54 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=1649 maj, --, ---, nobody, NEW, Log files often get lost during shutdown 12:26:00 <nhnt11> oh 12:28:08 <aleth> Basically you have to be tolerant of all kinds of trouble when parsing logs, just in case. 12:28:22 <nhnt11> Yeah 12:28:39 <nhnt11> there could be completely unrelated json files there 12:28:53 <nhnt11> if the user put them there.. highly unlikely but there's a chance :P 12:29:34 <nhnt11> aleth: http://puu.sh/4bh4q.xpi 12:29:37 <nhnt11> That should be better.. 12:29:49 <flo-retina> bah, users... ;) 12:30:16 <nhnt11> flo-retina wants to keep his nifty little chat client to himself :P 12:31:12 <nhnt11> aleth: even if you see errors, most likely the thing is still working 12:31:21 <aleth> nhnt11: Now I'm seeing multiple Timestamp: 08/26/2013 02:30:08 PM Error: JSON.parse: unexpected end of data Line: 26 but it's continuing. 12:31:29 <nhnt11> yeah 12:31:36 <nhnt11> I made it report the error and move on 12:32:08 <nhnt11> Also it reports all the folders it's coming across so you'll know if it stopped :) 12:32:14 <nhnt11> (which you would've seen already..) 12:33:36 <aleth> I think it's still dying :( 12:34:05 <aleth> At least I don't have many logs for #labs ;) 12:34:22 <flo-retina> #labs? 12:34:25 * nhnt11 wonders what's happening this time 12:34:42 <aleth> flo-retina: Must have been mozilla labs 12:35:10 <flo-retina> nhnt11: I think I shared it with a few people (http://ftp.instantbird.com/instantbird/stats/ arguably some people aren't online in August though :-S)) 12:35:24 <nhnt11> :) 12:36:09 * nhnt11 wonders what happened in august 2011 that caused the huge surge in Ib users 12:36:24 <nhnt11> July * 12:36:31 <aleth> nhnt11: #labs.chat is a log folder containing only txt logs 12:37:08 <nhnt11> Oh, there's no JSON file at al 12:37:10 <nhnt11> all* 12:37:12 <aleth> nhnt11: flo did some actual marketing for 1.0 ;) 12:37:17 <clokep_> flo-retina aleth Can't nhnt11 use our log reader which already handles these weird issues with the JSON files? 12:37:23 <clokep_> Shouldn't he not be trying to read these files himself? 12:37:41 <aleth> clokep_: I don't really understand what exactly he's doing and why 12:37:54 <nhnt11> clokep_: Does the log reader go through all the files? I thought it opened files on demand 12:38:21 <aleth> nhnt11: The log reader goes through all the files for a particular user/chat 12:38:32 <clokep_> nhnt11: http://lxr.instantbird.org/instantbird/source/chat/components/public/imILogger.idl 12:38:38 <clokep_> You can get all logs for an account it looks like. 12:38:49 <clokep_> If it doesn't do what oyu want it to, you should expand it and use it's nice log reading methods, I'd imagine. 12:39:26 <flo-retina> clokep_: we could ask nhnt11 to fix the log reader, yeah... 12:39:29 <aleth> clokep_: It may be overkill in the sense that nhnt11 won't need complete conversations? 12:39:43 <nhnt11> aleth++ 12:40:28 <flo-retina> clokep_: the log reader in its current state is definitely inappropriate for something running in the background (even though we used it for gloda) because it's using synchronous disk I/O, and parses a whole file at once (freezing the UI for large files). 12:41:27 <flo-retina> (and one could even argue that the log reader in its current state isn't suitable for any purpose ;)) 12:42:13 --> nhnt12 has joined #instantbird 12:42:23 <nhnt12> So this is a new one.. 12:42:32 <nhnt12> I pressed command+shift+C to open the buddy list and poof 12:42:54 <-- nhnt11 has quit (NickServ (GHOST command used by nhnt12)) 12:42:58 * nhnt12 is now known as nhnt11 12:43:08 <flo-retina> ah, I only knew it for the about dialog and the preferences window 12:43:28 <clokep_> flo-retina: My point is that it has methods for handling our "bad files" though. :) So those could probably be C&Ped at the very least 12:43:54 <flo-retina> error handling can be copied, yes 12:45:50 --> dionisos has joined #instantbird 12:48:54 * clokep_ doesn't want nhnt11 to waste time rewriting code that someone already figured out. 12:49:04 <nhnt11> aleth: Last try for now (sorry and thanks for your patience testing these) http://puu.sh/4bhGv.xpi 12:49:38 <nhnt11> clokep_: For my purposes, I don't think it's that big a deal, if we encountered something we didn't expect, we move on to the next file :) 12:51:40 * flo-retina wonders how much work it would take to make log loading fully asynchronous. 12:54:35 <nhnt11> Hmm, I'm doing a build and I'm seeing activity in only 4 cores 12:55:07 <aleth> nhnt11: Looks like it's working so far :) 12:55:11 <nhnt11> yay 12:56:01 --> dew1 has joined #instantbird 12:56:11 <-- dew has quit (Ping timeout) 12:56:49 <aleth> nhnt11: Results look reasonable :) 12:56:53 <nhnt11> Yay results 12:57:13 <flo-retina> how long did it take? 12:57:22 <nhnt11> If they're reasonable, looks like my multipliers are fine 12:57:34 <aleth> A couple of minutes 12:57:47 <nhnt11> aleth: Was the error console open? 12:58:17 <aleth> nhnt11: Yes, but it wasn't scrolling /that/ rapidly, I don't think that made much difference 12:58:23 <nhnt11> ok :) 13:00:07 <nhnt11> Is there a mozconfig file in the objdir that's used when I do | make -C . |? 13:00:55 <nhnt11> Basically my question is, do I need to specify -j8 manually? :P 13:02:13 <flo-retina> nhnt11: yes, if you type make -C, you need the -j flag 13:02:21 * nhnt11 thinks he might as well have clobbered considering how long this is taking. 13:02:23 <nhnt11> flo-retina: thanks 13:02:30 <flo-retina> nhnt11: although usually when you make -C you do it to a specific folder that is small enough that it doesn't matter at all 13:02:39 <flo-retina> I don't bother with -j when I |make ib| 13:02:54 <nhnt11> right 13:03:10 <nhnt11> I should probably have just done |make -f client.mk build| 13:03:16 <nhnt11> Probably no point in make -C . 13:03:17 <flo-retina> yeah 13:03:23 <nhnt11> (where . is objdir) 13:03:39 <flo-retina> well, "-C ." is pointless in general :-P 13:04:07 * nhnt11 would really like to fix the |code| formatting 13:04:34 <nhnt11> Uh yeah |make| would suffice 13:04:36 * flo-retina would really like to not have to touch that code :-D 13:04:49 <nhnt11> don't really know why I've been doing make -C . 13:16:52 <instantbot> email@example.com denied review for attachment 2783 on bug 2126. 13:16:55 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=2126 nor, --, ---, nobody, NEW, Simplify system message collapsing 13:18:13 <flo-retina> aleth: "put an "eventToggle" attribute on the parent" you mean set a JS property, or a DOM attribute? 13:18:26 <flo-retina> I think a JS property could be a nice simplification 13:18:39 <aleth> Either would do, a JS property seems better :) 13:19:24 <nhnt11> My build is still building after ~25 minutes or more :( 13:19:26 <flo-retina> although it takes memory all the time (the property would stay there until the conversation tab is closed), for something that's needed only when a new system message is added 13:20:24 <flo-retina> aleth: or maybe testing parent.classList.contains("eventToggle") would be better? 13:20:39 <aleth> Right, the question is whether it's worth the speed gain when adding system messages 13:20:41 <flo-retina> it seems faster than the query selector, and doesn't have the memory waste aspect 13:20:58 <flo-retina> nhnt11: j1? 13:21:32 <nhnt11> flo-retina: It was using 4 cores so I guess it's j4 by default? 13:21:36 <flo-retina> ok 13:21:38 <nhnt11> Oh it finished :) 13:22:06 <flo-retina> aleth: I think to really gain speed in a significant way we need to avoid pointless reflows. 13:22:24 <aleth> flo-retina: That might be a good solution, though it probably needs a separate class ("collapsable" maybe) 13:22:36 <flo-retina> why? 13:22:43 <flo-retina> ah 13:23:16 <aleth> flo-retina: Do we have a lot of them? 13:23:32 <flo-retina> if we have to add a class, it's likely not better than a JS property 13:23:45 * flo-retina got confused by what the .querySelector was doing 13:23:51 <flo-retina> aleth: reflows? 13:23:55 <aleth> YEs 13:24:02 <flo-retina> I wouldn't be surprised if the timebubble code generated quite a bit of them 13:24:10 <flo-retina> although I haven't checked 13:24:11 <aleth> (pointless ones) 13:24:47 <flo-retina> the auto-scroll code likely forces a few of them too 13:26:39 <flo-retina> aleth: if (body.scrollHeight <= body.scrollTop + body.clientHeight + p.clientHeight + 10) in handleLastMessage likely causes a synchronous reflow 13:26:55 <flo-retina> but we do it only when we are done inserting messages, so that should be only once :) 13:27:14 <flo-retina> ok, it looks like I've already optimized this 13:27:17 <aleth> Right, iirc we added something to only do that at the end 13:32:37 * aleth will have to read up a bit on mutation observers to review bug 1750 properly 13:32:41 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=1750 min, --, ---, florian, NEW, Warning: Use of Mutation Events is deprecated. Use MutationObserver instead. 13:33:21 <flo-retina> https://developer.mozilla.org/en-US/docs/Web/API/MutationObserver 13:34:35 <-- nhnt11 has quit (Quit: Instantbird 1.5a1pre -- http://www.instantbird.com) 13:41:28 <clokep_> That's why I didn't review that bug. ;) 13:47:42 * clokep_ wonders if he should request aurora approval on https://bugzilla.mozilla.org/show_bug.cgi?id=898760 :-/ 13:48:05 <flo-retina> what's the first broken Tb? 13:48:18 <flo-retina> if the bug is on aurora, yes, we need to upload 13:48:20 <flo-retina> *uplift 13:48:58 <aleth> Isn't the whole new twitter API support stuff still to be merged? So Twitter eventually won't work in the next TB anyway? 13:48:59 * clokep_ needs to find the wiki page on that... 13:49:09 <clokep_> aleth: That was merged a long time ago. 13:49:24 <clokep_> aleth: That's in TB 24 IIRC. 13:49:26 <aleth> Oh, good. The last merge seems a long time ago ;) 13:49:59 <flo-retina> aleth: the new API is annoying anyway, with the limit of oauth token we can get per key :( 13:52:59 <clokep_> aleth: It's in TB 23: https://bugzilla.mozilla.org/show_bug.cgi?id=857049 13:53:25 <aleth> Oh, I see, that was done separately. 14:01:16 <clokep_> Yes. :) 14:01:23 <clokep_> The merge would be a mess right now though. 14:01:26 * clokep_ needs to port the Http.jsm changes back to IB. 14:06:40 <aleth> flo-retina: What I was looking for (and can't find documented) is when exactly a mutationobserver fires (i.e. how many changes are batched and how is that decided). 14:08:01 <aleth> I suppose the answer is "your code shouldn't care, this is up to gecko"? 14:12:02 * flo-retina is downloading ubuntu 14:13:29 * clokep_ wonders what flo is installing Ubuntu for. ;) 14:13:56 <flo-retina> I said downloading, not installing ;) 14:14:02 <flo-retina> maybe I'm just testing the download speed? :) 14:14:14 <flo-retina> more seriously though, I want to test https://bugzilla.mozilla.org/show_bug.cgi?id=462222 14:16:37 <clokep_> SocialAPI work? 14:16:42 <flo-retina> yes 14:16:52 <flo-retina> https://bugzilla.mozilla.org/show_bug.cgi?id=874566 14:43:08 <qheaden> Hello everyone 14:45:23 <clokep_> Hello. 14:51:04 <flo-retina> hello :) 14:52:43 <qheaden> flo-retina: Like I told clokep_ in an email, my working hours will have to shift to evening since my semester starts today. 14:53:25 <flo-retina> qheaden: clokep_ forwarded the information to us ;). But thanks for the heads up anyway :) 14:53:29 <clokep_> qheaden: I replied all. ;) 14:53:41 <clokep_> qheaden: Btw you should CC stuff like that to team@instantbird 14:53:48 <qheaden> Ahh okay. I didn't notice the reply all. 14:53:48 <instantbot> firstname.lastname@example.org granted review for attachment 2780 on bug 1750. 14:53:53 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=1750 min, --, ---, florian, NEW, Warning: Use of Mutation Events is deprecated. Use MutationObserver instead. 14:53:58 <qheaden> clokep_: Yeah, I need to remember that. 14:55:23 <qheaden> But of course, my ZNC will be idling, and I'll be checking in on logs. So feel free to ask me anything at any time. 14:57:14 <clokep_> qheaden: Right. :) 14:57:24 <clokep_> I'd like to have a discussion at some point today about what's left to do and such though. 14:58:00 <qheaden> Okay. 15:00:17 <flo-retina> ubuntu started. This laptop suddenly feels a lot more friendly 15:01:47 <qheaden> Speaking of Ubuntu, I switched back to developing on Linux. I know clokep_ will sigh that that. :P 15:02:16 <clokep_> qheaden: Doesn't bother me. :P 15:02:38 <aleth> OS battles are so last century :P 15:02:51 <qheaden> :) 15:04:01 --> mconley has joined #instantbird 15:04:06 <flo-retina> aleth: I'm not going to attempt to convince anybody to switch to ubuntu. I'm actually very happy that some people here are willing to ensure Windows so that I don't have to ;). 15:04:41 <qheaden> I just wish Ib played nicer with the Ubuntu's Unity interface. 15:05:04 <clokep_> mconley VERSION LimeChat for Mac 2.35 15:05:07 <flo-retina> you just volunteered to fix it :-P 15:05:07 <aleth> qheaden: Now we have a dev using IB with unity, maybe that will change? ;) 15:05:10 <clokep_> For anyone that was curious from earlier... 15:05:20 <qheaden> aleth: I'm not using Unity. ;) 15:05:29 <qheaden> I use Xubuntu (XFCE) 15:05:45 <aleth> qheaden: Then you don't really wish it hard enough ;) 15:05:50 <qheaden> :P 16:30:25 <-- flo-retina has quit (Quit: Instantbird 1.5a1pre -- http://www.instantbird.com) 16:39:02 <-- EionRobb has quit (Quit: Leaving.) 16:40:04 --> Mook_as has joined #instantbird 16:50:23 <-- Tonnes has quit (Connection reset by peer) 16:51:54 --> Tonnes has joined #instantbird 16:53:17 <-- chrisccoulson has quit (Ping timeout) 17:01:43 --> flo-retina has joined #instantbird 17:01:43 * ChanServ sets mode +qo flo-retina flo-retina 17:06:11 --> FireFly_TB has joined #instantbird 17:06:45 <-- FireFly_TB has quit (Quit: FireFly_TB) 17:07:54 --> FireFly_TB has joined #instantbird 17:10:23 --> qlum has joined #instantbird 17:18:22 <-- gerard-majax has quit (Ping timeout) 17:23:31 --> Even has joined #instantbird 17:23:31 * ChanServ sets mode +o Even 17:27:41 <-- flo-retina has quit (Ping timeout) 17:28:54 --> flo-retina has joined #instantbird 17:28:54 * ChanServ sets mode +qo flo-retina flo-retina 17:45:34 <-- aleth has quit (Quit: Ciao) 17:48:19 <-- instant-buildbot has quit (Connection reset by peer) 17:48:46 --> instant-buildbot has joined #instantbird 17:48:47 * ChanServ sets mode +v instant-buildbot 17:50:46 <-- FireFly_TB has quit (Ping timeout) 17:51:23 <flo-retina> aleth, clokep_: any idea? http://i2.minus.com/ijZw2cABYu80M.png :( 17:57:20 --> gerard-majax has joined #instantbird 18:04:18 <instantbot> email@example.com requested review from firstname.lastname@example.org rg for attachment 2785 on bug 2126. 18:04:20 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=2126 nor, --, ---, florian, NEW, Simplify system message collapsing 18:10:55 <instantbot> email@example.com set the Resolution field on bug 1750 to FIXED. 18:10:58 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=1750 min, --, 1.5, florian, RESO FIXED, Warning: Use of Mutation Events is deprecated. Use MutationObserver instead. 18:11:45 <instantbot> Check-in: http://hg.instantbird.org/instantbird/rev/b3986d237da1 - Florian Quèze - Bug 1750 - Warning: Use of Mutation Events is deprecated. Use MutationObserver instead - Instantbird UI part, r=aleth. 18:15:06 * mconley is now known as mconley|away 18:15:17 <flo-retina> clokep_: do you want to review https://bugzilla.instantbird.org/attachment.cgi?id=2784&action=diff again? 18:21:57 <instantbot> firstname.lastname@example.org granted review for attachment 2784 on bug 2117. 18:22:00 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=2117 nor, --, ---, qheaden, ASSI, /invite should print a system message to show it's done something 18:30:32 <instant-buildbot> build #451 of macosx-onCommit is complete: Success [build successful] Build details are at http://buildbot.instantbird.org/builders/macosx-onCommit/builds/451 18:33:45 <clokep_> flo-retina: No idea, I'd have to look over the code again. 18:33:54 <clokep_> flo-retina: Umm...I can review it again, but it's pretty trivial. :) 18:33:56 <flo-retina> the code isn't changed 18:34:10 <flo-retina> it's only the strings that we have been bikeshedding while you were away 18:34:18 * mconley|away is now known as mconley 18:34:59 <clokep_> Then no, I don't want to. :) 18:37:31 <-- flo-retina has quit (Ping timeout) 18:37:52 --> flo-retina has joined #instantbird 18:37:53 * ChanServ sets mode +qo flo-retina flo-retina 18:38:33 --> rosonline has joined #instantbird 19:12:56 <flo-retina> I've debugged a bit our crazy quit bug; it's interesting. 19:13:13 <flo-retina> Every click attempts to open a window, and that attempt fails, so the 'new window' is closed. 19:14:09 <flo-retina> nsAppStartup maintains a count of how many opened window we have. When that count reaches 0, the application exits. 19:14:32 <flo-retina> so to quit Instantbird from the "Details" links, you need to make as many clicks as you have opened windows at the time 19:14:54 <flo-retina> so the problem is that we are closing windows that have never been opened 19:15:18 * clokep_ thought that was a feature. ;) 19:17:33 <flo-retina> quitting if a user is pressing us too much for details? 19:19:12 <-- flo-retina has quit (Ping timeout) 19:19:18 <clokep_> We don't want them to know too much. 19:19:51 --> flo-retina has joined #instantbird 19:19:51 * ChanServ sets mode +qo flo-retina flo-retina 19:21:34 <qheaden> Hi again everyone. 19:29:48 <flo-retina> I filed https://bugzilla.mozilla.org/show_bug.cgi?id=909466 It looks like a bug of the new findbar (but I know we've had that bug with the nicklist for years ;)). 19:33:39 <qheaden> flo-retina: I'll make the changes to bug 2117 later this evening. 19:33:42 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=2117 nor, --, ---, qheaden, ASSI, /invite should print a system message to show it's done something 19:40:22 <flo-retina> qheaden: if it's just adding 2 words to a comment, I can do it for you ;) 19:40:54 <qheaden> flo-retina: Okay. Thanks. :) 20:22:51 --> EionRobb has joined #instantbird 20:47:49 <-- flo-retina has quit (Ping timeout) 20:53:02 --> flo-retina has joined #instantbird 20:53:02 * ChanServ sets mode +qo flo-retina flo-retina 21:14:21 --> wnayes has joined #instantbird 21:16:06 --> FireFly_TB has joined #instantbird 21:25:27 <-- clokep_ has quit (Quit: http://www.mibbit.com ajax IRC Client) 21:36:27 <-- FireFly_TB has quit (Quit: FireFly_TB) 22:08:02 <instantbot> New Instantbird (UI) bug 2128 filed by email@example.com. 22:08:04 <instantbot> firstname.lastname@example.org requested review from the wind for attachment 2787 on bug 2128. 22:08:06 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=2128 tri, --, ---, nobody, NEW, Chrome file doesn't exist: messages/papersheets/Variants/default.css 22:08:41 * flo-retina dislikes warnings 22:11:42 <-- qlum has quit (Connection reset by peer) 22:22:41 <instantbot> New Instantbird (UI) bug 2129 filed by email@example.com. 22:22:43 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=2129 nor, --, ---, nobody, NEW, Account displayed connected and with an error at the same time. 22:27:36 <instantbot> firstname.lastname@example.org requested review from the wind for attachment 2789 on bug 2129. 22:27:39 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=2129 nor, --, ---, florian, NEW, Account displayed connected and with an error at the same time. 22:41:22 <instantbot> New Core - XMPP bug 2130 filed by email@example.com. 22:41:23 <instantbot> firstname.lastname@example.org requested review from email@example.com for attachment 2790 on bug 2130. 22:41:24 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=2130 tri, --, ---, florian, ASSI, Warning: received presence stanza for unknown buddy <user's JID with another resource> 22:54:28 <instantbot> firstname.lastname@example.org requested review from email@example.com for attachment 2791 on bug 2127. 22:54:30 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=2127 cri, --, ---, florian, ASSI, Triple clicking the Details links of the Update history dialog quits Instantbird 23:00:14 <instantbot> firstname.lastname@example.org set the Resolution field on bug 2117 to FIXED. 23:00:16 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=2117 nor, --, 1.5, qheaden, RESO FIXED, /invite should print a system message to show it's done something 23:02:11 <instantbot> Check-in: http://hg.instantbird.org/instantbird/rev/cb85b50c0af3 - Quentin Headen - Bug 2117 - Yahoo: /invite should print a system message to show it's done something, r=clokep,fqueze. 23:02:11 --> jb has joined #instantbird 23:04:15 <-- jb has quit (Ping timeout) 23:05:35 <flo-retina> another 3 patches and I'll have as many patches waiting for review as I have waiting for my review :-D 23:06:15 <-- mconley has quit (Input/output error) 23:09:03 <-- dionisos has quit (Ping timeout) 23:18:09 <instant-buildbot> build #452 of macosx-onCommit is complete: Success [build successful] Build details are at http://buildbot.instantbird.org/builders/macosx-onCommit/builds/452 23:34:20 --> dionisos has joined #instantbird