[01:38] <lfaraone> dfarning: I just tested Surf on stock Ubuntu 10.10 and it crashed as I experienced...
[01:41]  * lfaraone is looking at Speak\
[02:48] <lfaraone> manusheel: is kandarp around?
[04:21] <lfaraone> xxkill
[04:26] <lfaraone> alsroot: you could get ubuntulo1 or meeting
[04:42] <alsroot> lfaraone: I'm already setting up supybot, looks like it is pretty powerful
[04:43] <alsroot> at least it has bunch of plugins (including meeting)
[11:12] <bernie> dfarning: this looks like a very good bug to get someone's teeth cut: http://bugs.sugarlabs.org/ticket/2163
[11:48] <bernie> manusheel:  this looks like a very good bug to get someone's teeth cut: http://bugs.sugarlabs.org/ticket/2163
[11:49] <manusheel> bernie: Yes, Bernie. Indeed :-)
[11:50] <manusheel> bernie: Any pointers that you would like to share - files we should look at, functions and variables?
[12:11] <bernie> manusheel: not sure... the bug might be somewhere in the FavouritesLayout class
[12:11] <bernie> manusheel: which is part of the "sugar" module
[12:11] <bernie> manusheel: I noticed that your developers are debugging right in Dextrose. this is ok for platform bugs, but it's not a comfortable work environment for sugar bugs.
[12:12] <bernie> manusheel: once they've reproduced the bug in Dextrose, it would save time if they could reproduce the same bug in jhbuild too, where they could take full advantage of a ful linux development environment and version control
[12:13] <bernie> manusheel: even if they fix the bug in the code in /usr/lib/something, then they'd have to redo the change in git to send a patch. so it's not really saving any time to debug directly on the XO
[12:13] <bernie> manusheel: again, I'm talking about sugar bugs, not driver/kernel bugs of course
[12:49] <alsroot> manusheel: ok, it's ready to use
[12:49] <manusheel> alsroot: Great.
[14:00] <manusheel> alsroot: Where can we find the logs?
[14:00] <manusheel> Of #sugar-newbies
[14:01] <alsroot> manusheel: still in progress, trying to figure out how to make them useful, ie searching
[14:02] <manusheel> alsroot: Sure.
[14:03] <manusheel> alsroot: Great.
[14:05] <lfaraone> alsroot: aka "site:foo.bar.baz query" in Google? :)
[14:07] <alsroot> lfaraone: if got it right it wont be reliable (we need to pay google otherwise), but since I'm so eager to web code by myself, it could be good for the first time :)
[14:07] <lfaraone> alsroot: pay google? huh?
[14:07] <alsroot> but /me is still looking for decent options
[14:08] <lfaraone> alsroot: http://www.google.com/search?q=site%3Airclogs.ubuntu.com+alsroot
[14:09] <lfaraone> *  http://www.google.com/search?q=site%3Airclogs.ubuntu.com+"alsroot"
[14:10] <alsroot> lfaraone: http://www.google.com/sitesearch/, see pricing, but anyway I'm tending to just enable google search
[14:11] <lfaraone> alsroot: you want http://www.google.com/cse/
[14:12] <alsroot> lfaraone: nope, I was just thinking that "site:" options won't be reliable, e.g., debina.org uses xapian for searching within mls/packages/etc
[14:34] <dfarning> neeraj, ping
[14:35] <neeraj> dfarning: pong
[14:36] <dfarning> neeraj, how close are you to release usr-meta?
[14:36] <lfaraone> dfarning: I don't think it was clear as to whether you wanted us to do two releases of USR, one now with existing pacakges and one later once everything's synced.
[14:37] <lfaraone> neeraj: by the way, "turtleart" was accepted from Debian NEW and probably is a good thing to have over in Ubuntu-land. :)
[14:37] <neeraj> lfaraone: great :)
[14:38] <neeraj> dfarning: We had an schedule meeting with luke today for discussing these stuff.
[14:38] <dfarning> lfaraone, neeraj it wasn't clear.... because I didn't say.  You guys have a better understand of the state to packageing than I do.
[14:38] <neeraj> Actually some packages are in sync state at present. So, if we want them in USR then we will have to wait to them to get released in upstream.
[14:39] <lfaraone> neeraj: you mean we'll have to wait for the syncs to get processed by an archive administrator.
[14:39] <dfarning> neeraj, what time is your meeting? I would like to listen.
[14:39] <lfaraone> neeraj: "upstream" means Debian or Sugar Labs, and they aren't required to take any action here.
[14:40] <lfaraone> dfarning: 10:30 I think was what I agreed upon with manusheel earlier.
[14:40] <alsroot> lfaraone: and looks like I found one :), nice demo app consists of 117 lines in python and provide exactly what I need, search string and pagination of results -- it's looking to xapian db
[14:40] <neeraj> lfaraone: sorry my bad. I meant in ubuntu :)
[14:41] <dfarning> lfaraone, thanks
[14:41] <neeraj> *brb
[14:41] <lfaraone> if manusheel 's around, I'm happy to hold it earlier.
[14:43] <dfarning> lfaraone, I am in no hurry.  I am going to do release of the ISO.  I will probobly be easiest to hard code the activites in 10.10 into the build script.
[14:47] <neeraj>  lfaraone we can start in 10 min
[14:48] <manusheel> lfaraone: I am around.
[14:48] <lfaraone> manusheel, neeraj, want to hold it at 10h instead? (12m from now)
[14:49] <manusheel> lfaraone: Sure.
[14:49] <neeraj> sure.
[15:02] <lfaraone> okay, let's get started.
[15:02] <dfarning> lfaraone, +1
[15:02] <lfaraone> #startmeeting
[15:02] <meeting> Meeting started at 10:02 UTC. The chair is lfaraone.
[15:02] <meeting> Commands Available: #TOPIC, #IDEA, #ACTION, #AGREED, #LINK
[15:03] <lfaraone> #TOPIC Agenda
[15:03] <lfaraone> manusheel, neeraj, do we have an agenda of what we want to discuss? I'd like to keep this short, so keeping to a list of topics will help us do that.
[15:05] <manusheel> lfaraone: Sure. One is arriving at a conclusion on whether to keep sugar-record, irc and e-toys as a dependency for this release, or not?
[15:06] <lfaraone> Okay. I've prepared a short topics list.
[15:06] <lfaraone> #LINK http://openetherpad.com/6b86BdsfpN
[15:06] <dfarning> 1. Package Status. 2. Browse/Surf Update 3. weekly objectives
[15:06] <lfaraone> #link http://openetherpad.com/6b86BdsfpN
[15:07] <lfaraone> hmmm. Not sure whether meetbot is getting those, but w/e.
[15:07] <manusheel> dfarning: Great.
[15:07] <lfaraone> #topic Keeping s-{record, irc, etoys}-a as deps for this release
[15:08] <lfaraone> If I recall, neeraj, you've got sync requests for all of these right now, correct?
[15:08] <neeraj> lfaraone: As discussed on mail, yes for irc,record and etoys
[15:08] <lfaraone> neeraj: right.
[15:08] <neeraj> We will add etoys as recommends only.
[15:09] <lfaraone> So etoys can't be a dependency for this release because it's in multiverse.
[15:09] <dfarning> lfaraone, I think dogi usually cuts and pastes the contents of etherpad to irc so it goes into the meeting recored.
[15:09] <lfaraone> neeraj: recently, "Recommends:" are installed by default by apt-get.
[15:09] <lfaraone> neeraj: so it'll have to drop to a "Suggets:".
[15:09] <lfaraone> dfarning: fair enough. Here's the current contents:
[15:09] <lfaraone>     * Status of sugar-*-activities
[15:09] <lfaraone>     * Keeping s-{record, irc, etoys}-a as deps for this release
[15:09] <lfaraone>     * Browse / Surf update
[15:09] <lfaraone>     * QA delegation
[15:09] <lfaraone>     * Updating usr-meta
[15:09] <lfaraone>     * Other weekly objectives (ACTIONs)
[15:10] <neeraj> lfaraone: Ok. I will add etoys as suggests then
[15:11] <lfaraone> manusheel: since irc and record will both be in universe, there's no reason not to add them, once they're in the archive.
[15:11] <lfaraone> manusheel: and since the SRU has already been ACK'd by a MOTU and the release team, it'll be processed some time before final release, and it'll be handled even if it's after Final Freeze because it was "in the queue" before-hand.
[15:11] <lfaraone> s/SRU/FFe/
[15:12] <lfaraone> the only thing now is whether we want to add the currently existing activities in the archive to usr-meta and do an upload now, or wait later and get them all in one swoop.
[15:12] <dfarning> lfaraone, +1 for moving etoys to suggests.  It become a hurdle for oems and resellers to ship multiverse.
[15:12] <neeraj> lfaraone: +1. thats my doubt.
[15:13] <lfaraone> the pros of doing it all now: we don't have to special-case in the build scripts, we enable `apt-get`tability for testers, and in case for some reason the syncs aren't processed or its too late to upload usr meta we at least have what we have now in the metapackage.
[15:14] <dfarning> neeraj, how much work is it to do a usr-meta?
[15:14] <lfaraone> the cons are: additonal work of preparing another upload (may be negligable and/or good practice for us), and having to bug an archive admin to process the upload. (rubber-stamp, essentially)
[15:14] <lfaraone> s/it all now / in two loads/g
[15:14] <neeraj> dfarning: no work at all. I have to just make change in control file
[15:15] <manusheel> lfaraone: Ok. But, how much time will it take for these activities to get accepted in MOTU?
[15:15] <dfarning> neeraj, then please do one today.  pros outweigh the cons.
[15:16] <lfaraone> manusheel: for the ones that neeraj filed a sync request for to be accepted in Universe? some time between now and 2010-10-10 :)
[15:17] <manusheel> lfaraone: We would not want meta package failures, and would also like to make sure QA is done once the iso is ready. Keep 1 week contigency time before the release (Sep. 3).
[15:17] <lfaraone> neeraj: we'll have to talk a little bit about that, by the way, since it's not just "add the deps directly to control", it's "add them to the metapackage in a special file", but you'd need to learn that eventually :)
[15:17] <lfaraone> manusheel: er, sep 3 is over a month from the final release. The *FinalFreeze*, on the other hand, is Sept 15
[15:18] <lfaraone> (2010-09-15)
[15:20] <manusheel> lfaraone: Sorry, I meant October 3. Not, Sep. 3
[15:20] <manusheel> 7 days before October 10.
[15:21] <lfaraone> well, at that point, we'll already be in FinalFreeze. *Ideally*, we'll have all of our changes in before the FinalF and have a month for testing, but it may not end up that way.
[15:22] <lfaraone> neeraj, dfarning, manusheel, so do we all think that it's a good idea for Neeraj to include all current shippable universe activities in usr-meta?
[15:22] <lfaraone> (and to do a different upload later)
[15:22] <dfarning> +1
[15:23] <manusheel> lfaraone: +1
[15:23] <neeraj> lfaraone: Ok. current shippable does not include irc,record and etoys. Right?
[15:24] <lfaraone> neeraj: if it's not in universe as of yet, it's not currently shippable :)
[15:24] <manusheel> lfaraone: Right.
[15:24] <lfaraone> neeraj: easy way to check is "rmadison PACKAGE_NAME" which will show you whether the package is in Ubuntu, which release, suite, and version.
[15:25] <lfaraone> #ACTION neeraj to look into adding all sugar-*-activity* packages currently in universe to usr-meta
[15:26] <lfaraone> #agreed do an upload of usr-meta with all activities available now, and one later if possible for record and irc when synced.
[15:26] <lfaraone> #topic Browse / Surf updates
[15:27] <lfaraone> manusheel: who's working on this on the SEETA side?
[15:27] <lfaraone> When I tried Surf earlier today in a clean Maverick VM it crashed on start. (using the .deb, not the .xo bundle)
[15:27] <lfaraone> the issue with browse as I understand it is still a dependency issue, which needs to be worked out with the mozillateam.
[15:28] <manusheel> lfaraone: Mukul and Ishan are working on it.
[15:28] <manusheel> lfaraone: Right.
[15:28] <lfaraone> manusheel: what's their progress on it?
[15:29] <dfarning> neeraj, I just added a list of what apt-get tries to install to http://openetherpad.com/6b86BdsfpN
[15:31] <lfaraone> dfarning: sugar-jukebox-activity-0.88?
[15:31] <manusheel> lfaraone: Hulahop library was broken in Ubuntu. So, I ask them to halt the process. They'll submit a fresh request r? by tomorrow.
[15:32] <lfaraone> manusheel: okay. the issue with hulahop is I don't really have any involvement in that arena, they'll need to talk to the people in #ubuntu-mozillateam.
[15:33] <dfarning> lfaraone, let me run it again.
[15:33] <lfaraone> dfarning: that package is not in debian or Ubuntu…
[15:33] <neeraj> dfarning: all the packages which u listed are not in Maverick
[15:33] <manusheel> lfaraone: Fine. I'll do that today.
[15:33] <manusheel> lfaraone: We did write to Mozilla guys. Got a reply too.
[15:33] <lfaraone> manusheel: the Mozilla *Ubuntu* team?
[15:34] <shachi__> dipankar,  hi
[15:34] <dfarning> lfaraone, neeraj ok I am deleting all of sugar and going to try a freash install and see what gets pulled in.
[15:35] <lfaraone> dfarning: I just did an apt-cache search and posted the results.
[15:35] <dfarning> neeraj, does lfaraone's list look right to you?
[15:36] <manusheel> lfaraone: We did forward the reply too. It seems the packages are in unstable state. Mike Hommey from Ubuntu looks after it.
[15:36] <lfaraone> minus read, of course.
[15:36] <lfaraone> manusheel: right.
[15:36] <lfaraone> manusheel: so any work on hulahop would need coordination with him and other members of the mozillateam.
[15:37] <manusheel> lfaraone: Right, absolutely.
[15:37] <lfaraone> manusheel: when I talked with micahg, he seemed to not feel comfortable shipping pyxpcom, which hulahop requires, because pyxpcom does not seem to be maintained upstream.
[15:37] <manusheel> lfaraone: Yes, we got the same vibes from Mike too. He said it is in unstable state.
[15:38] <lfaraone> okay. so we'll get an update from ishan and mukul re that tomorrow.
[15:39] <manusheel> lfaraone: Yes.
[15:40] <manusheel> lfaraone: How about Surf package?
[15:40] <manusheel> lfaraone: Does it have dependency issues?
[15:41] <lfaraone> manusheel: Surf has no dependency issues as far as I'm aware, but it segfaults whenever you click a link in my tests.
[15:43] <lfaraone> with regards to shipping sugar-firefox-activity, the intergration does not work at all. I was not able to use the Firefox theme that makes the text readable under the Sugar GTK theme.
[15:43] <lfaraone> Nor did the journal XPI work OOTB.
[15:44] <lfaraone> In order to ship Firefox.activity as Firefox.activity and not, say, "Abrowser.activity" (which is available in Ubuntu, btw, as "abrowser"), the Mozillateam folks still felt we'd need trademark approval.
[15:44] <manusheel> lfaraone: Right. Sugar Firefox is not be maintained well too.
[15:44] <lfaraone> dfarning: you said that's changed recently but docs have not been updated. Do you think it's worth following up with the Mozilla team  on that?
[15:44] <manusheel> lfaraone: It is at an experimental stage.
[15:45] <lfaraone> manusheel: yes, but on the other hand it's the only web browser that will *run* in sugar on Ubuntu :(
[15:45] <manusheel> lfaraone: We did write to Rabi. Didn't hear from him.
[15:45] <lfaraone> manusheel: Rabi?
[15:46] <dfarning> lfaraone, is it possiable to put a wrapper around the FF that ubuntu ships?
[15:46] <lfaraone> manusheel: C. Scott was the guy who wrote Firefox.activity
[15:46] <manusheel> lfaraone: Yes, C. Scott wrote it.
[15:46] <manusheel> lfaraone: But, it was OLE Nepal guys, who were using that activity.
[15:47] <lfaraone> dfarning: yes, that's what Firefox.activity does, albiet with some custom extensions and javascript settings. as of today, those settings are present but unapplied, so technically it's probably not violating trademark guidelines.
[15:47] <lfaraone> manusheel: ah, so they've made some updates to the activity?
[15:47] <manusheel> lfaraone: Also, maintaining it.
[15:48] <manusheel> lfaraone: I don't think so. If yes, didn't see it at the git.
[15:48] <manusheel> lfaraone: We did write to them too around 9-10 days back.
[15:48] <manusheel> lfaraone: No response on this thread.
[15:49] <dfarning> lfaraone, can you include the firefox as is?  will it at least browse the web?
[15:49] <lfaraone> dfarning: I think so.
[15:50] <lfaraone> meaning, it did in my tests.
[15:50] <dfarning> lfaraone, ok lets go with FF as is. this means dropping browse and surf until the next release.
[15:51] <lfaraone> dfarning: here's what it looks like in sugar-emulator: http://img714.imageshack.us/img714/7913/screenshotey.png
[15:52] <dfarning> lfaraone, neeraj can you guys package and upload the existing FF. lfaraone can you work with upstream about the treade mark issue if we get approval we will ad the setting and javascript if we have time.
[15:54] <neeraj> lfaraone: Did you find the source tarball of Mozilla Firefox activity?
[15:55] <dfarning> lfaraone, it is not perfect... but currently we are spending time on browse which is does not work and will be dropped and surf which does not work yet.  neither or which are moving us forward.
[15:56] <lfaraone> neeraj: yes. it's already in a git repository that I just haven't pushed up yet.
[15:58] <dfarning> manusheel, please drop all work on browse and browse dependencies.
[15:58] <dfarning> manusheel, please postpone all work on surf and surf until the next release.
[15:59] <lfaraone> fair enough.
[16:00] <lfaraone> #action manusheel to inform SEETA team members that work on surf/browse is tabled for this cycle
[16:00] <lfaraone> #topic QA delegation
[16:00] <lfaraone> We have testers, right? if not, we should look into a call-for-testing once we have a build that dfarning feels is ready for semi-public consumption.
[16:01] <manusheel> dfarning: Sure. Will do that now.
[16:01] <dfarning> lfaraone, the best group will be the NZ testers, satellit_ is also a great testing resource.
[16:02] <lfaraone> dfarning: cool. so we'll just ask them to take a look at it, say, the last week or so of Sept?
[16:02] <lfaraone> or tomorrow, once we get our packages in usr-meta. Beta was today IIRC
[16:03] <lfaraone> (for Ubuntu as a whole)
[16:03] <dfarning> lfaraone, I am doing am ISO build with the packages we talked about this morning.  Let's ask satellit_to take a initial look at it, if it works reasonably well we can release it as a beta.
[16:04] <lfaraone> okay, sounds good.
[16:04] <lfaraone> #action dfarning to review ISO build with activities for potential beta status.
[16:05] <lfaraone> #topic Updating usr-meta
[16:05] <lfaraone> We pretty much already discussed this, neeraj and I will work on that later today/tomorrow. Any other thoughts on this subject?
[16:06] <manusheel> dfarning: Once we are ready with beta iso, please let me know too. Will ask the team to do testing using the test plans.
[16:07] <lfaraone> #topic everything else
[16:07] <lfaraone> As we're into the second hour, does anybody have something we didn't talk about earlier that needs to be discussed?
[16:08] <dfarning> lfaraone, I think that is good.
[16:08] <lfaraone> cool.
[16:08] <lfaraone> #endmeeting
[16:08] <meeting> Meeting finished at 11:09.
[16:08] <meeting> Logs available at http://me.etin.gs/ubuntu-sugarteam/ubuntu-sugarteam.log.20100902_1002.html
[16:09] <manusheel> lfaraone: Thank you for your time today.
[16:09] <lfaraone> manusheel: my pleasure.
[16:10] <lfaraone> dfarning: is there a reason you added deps directly to the control file rather than modifying the ubuntu-sugar-remix-{$ARCH} files?
[16:11] <dfarning> lfaraone, no.  It was just a cut and paste from ubuntu-netbook-remix with a couple of personal hacks,
[16:14] <dfarning> manusheel, will kandarpk be around later.  I would like to have a brief status meeting with him and dipankar about the develpment/maintaince progress on USR.
[16:15] <dipankar> dfarning, good morning
[16:15] <dfarning> dipankar, god morning
[16:15] <dfarning> good
[16:15] <manusheel> dfarning: Sure, we can have a status meeting with Dipankar. Kandarp is traveling today and might be late. We can start the meeting now, if you wish.
[16:17] <dfarning> manusheel, let's do it when kandarpk is around... he should be the one chairing the meeting.
[16:18] <manusheel> dfarning: Ok. Sure.
[16:18]  * satellit_ glad to test when it is ready
[16:18]  * lfaraone → lunch.
[16:18] <dipankar> manusheel, dfarning : what is the meeting about?
[16:18] <dfarning> satellit_
[16:19] <manusheel> dipankar: Updates on the bugs and feature requests assigned as discussed in our in-house meeting recently.
[16:19] <dfarning> dipankar, I would like to get a handle on progress on https://edge.launchpad.net/ubuntu/+bugs?field.bug_supervisor=sugarteam
[16:21] <dfarning> dipankar, what is the status of https://bugs.edge.launchpad.net/ubuntu/+source/sugar-0.88/+bug/617813 ?
[16:21] <ubot2> Launchpad bug 617813 in sugar-0.88 (Ubuntu) "sugar freezes when register widget is clicked (affects: 1) (heat: 207)" [Critical,Confirmed]
[16:22] <dipankar> dfarning, on above bug, I contact bernie
[16:23] <dfarning> dipankar, what did you decide to do?
[16:23] <dipankar> dfarning, as you suggested, I tried putting yup a time lag check on the network connection setup
[16:23] <dipankar> for register
[16:23] <dipankar> but bernie told that we can't
[16:23] <dipankar> and he referred to a sugar-0.84 bug, similar to ours.
[16:24] <dfarning> what is the number of the sugar bug?
[16:24] <dipankar> dfarning, just a sec
[16:24] <manusheel> dfarning: http://bugs.sugarlabs.org/ticket/1152
[16:24] <dipankar> dfarning, bernie referred to this one: http://bugs.sugarlabs.org/ticket/1152
[16:24] <satellit_> [Sugar-devel] Findings for Register Bug LP #617813 also
[16:24] <ubot2> Launchpad bug 617813 in sugar-0.88 (Ubuntu) "sugar freezes when register widget is clicked (affects: 1) (heat: 207)" [Critical,Confirmed] https://launchpad.net/bugs/617813
[16:25] <dfarning> dipankar, what do you think you should do?
[16:26] <dipankar> dfarning, I was trying to go through it, having difficulty in thinking of a plan.
[16:26] <dipankar> dfarning, initiall I thought we can put check
[16:27] <dipankar> but when I tried, I came to realize we can't
[16:27] <dipankar> dfarning, is registration important? just asking
[16:27] <manusheel> dipankar: Absolutely.
[16:27] <manusheel> It is critical.
[16:27] <dipankar> ohk,
[16:28] <dfarning> dipankar, why can't you put in a check
[16:28] <dipankar> dfarning, to put a check I think we need to go to the library level
[16:29] <dipankar> dfarning, that would involve, send the data packet, wait for sometime
[16:29] <dipankar> and if the time is exceeding a set lag time, drop the process
[16:29] <dipankar> and raise an error
[16:29] <dipankar> just like e.g. ping
[16:30] <dipankar> we ping the site
[16:30] <dipankar> if the ttl is high
[16:30] <dipankar> drop the process
[16:30] <dfarning> dipankar, what do you mean by libary level?
[16:31] <dipankar> dfarning, I didn't get the exact word, sorry for using it. I meant manipulating the networking process itself
[16:31] <dipankar> dfarning, the code we have right now is: schoolserver.py
[16:31] <dipankar> dfarning, that directly call network functions
[16:32] <dipankar> dfarning, if some how we change those network functions, the way they work
[16:33] <dfarning> dipankar, what module contains this code?
[16:34] <dipankar> dfarning, let me check yup a bit
[16:36] <dipankar> dfarning, the function is ServerProxy()
[16:36] <dipankar> that creates a proxy object
[16:37] <dipankar> and later their functions are called
[16:37] <dipankar> dfarning, just a sec
[16:37] <dipankar> let me provide the link
[16:37] <dfarning> dipankar, where is serverproxy?
[16:37] <dipankar> http://docs.python.org/library/xmlrpclib.html
[16:38] <dipankar> dfarning, I think it is in : xmlrpclib
[16:43] <dfarning> dipankar, ok got it. ServerProxy() is making a remote functional and it is just waits until it receives a response form the server
[16:43] <manusheel> dipankar: Neat. What David is interested is in the Sugar api modules, which are gconf and logger in this case.
[16:44] <dipankar> dfarning, manusheel : that means we can manipulate the time lag allowed?
[16:44] <dipankar> dfarning, I tried putting a check on "ServerProxy()"
[16:45] <dipankar> ...
[16:45] <dipankar> try:
[16:45] <dipankar>     	server = ServerProxy(url)
[16:45] <dipankar>     except HTTPError:
[16:45] <dipankar>     	RegisterError(_('Cannot set Proxy'))
[16:45] <dipankar> ...
[16:45] <manusheel> dipankar: We should be doing that at the ServerProxy() function.
[16:45] <dipankar> manusheel, dfarning : The above code didn't work
[16:46] <dipankar> dfarning, manusheel : please try opening http://schoolserver:8080/ in web browser
[16:48] <manusheel> dipankar: Schoolserver is not a machine. It will not open.
[16:48] <dipankar> manusheel, ohk. that what schoolserver is? and why we are setting poxy server there?
[16:48] <dfarning> dipankar, ok understand the problem. I'll get back in a while.
[16:49] <dipankar> manusheel, sir, the only thing I couldn't understand so far is why set proxy ?
[16:49] <dipankar> :(
[16:50] <manusheel> dipankar: Right. Proxy is a method to access the network. Did you discuss this with alsroot?
[16:51] <dfarning> dipankar, see http://docs.python.org/library/xmlrpclib.html
[16:52] <dipankar> manusheel, complete went over the understanding :(
[16:54] <manusheel> dipankar: Ok, let us start the bottom up approach that we do whenever we are stuck.
[16:54] <dipankar> manusheel, sir, got it now
[16:54] <manusheel> dipankar: dfarning has provided an important pointer, which you looked at it earlier too. Can you open up http://docs.python.org/library/xmlrpclib.html ?
[16:55] <dipankar> manusheel, sir, if we try normal way (HTTP way), we will have trouble in registering, logging, etc to a jabber server
[16:56] <dipankar> manusheel, sir, once we setup the proxy then can easily (and safely) send the required data for register and login to any jabber server
[16:57] <dipankar> manusheel, sir, the data that is sent back is also in a structured manner
[16:57] <kandarpk> manusheel sir: hello
[16:57] <dipankar> so less clumsy in interpreting it
[16:58] <manusheel> dipankar: neat.
[16:58] <dipankar> manusheel, thank you sir.
[16:58] <manusheel> dipankar: This is how we should be thinking about it. Glad you solved the issue at your end.
[16:58] <manusheel> kandarpk: Hi Kandarp.
[16:59]  * dipankar is off for dinner. Be right back
[17:00] <dfarning> manusheel, see
[17:00] <dfarning> import xmlrpclib
[17:00] <dfarning> import httplib
[17:00] <dfarning> import socket
[17:00] <dfarning> class TimeoutHTTP(httplib.HTTP):
[17:00] <dfarning>    def __init__(self, host='', port=None, strict=None,
[17:00] <dfarning>                 timeout=socket._GLOBAL_DEFAULT_TIMEOUT):
[17:00] <dfarning>         if port == 0:
[17:00] <dfarning>             port = None
[17:01] <dfarning>         self._setup(self._connection_class(host, port, strict, timeout))
[17:01] <dfarning> class TimeoutTransport(xmlrpclib.Transport):
[17:01] <dfarning>     def __init__(self, timeout=socket._GLOBAL_DEFAULT_TIMEOUT, *args, **kwargs):
[17:01] <dfarning>         xmlrpclib.Transport.__init__(self, *args, **kwargs)
[17:01] <dfarning>         self.timeout = timeout
[17:01] <dfarning>     def make_connection(self, host):
[17:01] <dfarning>         host, extra_headers, x509 = self.get_host_info(host)
[17:01] <dfarning>         conn = TimeoutHTTP(host, timeout=self.timeout)
[17:01] <dfarning>         return conn
[17:01] <dfarning> class TimeoutServerProxy(xmlrpclib.ServerProxy):
[17:01] <dfarning>     def __init__(self, uri, timeout=socket._GLOBAL_DEFAULT_TIMEOUT,
[17:01] <dfarning>                  *args, **kwargs):
[17:01] <dfarning>         kwargs['transport'] = TimeoutTransport(timeout=timeout,
[17:01] <dfarning>                                     use_datetime=kwargs.get('use_datetime', 0))
[17:01] <dfarning>         xmlrpclib.ServerProxy.__init__(self, uri, *args, **kwargs)
[17:02] <dfarning> this will create a object called a TimeoutServerProxy with allows the user to set a timeout to a proxyserver conection.
[17:03] <manusheel> dfarning: Yes. This is where the condition has to be set.
[17:04] <manusheel> dfarning: We can have a member function, which is called by the object TimeoutServerProxy.
[17:05] <manusheel> This will allow the user to set up a timeout for the proxyserver connection.
[17:06] <neeraj> dfarning: bug 624592, I have attached the patch.
[17:06] <ubot2> Launchpad bug 624592 in ubuntu-sugar-remix-meta (Ubuntu) "request all packaged activities be installed by default on USR (affects: 1) (heat: 6)" [Critical,Confirmed] https://launchpad.net/bugs/624592
[17:08] <dfarning> manusheel, immediately before the async rpc function call to draw a message on the screen that registeration is in progress.  call gtk redraw to ensure the screen is rewrawn.  call TimeoutServerProxy
[17:08] <dfarning> neeraj, looks good.
[17:12] <manusheel> dfarning: Yes, thanks for the workflow. Yes, gtk redraw should be called to ensure screen is redrawn immediately after the registration is in progress.
[17:13] <manusheel> dfarning: This is the lag where Dipankar was getting stuck up. I think it should work out now.
[17:13] <manusheel> dfarning: Thanks for the pointer.
[17:40] <dfarning> manu the redraw needs to be done just before the call to .registration .  Once that rpc call is made, the client loses control until the server responds or the function times out.
[18:04] <dipankar> dfarning, around?
[18:04] <dfarning> dipankar, yes
[18:04] <dfarning> dipankar,  did the above make sense?
[18:05] <dipankar> dfarning, I was offline.
[18:05] <dipankar> dfarning, if I missed anything, could you please copy paste it? please.
 manusheel, see
[18:05] <dfarning>  import xmlrpclib
[18:05] <dfarning>  import httplib
[18:05] <dfarning>  import socket
[18:05] <dfarning>  class TimeoutHTTP(httplib.HTTP):
[18:05] <dfarning>     def __init__(self, host='', port=None, strict=None,
[18:05] <dfarning>                  timeout=socket._GLOBAL_DEFAULT_TIMEOUT):
[18:05] <dfarning>          if port == 0:
[18:06] <dfarning>              port = None
[18:06] <dfarning>          self._setup(self._connection_class(host, port, strict, timeout))
[18:06] <dfarning>  class TimeoutTransport(xmlrpclib.Transport):
[18:06] <dfarning>      def __init__(self, timeout=socket._GLOBAL_DEFAULT_TIMEOUT, *args, **kwargs):
[18:06] <dfarning>          xmlrpclib.Transport.__init__(self, *args, **kwargs)
[18:06] <dfarning>          self.timeout = timeout
[18:06] <dfarning>      def make_connection(self, host):
[18:06] <dfarning>          host, extra_headers, x509 = self.get_host_info(host)
[18:06] <dfarning>          conn = TimeoutHTTP(host, timeout=self.timeout)
[18:06] <dfarning>          return conn
[18:06] <dfarning>  class TimeoutServerProxy(xmlrpclib.ServerProxy):
[18:06] <dfarning>      def __init__(self, uri, timeout=socket._GLOBAL_DEFAULT_TIMEOUT,
[18:06] <dfarning>                   *args, **kwargs):
[18:06] <dfarning>          kwargs['transport'] = TimeoutTransport(timeout=timeout,
[18:06] <dfarning>                                      use_datetime=kwargs.get('use_datetime', 0))
[18:06] <dfarning>          xmlrpclib.ServerProxy.__init__(self, uri, *args, **kwargs)
[18:06] <dfarning>  this will create a object called a TimeoutServerProxy with allows the user to set a timeout to a proxyserver conection.
 dfarning: Yes. This is where the condition has to be set.
[18:06] <dfarning>  dfarning: We can have a member function, which is called by the object TimeoutServerProxy.
 This will allow the user to set up a timeout for the proxyserver connection.
 dfarning: bug 624592, I have attached the patch.
[18:06] <ubot2> Launchpad bug 624592 in ubuntu-sugar-remix-meta (Ubuntu) "request all packaged activities be installed by default on USR (affects: 1) (heat: 10)" [Critical,Confirmed] https://launchpad.net/bugs/624592
 Launchpad bug 624592 in ubuntu-sugar-remix-meta (Ubuntu) "request all packaged activities be installed by default on USR (affects: 1) (heat: 6)" [Critical,Confirmed] https://launchpad.net/bugs/624592
 manusheel, immediately before the async rpc function call to draw a message on the screen that registeration is in progress.  call gtk redraw to ensure the screen is rewrawn.  call TimeoutServerProxy
[18:06] <dfarning>  neeraj, looks good.
 dfarning: Yes, thanks for the workflow. Yes, gtk redraw should be called to ensure screen is redrawn immediately after the registration is in progress.
[18:06] <ubot2> dfarning: Bug 624592 on http://launchpad.net/bugs/624592 is private
[18:06] <dfarning>  dfarning: This is the lag where Dipankar was getting stuck up. I think it should work out now.
[18:07] <ubot2> Launchpad bug 624592 in ubuntu-sugar-remix-meta (Ubuntu) "request all packaged activities be installed by default on USR (affects: 1) (heat: 10)" [Critical,Confirmed]
[18:07] <dfarning>  dfarning: Thanks for the pointer.
 manu the redraw needs to be done just before the call to .registration .  Once that rpc call is made, the client loses control until the server responds or the function times out.
[18:07]  * dipankar is going through above
[18:10] <dipankar> dfarning, ok got it. but where is the source file? :)
[18:10] <ishan> dipankar: did you looked at that sir
[18:10] <dfarning> dipankar, you are hitting a cascade of failures.
[18:11] <dfarning> google serverproxy timeout  -- or something like that.  this is a pretty common issue.
[18:12] <dipankar> dfarning, ohk. just a minute
[18:13] <dfarning> dipankar, the async rpc function call is one problem.  The other is that there is garbage on the screen when that call is made.
[18:14] <dipankar> dfarning, yes. That I figured out: two problems
[18:14] <dipankar> 1. Time out
[18:14] <dipankar> 2. gtk redraw (to remove the gray rectangle that is left out after clicking)
[18:19] <ishan_> lfaraone, hi
[18:20] <dfarning> dipankar,  normally gtk widgets such as the window are redrawn in the background  as part of gtk_widget_queue (Or something similar) I think there is a comannd to redraw the queue in the main thread so that the screen is in a know good state prior to making the function call.
[18:21] <ishan_> lfaraone, wanted to discuss about moon package
[18:23] <dipankar> dfarning, ok
[18:27] <dfarning> dipankar, I think the following will trigger a redraw
[18:27] <dfarning>     event = gtk.gdk.Event(gtk.gdk.EXPOSE)
[18:27] <dfarning>     emit("expose-event", event)
[18:28] <dipankar> dfarning, ok. Now I am totally confused. :(
[18:28] <dipankar> dfarning, For the time out part: the code you provided in copy-paste, do I need to add it somewhere?
[18:29] <dipankar> or is it already implemented in python library?
[18:34] <dipankar> dfarning, ohk, now I seem to get it: http://stackoverflow.com/questions/372365/set-timeout-for-xmlrpclib-serverproxy
[18:34] <dipankar> the last solution to the problem, right?
[18:34] <dipankar> dfarning, that means I need to somehow implement what the solution is?
[18:35] <dfarning> dipankar, I would suggest adding the snippet above  (or something based on it) to schoolserver.py
[18:35] <dipankar> dfarning, won't that look odd?
[18:36] <dfarning> dipankar, why?
[18:36] <dipankar> dfarning, I mean, can I add new functions in the source files?
[18:36] <dipankar> of Sugar?
[18:38] <dfarning> dipankar, that is how to develop sugar.  by modifying the code.
[18:39] <dipankar> dfarning, all right then. just let me try a few changes in the code
[18:40] <dfarning> dipankar, +1 do your work in a git branch on a recently updated jhbuild.  Then you can easily make a patch for others to review.
[18:42] <dipankar> dfarning, ok, I was just carrying out tests on the code separately right now for checking purposes
[18:42] <dfarning> dipankar, that is why git is so cool.... if you make a mistake you can just reset.
[18:44] <dipankar> dfarning, since I am new to networking, how do I use the above classes? I mean, we are trying to replace the code - server = ServerProxy(url) right?
[18:44] <dipankar> * replace the code with a timeout controlled code?
[18:45] <dfarning> dipankar, in the code you will want to replace line 99 with server = TimeoutServerProxy(url)
[18:47] <dfarning> dipankar, then add the code for the TimeoutServerProxy to the file somewhere
[18:47] <dipankar> dfarning, yup.
[18:50] <dfarning> dipankar, all you are doing is creating a subclass of serverProxy called TimeoutServerProxy which add the ability to define a timeout factor.
[18:52] <dipankar> dfarning, sorry for my ignorance again: git repo of jhbuild. the one here right? http://wiki.sugarlabs.org/go/Development_Team/Jhbuild#Check_out_sugar-jhbuild
[18:53] <dfarning> dipankar, you were very close where you said that you thought that we needed to modify the library layer.... that is exactly what we are doing... By using inheritance we can tweak the underlaying libaries to meet our needs.
[18:53] <dfarning> dipankar, yes http://wiki.sugarlabs.org/go/Development_Team/Jhbuild#Check_out_sugar-jhbuild
[18:54] <dipankar> dfarning, glad I could think to that level. (If only i knew networking a bit :( )
[18:54] <dipankar> dfarning, I think I am getting the picture a bit clear.
[18:55] <dipankar> dfarning, rather than modifying the already existing library function, we are tweaking it a bit to suit our needs?
[19:03] <dfarning> dipankar, i guess technically we are adding a wrapper....  we want to do something to Proxyserver that the original authors did not include.... so we derive TimeoutProxyServer from ProxyServer.
[19:03] <dipankar> dfarning, yeah. I am through updating the jhbuild. Now changing the source
[19:07] <manusheel> dipankar: Hi Dipankar.
[19:07] <manusheel> Please check the logs.
[19:07] <manusheel> dipankar: dfarning provided some pointers on solving the bug.
[19:08] <dipankar> manusheel, sir, working on them, had the discussion what is to be done with dfarning :)
[19:10] <manusheel> dipankar: Ok. Did you get a hold on the situation?
[19:10] <dipankar> manusheel, yes sir. Now I am trying to implement the code
[19:11] <dipankar> * its a bit tough to track
[19:12] <manusheel> dipankar: Ok, great.
[19:17] <dfarning> dipankar, manusheel I am going to lunch.
[19:18] <dipankar> dfarning, enjoy your lunch :)
[19:21] <dipankar> manusheel, I have implemented the change : http://paste.ubuntu.com/487377/
[19:21] <dipankar> line 81
[19:21] <dipankar> manusheel, please review it.
[19:22] <dipankar> I want to complete it before I go ot sleep
[19:24] <manusheel> dipankar: Sure, Dipankar.
[19:24] <manusheel> Reviewing it.
[19:26] <dfarning> dipankar, It looks sane.  Have you tested it?
[19:27] <dipankar> dfarning, just running it now
[19:29] <dfarning> dipankar, if it works. we can go over how to submit it for review tomorrow.
[19:29] <dipankar> dfarning, manusheel : it crashed.
[19:29] <dipankar> http://paste.ubuntu.com/487381/
[19:29] <dipankar> sugar is not starting
[19:29] <dipankar> in jhbuild
[19:30] <dfarning> dipankar, the good news it that you patch did not cause the crash.
[19:30] <manusheel> dipankar: Yes, I got why it crashed.
[19:30] <dipankar> http://paste.ubuntu.com/487383/
[19:31] <dipankar> dfarning, I think it
[19:31] <dipankar> the report was clipped off in previous one :(
[19:31] <dipankar> sorry
[19:31] <manusheel> dipankar: Right.
[19:32] <dipankar> manusheel, dfarning : I think I got the problem
[19:32] <dfarning> dipankar, it is how the imports are handled
[19:32] <dipankar> dfarning, yup
[19:32] <dfarning> the code you added needs import xmlrpclib
[19:32] <dipankar> the xmlrpclib was not imported a whole
[19:35] <dipankar> : sugar started
[19:37] <dipankar> dfarning, manusheel : the strange thing is, there is no option for register in jhbuild
[19:37] <dipankar> !!
[19:38] <dfarning> dipankar, if you are already registed it will not show up again.
[19:38] <dfarning> I think you need to delete ~/.sugar
[19:39] <dipankar> ok
[19:40] <dipankar> dfarning, now register is showing up
[19:41] <dipankar> dfarning, but there is no response even after I click on it. I mean, there is no freezing.
[19:43] <dfarning> dipankar, you will need to simulate a error condition.
[19:43] <dipankar> ohk
[19:43] <manusheel> dipankar: Right, Dipankar. You'll need to simulate an error/exception condition.
[19:44] <dfarning> dipankar, what happens if you set the jabber server to www.google.com in the control panel?
[19:45] <dipankar> dfarning, it freezes
[19:46] <dipankar> dfarning, no, wait. It freezes for a while and then nothing happens
[19:46] <dipankar> everything is back to normal, the way it was
[19:47] <dfarning> dipankar, you are getting close.  did you set a timeout length in the code?
[19:47] <dfarning> dipankar, try setting that to 5 seconds
[19:50] <dipankar> dfarning, its WORKING!!
[19:51] <dipankar> dfarning, I can vary the freeze time!!
[19:52] <dfarning> dipankar, nice.  tomorrow let's turn it into a patch and submit it. then we an worry about the screen redraw and message later.
[19:53] <dipankar> dfarning, ohk, but what about the message to be displayed?
[19:53] <dipankar> dfarning, I think we should display a message
[19:53] <dfarning> dipankar, we can do that as a seperate patch.
[19:54] <dipankar> dfarning, sure
[19:54] <dipankar> :)
[19:54] <dipankar> manusheel, sir, around?
[19:54] <manusheel> dipankar: Good. Glad we arrived at a good conclusion on this issue. We'll take this up in the meeting tomorrow too.
[19:54] <manusheel> dipankar: Yes, I am around.
[19:54] <dipankar> manusheel, sure sir
[19:54] <dfarning> dipankar, it is easist for reviewers if a patch only does one specif thing.
[19:55] <dipankar> ohk
[19:55] <manusheel> dfarning: +1
[19:56] <manusheel> dfarning: Thank you for the pointers in helping us solve the bug. Very very helpful indeed.