[21:56] <kirkland>     a chown -R immediately before that, so the only part that was respecting
[21:56] <kirkland>     statoverride were the directory perms.
[21:56] <slangasek> then yes :)
[21:56] <kirkland> slangasek: does that look right?
[21:56] <kirkland> slangasek: cool
[21:57] <kirkland> mathiaz: anything else to include before i upload?
[21:57] <mathiaz> kirkland: a cookie?
[21:57] <kirkland> mathiaz: i just have that one /var/run/eucalyptus/net fix right now
[21:57] <kirkland> mathiaz: an easter egg?
[21:57] <mathiaz> kirkland: we can't talk about an easter egg in public though
[21:58] <kirkland> mathiaz: slangasek: uploaded eucalyptus_1.6~bzr854-0ubuntu12_source.changes
[21:58] <kirkland> slangasek: as soon as that builds, and a new iso comes along, we'll test it
[21:58] <mathiaz> kirkland: iz noh lunger a zicret ozzerwize
[21:59] <kirkland> mathiaz: you should make more liberal use of zzz's in your irc communications
[21:59] <kirkland> mathiaz: itz zwould zound zo much more like you
[21:59] <mathiaz> kirkland: oh!
[22:03] <slangasek> kirkland: more beta-critical stuff in the current upload?
[22:03] <kirkland> slangasek: yes, one beta critical bug fixed
[22:03] <slangasek> ok
[22:03] <kirkland> slangasek: one more still to go, though it's eluded us for most of the day
[22:03] <levi_> hello I am new
[22:04] <kirkland> slangasek: we're still trying to fix that one
[22:04] <kirkland> slangasek: in case we don't, or can't, we wanted to make sure the other one was fixed and on an ISO
[22:06] <kirkland> mathiaz: what evidence do we have that this might be an upstart bug?
[22:06] <mathiaz> kirkland: updating the bug description right now whith my investigation
[22:06] <kirkland> slangasek: could you poke us when the next iso is ready?
[22:07] <kirkland> mathiaz: shall i mark it as affecting upstart?
[22:07] <mathiaz> kirkland: probably yes
[22:07] <kirkland> mathiaz: done
[22:08] <Keevu77> Hello I am new
[22:09] <Keevu77> hello I am new
[22:09] <kirkland> Keevu77: you're probably looking for #ubuntu, then
[22:09] <Keevu77> ok sorry I just wnt to listen bye
[22:10] <sistpoty> being new is better than being old, I guess *g*
[22:17] <oxocoffee> I have a problem with multicast application. I was wondering some one can put some light on it.
[22:18] <oxocoffee> I have two sockets that bind to same port and ANY interface.
[22:18] <oxocoffee> than bot of them join different muticast groups
[22:18] <kirkland> mathiaz: have you gotten euca-describe-availability-zones verbose  to work yet?
[22:19] <mathiaz> kirkland: nope
[22:19] <mathiaz> kirkland: I've been debugging this registration failure for a day now
[22:20] <mathiaz> kirkland: and I think that the VERBOSE cmd line is actually --verbose
[22:21] <oxocoffee> when reading data I get double copy. Same data is beeing send over different multicast groups. But I read such data two times per socket instead of one copy per socket
[22:21] <oxocoffee> This works on Windows. I do not have any other system to test right now.
[22:21] <oxocoffee> Is there something different about linix that would explain this?
[22:21] <slangasek> oxocoffee: this is not a forum for application development questions
[22:22] <oxocoffee> I see. What would be the proper channel?
[22:22] <oxocoffee> I tried sockets but not one is there
[22:23] <slangasek> oxocoffee: I don't know offhand; a programming channel, I think
[22:24] <joaopinto> oxocoffee, it dependson the language you are using, #python, #c, etc
[22:26] <cr3> how can I query germinate somehow to determine if some packages are installed by default like apt-transport-https for example
[22:27] <cjwatson> in this case, 'apt-cache show apt-transport-https' will show "Task: standard" and the standard task is installed by default
[22:27] <cjwatson> you can also look at http://people.ubuntu.com/~ubuntu-archive/germinate-output/
[22:30] <doko_> ubuntu-archive: uploaded gcc-4.3/gcj-4.3. please consider accepting only one of them, so you have a free buildd on every arch.
[22:35] <cr3> cjwatson: ubuntu-moblin-remix doesn't seem to be on that page
[22:36] <cjwatson> cr3: it's indexed by the name of the seed collection branch, not by product name
[22:36] <cjwatson> I don't know if ubuntu-moblin-remix has seeds, or if so what they're called; if it does not have seeds then you cannot query germinate about them
[22:37] <cjwatson> if it does have seeds but we don't have pre-generated germinate output for them, then germinate is a package and you can run it by hand on things assuming you know the location of the seeds
[22:37] <cr3> cjwatson: I really need to learn more about these seeds
[22:37] <cjwatson> but in any case, the standard seed is common to all products, or should be
[22:38] <cjwatson> with some minor exceptions like minimal virtual machines
[22:40] <maxb> Is there anything I should do about bugs which I think are important for karmic but don't seem to be getting attention (I've already done "nominate for release") ?
[22:41] <kirkland> mathiaz: did you update that bug with your findings?
[22:42] <kirkland> mathiaz: i don't see anything yet
[22:42] <mathiaz> kirkland: not yet
[22:42] <kirkland> mathiaz: that sounds like fun
[22:43] <ScottK> maxb: Did you also milestone them for 9.10
[22:43] <maxb> am I allowed to? (I'm not ubuntu-dev)
[22:44] <cjwatson> doko_: at this point we're focused on getting the CDs built for beta release, and are deferring anything that doesn't directly contribute to that until after beta; is there a CD-relevant problem that gcc-4.3/gcj-4.3 is blocking?
[22:46] <doko_> cjwatson: no, both are universe (and unaffected by the freeze). just wanted to point out the build times of these packages
[22:49] <cjwatson> doko_: gcc-4.3 source is in main
[22:49] <cjwatson> FWIW
[22:53] <slangasek> maxb: in fact, nominating for release doesn't do anything useful (because everyone nominates everything for release).  If you have a regression, please use the regression-potential tag; otherwise, the next best (but not scalable) solution is to escalate to a developer directly
[22:57] <cjwatson> we can probably nuke linux-ports (though at this point I'm not inclined to do it before beta), and then blas is the only remaining build-dependency on gcc-4.3
[22:57] <cjwatson> in main
[22:57] <cjwatson> TheMuso: is linux-ports dead now, or are bits of it still kicking for some reason?
[22:58] <mdz> kirkland, any update on the registration stuff?
[23:01] <doko_> cjwatson: blas is alpha only, there's no dependency left. thanks for noticing ... I wasn't aware that it was still in main
[23:02] <doko_> could upload blas, would introduce a delta just for the gcc-4.3 dependency
[23:12] <mathiaz> kirkland: I've added a comment to bug 438602
[23:12] <mathiaz> kirkland: with a syslog
[23:19] <TheMuso> cjwatson: afaik linux-ports is dead, linux-ports-meta is still being used.
[23:20] <cjwatson> TheMuso: ok, will kill that after beta then, thanks
[23:21] <slangasek> kirkland: ETA 1h on the ubuntu-server respin
[23:33] <mathiaz> kirkland: so running: sudo start eucalyptus-cc-registration
[23:33] <mathiaz> kirkland: works as expected
[23:34] <mathiaz> kirkland: and it even starts eucalyptus-sc-registration!
[23:37] <mathiaz> kirkland: hm - sudo euca_conf --list-walruses doesn't return anything
[23:37] <mathiaz> kirkland: same for --list-clusters and --list-scs
[23:41] <mdz> mathiaz, did you try adding respawn to eucalyptus-cc-registration?
[23:41] <mdz> since eucalyptus-sc-registration seems to work, and it uses respawn
[23:42]  * mathiaz tries
[23:42] <mdz> mathiaz, can you confirm that SC registration seems to work? that would be very interesting as it's supposed to wait until CC registration is completed
[23:47] <mathiaz> mdz: adding respawn to  eucalyptus-cc-registration doesn't change anything: the job is still *not* started
[23:48] <mathiaz> mdz: sudo start eucalyptus-cc-registration will trigger both cc anc sc registration
[23:51] <mathiaz> nurmi: hi!
[23:51] <mathiaz> nurmi: Even after registration the cluster, sd and walrus aren't listed: http://paste.ubuntu.com/281717/
[23:51] <mdz> mathiaz, but walrus works?
[23:51] <mathiaz> mdz: well -  sudo euca_conf --list-walruses
[23:52] <mathiaz> mdz: doesn't return anything
[23:52] <mdz> that's even weirder, because the upstart config for walrus and cc are much more similar
[23:52] <directhex> walrus-related commands may be enough to interest me in ec2
[23:52] <mdz> if -cloud and -cc are running, -cc-registration should be run
[23:52] <mathiaz> mdz: ah - I see what you mean - yes walrus-registration works
[23:53] <mathiaz> mdz: the main difference between the cc and walrus jobs are that the former actually starts something, while the latter doesn't
[23:53] <mathiaz> mdz: it only waits for the service to be available
[23:53] <chrisccoulson> seb128 - i've agreed on a xklavier fix with svu now, which will stop that g-s-d crash
[23:53] <mdz> mathiaz, I just fixed a typo I noticed in the post-stop script.  shouldn't have any effect
[23:54] <mdz> mathiaz, you can have it exec a sleep or something if you think it might help
[23:54] <seb128> chrisccoulson, I was just reading the #c-c backlog ;-)
[23:54] <mathiaz> mdz: well - that's what I've tried - added script sleep 60 to the walrus job
[23:54] <chrisccoulson> i just realised i'm not in the room i expected ;)
[23:54] <chrisccoulson> i thought i was on #ubuntu-desktop
[23:54] <mathiaz> mdz: the result is that the walrus-registration job is *not* run
[23:55] <chrisccoulson> darned truncated tabs in empathy
[23:55] <mathiaz> mdz: that's why I suspect a timing issue with upstart
[23:55] <mdz> mathiaz, hmmmm
[23:56] <mathiaz> mdz: http://people.canonical.com/~mathiaz/syslog
[23:56] <mathiaz> mdz: ^^ that has two boots - the first one with a sleep 60 for the walrus job
[23:56] <mathiaz> mdz: and walrus-registration not run
[23:57] <mathiaz> mdz: the second doesn't have a script section in the walrus job and walrus-registration is run
[23:57] <mdz> mathiaz, just to check my sanity, can you try purging eucalyptus* and reinstalling it, and see if it registers everything then?
[23:57] <mdz> I need to go to sleep :-/
[23:57] <mathiaz> mdz: I'll give it a try
[23:57] <mathiaz> mdz: good night!


[15:57]  * stgraber waves
[15:58] <mdeslaur> o/
[15:58]  * slangasek waves
[15:59] <infinity> \o
[16:00] <mdeslaur> looks like kees is MIA
[16:00] <mdeslaur> let's get started
[16:00] <mdeslaur> #startmeeting
[16:00] <meetingology> Meeting started Tue May 23 16:00:05 2017 UTC.  The chair is mdeslaur. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:00] <meetingology> Available commands: action commands idea info link nick
[16:00] <mdeslaur> [topic] Action review
[16:00] <mdeslaur> infinity, slangasek: any progress on your items?
[16:00] <slangasek> none
[16:01] <slangasek> but my guilt levels are rising appropriately
[16:01] <infinity> As usual, I reminded myself of action items 5 minutes before the meeting.  I've pinged roaksoax to get the MaaS thing finally sorted.
[16:01] <mdeslaur> heh, ok
[16:01] <infinity> The other item, I did a ninja wiki edit of s/16.04.2/16.04.3/ :P
[16:01] <slangasek> heh
[16:01] <mdeslaur> infinity: perhaps just bump it to 16.04.5 right away? :)
[16:01] <infinity> Shush you.
[16:01] <mdeslaur> hehe
[16:01] <mdeslaur> #topic Mailing list archive
[16:02] <mdeslaur> doesn't look like there's anything new
[16:02] <mdeslaur> #topic Community bugs
[16:02] <mdeslaur> no open bugs
[16:02] <mdeslaur> #topic AOB
[16:02] <mdeslaur> anyone have anything to discuss?
[16:03] <slangasek> not I
[16:03] <stgraber> nothing here
[16:03] <infinity> Can we drop Go from the archive?
[16:03] <infinity> If not, then I have nothing to discuss. :P
[16:03] <mdeslaur> heh
[16:04] <mdeslaur> #topic Next chair
[16:04] <mdeslaur> slangasek with stgraber as backup
[16:04]  * slangasek nods
[16:04] <mdeslaur> #endmeeting
[16:04] <meetingology> Meeting ended Tue May 23 16:04:37 2017 UTC.
[16:04] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting-2/2017/ubuntu-meeting-2.2017-05-23-16.00.moin.txt
[16:04] <mdeslaur> thanks!
[16:04] <slangasek> kees: LATE
[16:04] <infinity> kees: You missed it.
[16:04] <kees> whoops, late
[16:04] <kees> haha
[16:04] <slangasek> :)
[16:04] <kees> saw the "thanks" and started laughing
[16:05] <slangasek> fwiw in 2 weeks time our team is sprinting, so I may be an unreliable meeting narrator
[16:05] <infinity> kees: You have AOB before we all /part?
[16:05] <kees> infinity: nope, all good.
[16:05] <mdeslaur> slangasek: I'll handle it if you don't show up
[16:06] <infinity> kees: You might be happy to know that we're finally PIE on all arches.
[16:06] <slangasek> mdeslaur: isn't stgraber supposed to? :)
[16:06] <kees> infinity: \o/ \o/
[16:06] <slangasek> infinity: has that flip been switched?
[16:06] <slangasek> (and I never got an answer to my email asking who would coordinate rebuilds)
[16:06] <infinity> slangasek: Yeah, doko got all keen and did it on Saturday, I followed up with a dpkg so the world didn't explode.
[16:06] <kees> https://outflux.net/ubuntu/hardening/ubuntu-hardening-5years.png
[16:06] <slangasek> ok
[16:07] <stgraber> slangasek: I'll be sprinting too :)
[16:07] <mdeslaur> slangasek: won't he be at the same sprint?
[16:07] <slangasek> mdeslaur: not the same one no
[16:07] <mdeslaur> oh, heh
[16:07] <stgraber> different sprints, same week
[16:07] <mdeslaur> well, we'll figure it out
[16:07] <stgraber> it was supposed to be the same sprint originally, but that didn't quite happen
[16:07] <kees> I changed how my PIE-analysis tool credited PIE packages, so there was quite a bump recently (if package is all .so's and no binaries, count as PIE. If a single ET_EXEC exists, no PIE for you)
[16:08] <slangasek> yeah, conference bookings went a bit sideways across the reorg
[16:08] <infinity> stgraber: Sadness.  I don't think we've hung out in a long while.
[16:08] <slangasek> kees: ahh ok
[16:08] <stgraber> infinity: been a while indeed, Seville was the last one I think
[16:08] <slangasek> I was going to say, I know I didn't have *that* many in my mass-rebuild
[16:09] <kees> slangasek: this is only amd64, so it'll likely not show much change
[16:09] <slangasek> kees: I mean the mass-rebuild we did right around 17.04 release
[16:09] <slangasek> which is probably the second smaller tick on your graph
[16:09] <kees> oh! that likely did help, yes.
[16:09] <slangasek> (main-only)
[16:10] <infinity> kees: Any urge to run stats for i386, so we can see where we need to apply abuse?
[16:10] <infinity> (or armhf or arm64, they should all be in the same state)
[16:10] <kees> I would suspect the two steps here are rebuild and script-adjust: https://outflux.net/ubuntu/hardening/ubuntu-hardening-month.png
[16:11] <kees> infinity: In theory I should be able to do i386, just requires some script-bashing
[16:12] <infinity> slangasek: I admit to being somewhat ignorant about the bits that need staged rebuilds.  Something to do with static linked bits?
[16:12] <slangasek> or some bash scripting?
[16:12] <kees> https://outflux.net/ubuntu/hardening/main/ had some unreliable data that I didn't try fixing
[16:12] <slangasek> infinity: yes
[16:12] <infinity> I don't think I was involved in that part for the previous arches.
[16:12] <kees> but the _current_ result is accurate, I think, for amd64 main
[16:12] <slangasek> infinity: basically, when we turned on PIE, we had a long tail of opaque build failures that required tracking down and rebuilding static libs in order to fix
[16:12] <kees> i.e. 96% PIE
[16:13] <slangasek> and nobody really took systematic notes on this
[16:13] <infinity> kees: Nice.  I, too, am 96% pie.
[16:13] <slangasek> hahaha
[16:13] <kees> haha
[16:14] <slangasek> so while we could just say "if it has a static lib that's not PIE, rebuild it", that's going to hit pretty much every library package in the archive instead of the ones that actually have static revdeps
[16:14] <infinity> slangasek: So, I guess maybe the next step, if we have no notes, is a rebuild test that we can unwind.
[16:15] <slangasek> infinity: I was going to suggest doing archive analysis for -dev build-deps that don't translate into runtime deps
[16:15] <slangasek> should we take this to #-devel? :)
[16:18] <infinity> slangasek: Sure.


[12:57] <BluesKaj> Hey all
[16:35] <bregma> for those who have not heard, it's ''Precise Pangolin''
[16:36] <pangolin> I heard
[16:41] <genii-around> Those things look weird
[17:20] <willwh> hi guys - anyone alive?
[17:20] <willwh> I have a quick question - I have a java application that starts via a shell script
[17:20]  * genii-around waves
[17:21] <willwh> I've run the startup.sh quite a few times
[17:21] <willwh> now when I try and run it, I'm getting this int he console: .: 2: 3: Too many open files
[17:21] <willwh> the scrip itself seems to set ulimit to 20000
[17:21] <willwh> any ideas on how I find out wtf is going on? :]
[17:21] <willwh> I restarted the box....
[17:21] <genii-around> Maybe it's not closing whatever files it opens
[17:21] <willwh> still same thing
[17:21] <genii-around> Hm
[17:22] <willwh> yeah it's real yodd
[17:22] <willwh> I don't know how I even go about debugging
[17:23] <willwh> any ideas genii-around ? :)
[17:24] <genii-around> None that come immediately to mind. Looks like it stores someplace the files that are open. Maybe ask in java channel?
[17:28] <willwh> ye
[17:38] <genii-around> willwh: Maybe set in /etc/sysctl.conf the variable fs.file-max=20000   or so


[06:52] <dholbach> good morning
[07:02] <dholbach> hey mitya57 - how are you doing?
[07:03] <dholbach> mitya57, can we do an upload of ubuntu-packaging-guide?
[07:49] <Rhonda> Is it to late to get ejabberd and its dependencies synced into unicorn?
[07:49] <Rhonda> There are new packages along that path. :/
[07:50] <Rhonda> A fair amount of erlang packages that is.
[08:14] <debfx> sounds a lot like it's too late
[08:37] <Rhonda> thought so, but asking is always possible :)
[09:11] <mitya57> dholbach: I'm good, thanks, and you? How is the developer.u.c migration to Sphinx going? :)
[09:11] <dholbach> mitya57, I'm working on a prototype - it'd be one possible options
[09:11] <dholbach> very slowly working on it :)
[09:12] <mitya57> I think the right person to ask about upload is Andrew
[09:12] <dholbach> ah ok
[09:12] <dholbach> will do
[09:12] <mitya57> Though, if he has no time and is ok with me doing it, I'll do it.
[09:13] <dholbach> I'll send a mail to the two of you
[09:13] <mitya57> Thanks!
[09:13] <mitya57> Do we have any new languages btw?
[09:14] <dholbach> no, I don't think so
[09:15] <mitya57> Right, the script agrees with you


[05:07] <Osirus126> Hello everyone. I hope all is well for everyone in the channel
[21:24] <Osirus126> hey guys
[21:24] <Osirus126> how is everyone?
[21:25] <Osirus126> just joined and would like to say hello


[00:00] <kdub> could anyone take a look over? https://code.launchpad.net/~kdub/platform-api/mir-deb-bump-0.1.3/+merge/200430
[00:00] <kdub> should be pretty simple, just bumping ABI
[03:05] <Akiva-Mobile> So I am thinking of contributing a feature to unity, patch and everything, about an idea that I just thought of. I'd like to pass the idea around here first
[03:05] <Akiva-Mobile> Its actually pretty mundane and simple, and has to do with moving windows with the mouse
[03:08] <Akiva-Mobile> When an application is full screen, and you go to the top screen bar, on the white space where no menu actions are currently situated, and then HoldLeftClick, you can move the window around
[03:09] <Akiva-Mobile> I basically want to extend this function to when windows are not full screen
[03:10] <Akiva-Mobile> One of the reasons why this is, is that I often find while using spaces, that my top menu bar is stuck on another virtual desktop
[03:11] <Akiva-Mobile> and I thus have to switch workspaces, or press alt+click the window to drag down.
[03:26] <RAOF> Hm. I was wondering where that was going; that's an actual use-case :)
[03:26] <RAOF> On the other hand, might this not be better solved by ensuring that the top bar is always visible?
[05:51] <Akiva-Mobile> RAOF: http://discourse.ubuntu.com/t/unity-five-suggestions-for-global-menu-bar-whitespace/1392 << sorry, library closed, and now im at the coffee shop :P. Anyways, I extended my suggestion to five
[05:52] <Akiva-Mobile> RAOF: The top bar being always visible... how would the logic work with vertical spaces?
[05:52] <RAOF> Akiva-Mobile: You'd just move the window down when you switched workspaces.
[05:53] <Akiva-Mobile> RAOF: wouldnt that be annoying if you were trying to escape that application, and it just happened to slightly be leaking into the next workspace?
[05:54] <Akiva-Mobile> RAOF: Gnome 3 doesnt have this issue though, does it...?
[05:55] <RAOF> Akiva-Mobile: Yeah, that would be awkward I guess. GNOME 3 gets around this by not having workspaces in a coherent space.
[05:55] <Akiva-Mobile> RAOF: If Gnome3 had HUD, I'd definitely consider using it.
[06:02] <Akiva-Mobile> RAOF: Sorry again :P
[06:03] <Akiva-Mobile> RAOF: I think my idea is reasonable, and it would be neat trying to get a patch accepted by the ubuntu project. Maybe then someone will hire me as a programmer once I have that on my mantle :)
[06:03] <RAOF> :)
[06:03] <RAOF> I'd give it a go.
[06:04] <Akiva-Mobile> RAOF: Any suggestion what file to start looking into? Save myself some time~
[06:04] <RAOF> Sorry, no.
[06:05] <Akiva-Mobile> RAOF: I'll expose my ignorance here, but will I have to do this on mir?
[06:05] <Akiva-Mobile> or will the code be transferable?
[06:05] <RAOF> No; the Unity 8 codebase is entirely distinct.
[06:05] <RAOF> There's not currently any window management in Unity 8 anyway :)
[06:05] <Akiva-Mobile> RAOF: For mir, how much needs to be rewritten?
[06:06] <RAOF> We're rewriting everything; using Qt5 rather than compiz, etc.
[09:07] <Mirv> Saviq: FYI test failing https://bugs.launchpad.net/unity-scopes-shell/+bug/1267026
[09:07] <Saviq> mhr3, ↑
[09:08] <Saviq> Mirv, the unity-api issue is tricky :/ in theory we've identified the commit where it got better, but that one commit wasn't enough
[09:08] <Saviq> Mirv, it's working fine on the stable branch, after https://bugreports.qt-project.org/browse/QTBUG-35721 has been fixed
[09:09] <tsdgeos> and the tabbar was merged, let's see all the complains :D
[09:09] <Mirv> Saviq: is stable = upcoming 5.2.1? please don't say 5.3 :)
[09:09] <tsdgeos> yes
[09:09] <Mirv> ok, yes I'd be planning to get qtbase and qtdeclarative snapshots (or maybe just qtdeclarative for starters)
[09:10] <tsdgeos> "Target for Qt 5.2.1 release is at the end of January \ early February."
[09:10] <tsdgeos> http://lists.qt-project.org/pipermail/releasing/2013-December/001557.html
[09:12] <Mirv> larsu: if you could check (or delegate) gsettings-qt bug #1259145 at some point, it would be nice. maybe some tests shouldn't be run under xvfb? SDK team might have encountered something similar earlier, also
[09:12] <tsdgeos> Mirv: as said i fixed that
[09:12] <tsdgeos> it's nothing about xvfb
[09:12] <tsdgeos> it's just that the test was failing
[09:12] <larsu> Mirv: I already did, it's fixed in qt
[09:13] <larsu> tsdgeos: thanks again for that :)
[09:13] <tsdgeos> Mirv: i.e. the x error we get we were getting before (afaics)
[09:13] <Mirv> tsdgeos: larsu: oh right I might be confused, there was the another bug report that was filed during RC1. the latest gsettings-qt build from 2012-12-19 failed still: https://launchpadlibrarian.net/160186213/buildlog_ubuntu-trusty-amd64.gsettings-qt_1%3A0.0%2B13.10.20130902.1-0~42.1~ubuntu14.04.1_FAILEDTOBUILD.txt.gz
[09:13] <tsdgeos> Mirv: a recent enough snapshot of qtdeclarative stable branch should fix it
[09:14] <Mirv> tsdgeos: aha, aha, so that's also one of those that needs newer qtdeclarative?
[09:14] <tsdgeos> yes
[09:14] <tsdgeos> they totally from QQmlPropertyMap in 5.2.0
[09:14] <tsdgeos> it's far from salvageable
[09:14] <Mirv> right, in that case that's the first priority now (well aside from my ir testing)
[09:14] <tsdgeos> you need 5.2.1
[09:14] <Mirv> Mir
[09:15] <Mirv> thanks. I'll skip qtbase updating for now until there's a known need for a snapshot.
[09:16] <Saviq> Mirv, so - we're targeting 5.2.1 then?
[09:17] <Mirv> Saviq: we're targeting anything that can get all FTBFS:s fixed and image results as good as with 5.0.x. preferably it would have been 5.2.0 already.
[09:17] <Saviq> Mirv, i.e. if stuff works with 5.2.1 but not 5.2.0, are we sad?
[09:17] <Saviq> Mirv, yeah, that isn't working apparently :/
[09:17] <Mirv> Saviq: I think it doesn't matter what we use, as long as we can use it without regressions and the 100 source packages all compile neatly against it and everything is full of flowers :)
[09:18] <mhr3> :/ seen that bug already
[09:18] <mhr3> it's some kind of race
[09:18] <Mirv> I hope the qtdeclarative will resolve some of the build failures at https://launchpad.net/~canonical-qt5-edgers/+archive/qt5-beta2/+packages (gsettings-qt is one pre-requirement to move forward)
[09:18] <Saviq> Mirv, so you're snapshotting qtdeclarative from the stable branch (5.2.1) now? awesome.
[09:20] <Saviq> elopio_, crap, sorry for yanking the bottom bar out from under your feet... :/
[09:20] <Saviq> elopio_, didn't know you were working on that emulator
[09:20] <Saviq> elopio_, hopefully this new emulator will be able to use one from the sdk? is there an emulator for tabs in sdk already?
[09:20] <Mirv> Saviq: yes
[09:21] <Saviq> elopio_, ah, already done! ;)
[09:21] <mhr3> Saviq, mind if we start the preview meeting 15minutes later?
[09:22] <Saviq> mhr3, sure
[09:22] <Saviq> mhr3, I don't
[09:22] <mhr3> :) moving
[09:24] <mzanetti> Saviq: hey, did you come to a conclusion regarding the qml in cmake?
[09:25] <Saviq> mzanetti, I don't think I did ;)
[09:25] <Saviq> mzanetti, /me looks at the branch
[09:25] <mzanetti> Saviq: want me to summarize the possible options again?
[09:26] <Saviq> mzanetti, no, I think the only last beef I had was moving it into src/ or something
[09:26] <mhr3> Mirv, you can try to just rebuild, it might just work
[09:27] <mzanetti> ah ok. yeah, gerry had the same opinion. I still think qml sources are sources too but I don't really mind as long as I don't have to open 2 project files all the time
[09:28] <Mirv> mhr3: well we don't allow flaky tests anyway, so it wouldn't change much even if it would work. but it seems to have failed every time on armhf: https://launchpad.net/~ubuntu-unity/+archive/daily-build/+builds?build_text=unity-scopes-shell&build_state=all
[09:30] <Saviq> mzanetti, I think file(GLOB_RECURSE ../qml/*.qml ../qml/*.js) will do what you need
[09:30] <mhr3> Mirv, seeing when it started happening actually helps, thx
[09:31] <mzanetti> Saviq: ok. I'll change it
[09:31] <Saviq> mzanetti, so leave qml/ be, and just do the GLOB again in src/
[09:31] <mzanetti> Saviq: yep
[09:33] <Saviq> mzanetti, and drop .qmlproject then, I think?
[09:33] <mzanetti> yep
[09:34] <Saviq> mzanetti, http://paste.ubuntu.com/6713876/
[09:34] <Saviq> mzanetti, that works for me
[09:34] <Saviq> mzanetti, might want to add .png / .svg etc.
[09:35] <Saviq> mzanetti, stuff that qmlproject itself does :/
[09:35] <Mirv> mhr3: ok, great, indeed there is a certain point
[09:36] <mzanetti> Saviq: on a first thought I'd say that's not needed, given that we can't really do much with them in the IDE anyways. But I'm not opposed to it
[09:37] <Saviq> mzanetti, you can view them at least
[09:37] <Saviq> mzanetti, and see a list of them in the project explorer
[09:37] <Saviq> mzanetti, which is useful
[09:37] <mzanetti> ok
[09:38] <Saviq> mzanetti, .png, .svg, .sci
[09:38] <Saviq> mzanetti, and see if we have any other
[09:38] <mzanetti> ack
[09:47] <Saviq> mzanetti, http://paste.ubuntu.com/6713935/ is probably enough... after all we want all files from under qml/ to show up
[09:48] <mzanetti> Saviq: true... any idea how to make the importPaths statement work?
[09:48] <mzanetti> I tried this, but doesn't seem to work: add_definitions(-DQML_IMPORT_PATH=builddir/plugins:builddir/modules:builddir/tests/plugins:builddir/tests/utils/modules)
[09:49] <Saviq> mzanetti, do we actually need that?
[09:49] <mzanetti> its not totally essential. but for some plugins we'd get code completion
[09:49] <Saviq> mzanetti, that's *if* QtCreator would actually honor that
[09:49] <mzanetti> :D
[09:50] <Saviq> mzanetti, which I doubt it would
[09:50] <mzanetti> for qmake based projects apparently setting QML_IMPORT_PATH should work
[09:52] <Mirv> Saviq: would you have some time to test qtdeclarative stable head compilation? at least when combined with our packaging + patches, I'm getting http://pastebin.ubuntu.com/6713954/ (git hash used is there in the directory)
[09:53] <Saviq> Mirv, sure, sec
[09:54] <Mirv> this is with normal qt 5.2.0 otherwise (qtbase + qtxmlpatterns)
[09:55] <Saviq> Mirv, I imagine this says "you need newer qtbase"
[09:57] <Mirv> Saviq: I wish even stable branch would be safe from the interdependencies :)
[09:58] <Mirv> but sure, I wouldn't be surprised. the referrals failing are to qtdeclarative's own sources, but maybe something in qtbase changed about finding sources.
[10:13] <mzanetti> Saviq: https://code.launchpad.net/~mzanetti/unity8/qml-in-cmake-take2/+merge/200793
[10:15] <mzanetti> thanks :)
[10:16] <Saviq> mzanetti, still not using colocated branches, btw? ;)
[10:16] <mzanetti> nope
[10:17] <mzanetti> but my disk space would appreciate it I guess
[10:18] <Saviq> Mirv, actually
[10:18] <Saviq> Mirv, qtdeclarative compiled fine here
[10:18] <Saviq> Mirv, clean chroot with qt5-beta2
[10:20] <mzanetti> Saviq: where did you get the plugin from?
[10:20] <Saviq> mzanetti, lp:~fboucault/bzr-colo/colo-push/ for some reason
[10:21] <Saviq> mzanetti, but lp:bzr-colo is probably a better source
[10:22] <dandrader> tsdgeos, about the horizontalJournal Q_ASSERt
[10:22] <dandrader> tsdgeos, I thought that the signal would only be emitted if the operation was async
[10:22] <tsdgeos> nope
[10:22] <dandrader> therefore that slot would only be called in the async case
[10:22] <mhr3> Saviq, you in a call already?
[10:22] <Saviq> mhr3, no
[10:22] <tsdgeos> dandrader: nope
[10:23] <tsdgeos> dandrader: which Q_ASSERT in horizontalJournal ?
[10:23] <tsdgeos> ignore me
[10:23] <tsdgeos> can't read
[10:23] <tsdgeos> ok
[10:23] <tsdgeos> :D
[10:28] <dednick> is s-jenkins down?
[10:29] <mzanetti> dednick: works for me
[10:29] <dednick> mh.
[10:30] <dandrader> tsdgeos, that one in itemCreated slot
[10:30] <tsdgeos> yes yes
[10:31] <dednick> stupid dns thing again... sigh
[10:31] <tsdgeos> dandrader: was lost in the way you built the sentence and how my brain read it
[10:49]  * mzanetti wishes we could wake up the screen by double tapping it
[11:11] <Mirv> Saviq: hrm!
[11:39] <dednick> mzanetti: any idea? https://jenkins.qa.ubuntu.com/job/unity-phablet-qmluitests-trusty/832/console
[11:39] <mzanetti> dednick: I've seen the same in one of my branches. So far I hoped it's temporary woes... seems not :/
[11:40] <mzanetti> Saviq: ^ ?
[11:41] <Saviq> hmmmpf
[11:41] <mhr3> isn't that debian saying "you really need to bump the version"?
[11:41] <Saviq> mzanetti, why does qmluitests build the package at all?
[11:41] <Saviq> mhr3, yeah it kind of is
[11:42] <Saviq> mhr3, but why would it suddenly start now?
[11:42] <Saviq> TBH I never understood when dpkg starts complaining about that
[11:42] <mhr3> error: ...  binary file contents changed
[11:43] <mzanetti> Saviq: we've always built the package for qmltests
[11:43] <Saviq> mhr3, ah, so you're saying it doesn't care until you change a binary file?
[11:43] <mhr3> Saviq, i'm no debian pro, but seems that way
[11:44] <Saviq> interesting...
[11:46] <dednick> wtf. my character map just changed, but it's still showing correct layout in region settings
[11:46] <Saviq> mzanetti, so what we're missing probably is bumping the version before building the package
[11:46] <Saviq> mzanetti, but why do we build the package at all?
[11:46] <mzanetti> Saviq: that was the most straight forward way to get it done in jenkins
[11:46] <dednick> funny thing is, i only have uk english installed... weird
[11:47] <Saviq> mzanetti, but that doesn't build the mocks etc. does it?
[11:47] <mzanetti> Saviq: sure it does. it's installed into the unity8-fake-env package
[11:49] <Saviq> mzanetti, I'm not sure that's true - not for *all* the mocks at least
[11:49] <Saviq> mzanetti, anyway
[11:49] <mzanetti> hmm, ok. I might miss something
[11:49] <Saviq> mzanetti, do you have access to the job?
[11:49] <mzanetti> yes, I do
[11:50] <Saviq> mzanetti, the pbuilderjenkins command
[11:50] <Saviq> mzanetti, doesn't use the hooks as defined in the job
[11:51] <Saviq> mzanetti, if that's on purpose, add H05set_package_version there and we should be good
[11:51] <mzanetti> Saviq: added
[11:52] <Saviq> mzanetti, dednick restarted the job, will be at http://s-jenkins.ubuntu-ci:8080/job/unity-phablet-qmluitests-trusty/834
[11:52] <mzanetti> dednick: I restarted your job. lets see what happens
[11:52] <mzanetti> oh
[11:52] <dednick> ta
[12:00] <mzanetti> looks better, yes
[12:03] <mzanetti> Saviq: I've changed the job to inherit hooks from upstream jobs and just add the B09qmltests etc
[12:03] <Saviq> mzanetti, yup
[12:03] <mzanetti> lets hope I didn't break it. You'll know where to find me in that case
[12:04] <Saviq> mzanetti, I DO KNOW WHERE TO FIND YOU!
[12:04] <mzanetti> :D
[12:04]  * mzanetti hides
[12:11] <Saviq> mzanetti, http://s-jenkins.ubuntu-ci:8080/job/unity-phablet-qmluitests-trusty/834/console
[12:11] <Saviq> Started by user Saviq
[12:11] <Saviq> Started by user mzanetti
[12:11] <Saviq> interesting ;D
[12:12] <Saviq> must be we triggered the exact same configuration and jenkins combined that into one
[12:13] <mzanetti> heh
[12:13] <mzanetti> I'd rather bet on a bug in jenkins :D
[12:22] <Saviq> /food
[12:43] <Saviq> tsdgeos, hJournal ready for merging or are you searching for the assert?
[12:43] <tsdgeos> Saviq: ready for merging
[12:43] <tsdgeos> i forgot to check the failure and reapprove
[12:44] <Saviq> tsdgeos, k
[12:44] <tsdgeos> test_show_hud_button_appears ?
[12:44] <tsdgeos> weird
[12:44] <tsdgeos> let's see next run
[12:45] <Saviq> tsdgeos, yeah, it does fail sometimes
[13:22] <Mirv> Saviq: one of these days I learn to attribute all mysterious immediate failures to syncqt when snapshot builds don't work
[13:24] <mzanetti> deleting the hud-service binary wasn't such a good idea :/
[13:25] <Saviq> Mirv, ;)
[13:25] <Saviq> mzanetti, btw, we've missed ../tests/*qml ../tests/*js :/
[13:26] <mzanetti> Saviq: true. I'll fix
[14:02] <tsdgeos> kgunn: you increased the dependency of unity-mir to mir* 0.1.3 but that's still not out, no?
[14:07] <tsdgeos> greyback: ok, https://code.launchpad.net/~aacid/unity-mir/application_manager_tests/+merge/180898 should be ready
[14:07] <tsdgeos> CI is failing to compile because the ↑↑↑ change
[14:07] <greyback> tsdgeos: \o/ thanks!!
[14:08] <tsdgeos> if you want to try now in the phone
[14:08] <tsdgeos> just do
[14:08] <tsdgeos> -               libmirserver-dev (>= 0.1.3),
[14:08] <tsdgeos> -               libmirclient-dev (>= 0.1.3),
[14:08] <tsdgeos> +               libmirserver-dev (>= 0.1.2),
[14:08] <tsdgeos> +               libmirclient-dev (>= 0.1.2),
[14:08] <tsdgeos> on the control file
[14:08] <tsdgeos> it worked for me
[14:13] <greyback> tsdgeos: ok
[14:17] <elopio_> Saviq: I was trying to use the tab bar from ubuntu ui toolkit, but it causes a couple of problems. The biggest is that when trying to open the files & folders scope, it tries to click on the right border of the screen and nothing happens there.
[14:17] <elopio_> I need to make a workaround on the toolkit emulator before it's usable by unity.
[14:19] <kgunn> tsdgeos: yes...release team is testing new mir, so they had to approve and push the bump
[14:20] <kgunn> it should be over soon (and hopefully mir out soon)
[14:20] <tsdgeos> great
[14:20] <tsdgeos> ;)
[14:21] <Saviq> elopio, ack
[14:21] <elopio> Saviq: but I need help from my branch, on mako there are failures that don't seem related to my branch. I was hoping to find aacid here today.
[14:22] <Saviq> elopio, tsdgeos [14:22] <Saviq> he's crypto, we know
[14:22] <Saviq> ;)
[14:22]  * tsdgeos hides behind his nicks
[14:22] <tsdgeos> elopio: need help?
[14:22] <tsdgeos> Saviq: remember we talked about the "Please enter SIM PIN" text a while ago?
[14:23] <Saviq> tsdgeos, not really, wassup?
[14:23] <tsdgeos> Saviq: basically you said "it should come from the indicator"
[14:23] <tsdgeos> but it's still there
[14:23] <elopio> tsdgeos: \o/ I found you!
[14:23] <Saviq> tsdgeos, right
[14:23] <elopio> let me get something to drink and wake up a little, and I'll start bothering you :)
[14:23] <Saviq> tsdgeos, file a bug please?
[14:23] <tsdgeos> Saviq: shall i open a bug or something so someone maybe acts on it
[14:24] <Saviq> tsdgeos, ↑ that
[14:24] <tsdgeos> Saviq: against what? unity8? or?
[14:24] <Saviq> tsdgeos, affects unity8 and indicator-network
[14:24] <tsdgeos> okidoki
[14:26] <tsdgeos> man i ate too much of my fake chocolate cava bottle :D :( :-S
[14:29]  * mzanetti googles chocolate cava bottle
[14:30] <tsdgeos> http://www.badamelos.com/1177-large_default/botellas-cava-benjamin-chocolate.jpg
[14:30] <tsdgeos> mzanetti: ↑↑
[14:30] <mzanetti> lol
[14:30] <mzanetti> leftover from new years eve?
[14:31] <tsdgeos> yep
[14:31] <Saviq> greyback, mterry_, standup
[14:37] <greyback> mzanetti: thanks :) When I reboot, or suspend/resume, PA thinks sound is at the usual place, but is actually 0. If I wiggle the mic volume, it then works
[14:38] <mzanetti> greyback: yeah... try a "asoundctl store" with non-muted settings
[14:42] <tsdgeos> Saviq: https://bugs.launchpad.net/indicator-network/+bug/1267135
[14:44] <elopio> I'm back. tsdgeos, please let me know when you have some time, it seems I'll need more help than what I thought.
[14:45] <tsdgeos> elopio: now is a good moment
[14:47] <elopio> tsdgeos: the dashContentList has a currentIndex property. My problem is that the QQuickLoader and the GenericScopeViews don't have an index.
[14:47] <elopio> so I have no way to tell which is the currently selected scope.
[14:47] <elopio> I was assuming that the order of the list would give me the right index, but on mako where the music scope is to the left, my assumption breaks.
[14:48] <tsdgeos> elopio: the current scope is the one of the currentIndex?
[14:49] <tsdgeos> dashContent.model list the order of them
[14:50] <tsdgeos> which is actually the list of visible scopes
[14:50] <tsdgeos> as returned by Scopes
[14:50] <elopio> let me see if autopilot can access that.
[14:50] <tsdgeos> elopio: what do you want to find out actually? name? or something else?
[14:51] <elopio> tsdgeos: well, what I need is a way to know what's the index of a scope. On the toolkit tabs I had the same problem, and they fixed it adding the a new tabIndex property to every tab.
[14:52] <tsdgeos> elopio: as said the index of a scope is it's index in the list of visible scopes
[14:52] <tsdgeos> i.e. whatever is sorting scopes it's not the ui
[14:55] <elopio> tsdgeos: right. The problem seems to be that the list of scopes returned by autopilot is not on the same order.
[14:55] <elopio> (Pdb) p self.dash.dash_content_list.currentIndex
[14:55] <elopio> 1
[14:55] <elopio> (Pdb) p self.scope_loaders[1].scopeId
[14:55] <elopio> u'music.scope'
[14:56] <elopio> there's the problem, because the selected scope at this moment is 'home.scope'
[14:56] <elopio> so we shouldn't rely on the order of elements that autopilot returns.
[14:57] <tsdgeos> what's scope_loaders ?
[14:57] <tsdgeos> i.e. who provides that info?
[14:58] <tsdgeos> and is self.scope_loaders[0] marked as visible or not?
[14:58] <elopio> tsdgeos: self.scope_loaders = self.dash.dash_content_list.select_many('QQuickLoader')
[14:59] <tsdgeos> ok
[14:59] <elopio> tsdgeos: and all of them always have visible=True, we can't rely on the visible property.
[14:59] <tsdgeos> so select_many is not giving you stuff in the corect order
[14:59] <elopio> (Pdb) p self.scope_loaders[1].visible
[14:59] <elopio> True
[14:59] <elopio> (Pdb) p self.scope_loaders[0].visible
[14:59] <elopio> True
[14:59] <tsdgeos> which given the name seems even reasonable
[15:02] <elopio> yes. But according to thomi, autopilot just returns the elements on the same order of the QML tree it sees.
[15:02] <elopio> as we have seen before, and now again, it seems a bad idea to rely on the order of the elements of the tree.
[15:02] <tsdgeos> so again, what do you need?
[15:02] <tsdgeos> know the current scope?
[15:03] <tsdgeos> maybe match it against the name of the selected tab?
[15:03] <tsdgeos> or that is what you're trying to test?
[15:04] <elopio> tsdgeos: not just know the current scope, I could use the isCurrent property for that.
[15:04] <elopio> I need to know the order of them, so I scroll to the left if the index I need is lower than the currently selected one, and scroll to the right if the index is higher.
[15:07] <tsdgeos> well then you can use the tabs?
[15:07] <tsdgeos> i think the tabs has getters
[15:07] <tsdgeos> let me see
[15:07] <tsdgeos> maybe not
[15:07] <elopio> tsdgeos: I found the bug and branch for the same problem on the toolkit:
[15:07] <elopio> https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1233402
[15:07] <tsdgeos> booo
[15:07] <tsdgeos> ok
[15:07] <tsdgeos> :D
[15:07] <elopio> tsdgeos: I could use the tabs instead of scrolling, but first I need to implement some changes on its emulator.
[15:08] <tsdgeos> elopio: so you want to do the change by swiping i guess, it's not ok that we add a switchToScope function
[15:09] <elopio> tsdgeos: sorry, I didn't get that last part.
[15:10] <tsdgeos> elopio: Dash.qml has a "function setCurrentScope"
[15:10] <tsdgeos> can you use that?
[15:10] <elopio> tsdgeos: no, with autopilot it all should be black box.
[15:10] <tsdgeos> or you want to trigger the change "emulating the user touch presses"?
[15:10] <tsdgeos> ok
[15:10] <elopio> I need to set the current scope only using the pointer.
[15:11] <tsdgeos> does autopilot know how to query models?
[15:11] <tsdgeos> if so i think that querying filteredScopes would be useful to get the order of things
[15:12] <tsdgeos> if not, someone should make autopilot able to introspect the models :D
[15:14] <elopio> tsdgeos: I think that's not possible. That's information that QML doesn't expose through the testability feature, that's what autopilot uses.
[15:14] <elopio> tsdgeos: but if you look at zsombi's branch: https://code.launchpad.net/~zsombi/ubuntu-ui-toolkit/tab-index/+merge/188769
[15:14] <elopio> it doesn't seem like a big change on the model
[15:14] <elopio> I don't know enough QML to do it myself on this case, though.
[15:16] <mzanetti> greyback: could we sort the appmanager model in a way that the focused one is at index 0?
[15:16] <tsdgeos> elopio: i'm understanding you can't access the attached properties of the listview deleagtes, no?
[15:16] <tsdgeos> elopio: i.e. i can use "index" inside a QML listview item
[15:16] <tsdgeos> and it'll give me the index
[15:18] <elopio> tsdgeos: I can access things like isCurrent and scopeId, but no, index doesn't seem to be available.
[15:18] <elopio> tsdgeos: have you used autopilot vis?
[15:18] <greyback> mzanetti: that should be the case already
[15:18] <tsdgeos> i used it once when all the stars aligned
[15:18] <elopio> it shows the QML tree as autopilot sees it. So those are the only things we can use.
[15:18] <mzanetti> greyback: seems not...
[15:18] <tsdgeos> errrrr, is everybody getting the tabs to show in unity8?
[15:18] <mzanetti> greyback: the first app I launch is always at 0
[15:18] <greyback> mzanetti: but I don't see the code to do it either
[15:18] <tsdgeos> they don't show here :-S
[15:18]  * tsdgeos does a clean build
[15:19] <greyback> mzanetti: suspect unity8 doing it
[15:19] <elopio> tsdgeos: I can see them. They work nicely here.
[15:19] <mzanetti> gnaaa
[15:19] <mzanetti> greyback: ok... I'll try to change it in my screenshotting-focusing branch
[15:20] <greyback> mzanetti: no objection here
[15:21] <tsdgeos> ok, tabs are here now, maybe needed a clean build
[15:21] <tsdgeos> elopio: let me try to run the visualizer
[15:22] <elopio> thanks tsdgeos. Take a look at the TabBar inside the PageHeader. It has a selectedIndex property. And then the AbstractButtons children of that TabBar have a buttonIndex property.
[15:23] <elopio> that's what I need. With those properties, I don't need to rely on the order of the children as autopilot sees them.
[15:25] <tsdgeos> sure
[15:25] <tsdgeos> adding the property is trivial
[15:25] <tsdgeos> it's just that i'd prefer not to add extra code just for the testing
[15:25] <tsdgeos> elopio: maybe you can use the "x" property of the loaders to sort them?
[15:30] <elopio> tsdgeos: I could use that. Let me try to see if it gets ugly.
[15:49] <elopio> tsdgeos: that will work nicely :) thank you.
[15:49] <elopio> when is your EOD?
[15:50] <tsdgeos> cool \o/
[15:50] <tsdgeos> in 1:10h aprox
[15:50] <tsdgeos> 6pm spain time
[15:58] <elopio> tsdgeos: I have a meeting now, so I probably won't be able to finish my branch by then. Can you please take a look tomorrow?
[15:59] <elopio> https://code.launchpad.net/~elopio/unity8/open_scope/+merge/200426
[16:00] <tsdgeos> sure
[16:05] <tsdgeos> Saviq: so i was thinking about the organic grid for the Dash vs the one in the gallery. Ours is always visible in full width and is designed to scrolls vertically while the one in the gallery is always full height and designed to scroll horizontally. That's not a radical problem, but introduces a few else/ifs here and there, want me to code directly for both or just catter our needs at first stage and improve later?
[17:06] <kgunn> mterry_: ping
[17:06] <mterry_> kgunn, hello
[17:06] <kgunn> mterry_: hey hope you're feeling better....
[17:06] <kgunn> got a question for you that i should already know :)
[17:06] <mterry_> kgunn, OK
[17:06] <kgunn> so i was cleaning up some wiki stuff....for unity8
[17:07] <kgunn> and greeter section referenced
[17:08] <kgunn> https://launchpad.net/unity-greeter
[17:08] <kgunn> but isn't the greeter in unity8 now ?
[17:08] <kgunn> mterry_: ^
[17:08] <mterry_> kgunn, yes.  The phablet greeter is in unity8
[17:08] <mterry_> kgunn, unity-greeter is the old greeter
[17:08] <mterry_> "old"
[17:09] <kgunn> mterry_: ok...that's what i tho
[17:09] <kgunn> t
[17:09] <kgunn> mterry_: so even after you land the split...it'll still be the phablet greeter in use right ?
[17:10] <mterry_> kgunn, yes
[17:11] <kgunn> mterry_: thanks...i'll make it match
[17:11] <mterry_> kgunn, same source package (unity8) but new binary package (unity8-greeter)
[17:11] <kgunn> ;)
[17:11] <kgunn> mterry_: curious...why is it delivered in a bin like that ?
[17:11] <kgunn> at least the unity-greeter
[17:11] <mterry_> kgunn, I don't follow
[17:12] <kgunn> oh nvmd...i see...
[17:12] <kgunn> mterry_: ignore me
[17:18] <mhall119> Saviq: has there been any progress on building Unity 8 on Saucy?
[17:38] <Saviq> mhall119, there's more data on the failures, so hopefully it'll get better soon
[18:06] <greyback> fginther: hey, can I book some CI expert time for unity-mir. We've a branch that adds tests, which must run in an environment where Mir can execute. We need a hand to set up CI to deal with that
[19:12] <fginther> greyback, I can help but I'll need to get back to you later, I have some fires to put out
[19:13] <greyback> fginther: sure, it's far from urgent
[20:54] <karni_> Saviq: If there are any conventions on the team I didn't follow, just lemme know :) https://code.launchpad.net/~unity-team/unity8/new-scopes-horizontal-card-layout/+merge/200910
[21:03] <Saviq> karni, cheers
[21:04] <Saviq> karni, jest już test "test_art_size_data"
[21:04] <Saviq> ooh english ;)
[21:05] <Saviq> karni, there's already test_art_size_data
[21:05]  * karni paczy ;D
[21:05] <Saviq> karni, would make sense to build test_art_image_size into it
[21:06] <Saviq> karni, "card-size": "medium" is unsupported (and ignored, for that matter) in horizontal layout - not sure we should test that... or maybe we should, but add a "small" one, too
[21:07] <karni> Saviq: oh okay. I needed any size, I can replace that with small, as all sizes are covered in previous tests, right?
[21:07] <Saviq> karni, why did you need a size?
[21:08] <Saviq> karni, what I mean is: in horizontal layout, the card-size setting is ignored - so we should either test that setting it doesn't matter, or not set it at all
[21:08] <karni> Saviq: I looked at the code, seems I could have gone with the default
[21:09] <karni> Saviq: I'll remove that, yes
[21:09] <Saviq> karni, for test_card_horizontal_layout, you're only checking for width, so integrating into test_card_size should work
[21:09] <karni> Saviq: I think I wanted it to test the width/height of the artImage, but we decided that need not to be tested
[21:10] <karni> Saviq: agreed on first and last comment, too. fixing.
[21:11] <Saviq> karni, I'd rename test_*_anchors into test_*_layout, as we're not actually checking the anchors
[21:11] <karni> Saviq: agree :)
[21:12] <Saviq> karni, and now... .left/right/top/bottom are anchor lines
[21:12] <Saviq> karni, not pixel values
[21:12] <Saviq> karni, so test_header_anchors should actually fail
[21:12]  * karni looks
[21:13] <karni> Saviq: the last test? I'm not actually using anchors, the test name was confusing.
[21:13] <Saviq> karni, that's the thing - you are ;)
[21:14] <karni> let me do the art test refactor, and I'll push, so we're on the same page :)
[21:14] <Saviq> karni, header.top, header.left are anchor lines (not anchors, but something that can be attach to anchors)
[21:14] <Saviq> or something that anchors can attach to
[21:14]  * karni nods
[21:15] <Saviq> karni, so in the last test you're comparing header.top to art.bottom, for example
[21:15] <karni> may have gone blindfolded a bit
[21:16] <karni> +            top: template && template["card-layout"] [21:16] <Saviq> karni, that's header.anchors.top, not header.top
[21:16] <Saviq> which are two distinct anchor lines - what I mean is that if you revert the changes to Card.qml, the test will still pass (assuming it passes now)
[21:16] <karni> ooooh right!
[21:16] <karni> Saviq: lemme fix that :) thanks for the super fast review :D
[21:16] <Saviq> karni, so yeah, you can't compare anchor lines of different objects
[21:17] <Saviq> karni, so you should look at x/y/width/height instead
[21:17] <Saviq> adding where necessary
[21:17] <karni> yes, all tests pass, but I obviously failed there with that anchor bit
[21:18] <Saviq> karni, shelve changes to qml/ and run your tests suite again - make sure that all tests that should fail - do
[21:19] <karni> Saviq: regarding your first/second comment about integrating test_art_image_size into test_art_size, I'd have to name properties like "imageWidth" and "imageHeight" because most of test_art_size concerns art, while I'm testing artImage
[21:19] <karni> So.. does it in fact make sense to pull this test into test_art_size?
[21:20] <karni> test_art_size tests width/height of testCase.art, while test_art_image_size tests width/height of testCase.artImage
[21:20] <karni> (FWIW, bit confusing terminology ;D)
[21:20] <karni> good suggestion. it did feel weird to write tests after the code ;D
[21:22] <Saviq> karni, I know, sorry for that ;)
[21:22] <Saviq> karni, was easier to write the code than tests ;D
[21:22] <karni> Saviq: no worries, I know how fun it is to improve/fix things :D
[21:22] <karni> haha, happy I can help (and learn!)
[21:23] <Saviq> karni, you shouldn't be testing artImage's size at all, as that component isn't even visible - the UbuntuShape around it is what we care for
[21:24] <karni> Saviq: may have gone overboard trying to cover every line of your code ;D
[21:25] <Saviq> karni, so yeah, there's only one additional entry to test_card_size_data that should be added
[21:25] <karni> Saviq: yes, fixed that
[21:25] <Saviq> karni, yeah, coverage for QML (or UI, for that matter) is unfortunately an arbitrary thing
[21:25] <karni> haven't pushed yet, want to fix those anchors/pixels thing you noticed
[21:25] <Saviq> karni, cheers
[21:25] <karni> :)
[21:25] <karni> Thank you!
[21:25] <Saviq> karni, aren't you past EOD yourself, btw?
[21:26] <karni> Saviq: You working from Poland?
[21:26] <Saviq> karni, we're not talking about me here, are we now :P
[21:26] <karni> Saviq: I wonder, why would you ask hahahahah
[21:26]  * karni laughs
[21:26]  * Saviq → food
[21:27] <Saviq> karni, just leave it here if you have more, will reply when around the keyboard later
[21:27] <karni> Saviq: thanks! :)
[21:52] <karni> Saviq: updated the MP. Left one 'XXX', can't get that line in test_header_layout to pass. I'll get something to eat and will try the shelves that you suggested to make sure stuff would fail where it should.
[22:04] <Saviq> karni, a) test_art_layout is bad, tryCompare takes three arguments: object, propertyName, timeout
[22:04] <Saviq> so tryCompare(testCase.header.x, data.headerLeft, data.value); is bad
[22:05] <Saviq> not to mention data.headerLeft and data.value are undefined
[22:06] <Saviq> karni, as for the other thing... the problem is that the card is laid out only when the test is executed, the _data() function is called before that, on the default layout, so art.width is 148 then, but when you select index 5, it becomes 80
[22:07] <Saviq> but data.left is already evaluated with 148, so the test fails
[22:22] <Saviq> karni, http://paste.ubuntu.com/6717510/ fixes
[22:23] <Saviq> karni, actually make that http://paste.ubuntu.com/6717513/
[22:59] <karni> Saviq: wow.. I'm surprized I wasn't thrown at that .headerLeft was not defined (I did change the name, missed that one). and tests still passed. not reassuring :(
[23:33] <karni> Saviq: fixed along your diff, appreciated https://code.launchpad.net/~unity-team/unity8/new-scopes-horizontal-card-layout/+merge/200910


[08:52] <mandel> morning all!
[09:50] <rye> c_smith: hello, are you still here? Could you provide more information about the crash?
[11:01] <gatox> good morning!
[11:10] <gatox> brb
[11:24] <gatox> back
[12:26] <alecu> hello all!
[12:28] <gatox> alecu, hi
[12:30] <mandel> alecu, gatox, morning!
[12:31] <mandel> alecu, alecu, I have one more review and all the fsevents changes will be merged! so I'll do revies for gatox and will propose my branch
[12:31] <gatox> mandel, ack
[12:31] <mandel> gatox, how is the change that was driving you crazy?
[12:32] <gatox> mandel, i had some issues, it's already working.... you can see it in the MP
[12:32] <mandel> oh, and my internet is super crap today.. so expect me to disappear every now and then..
[12:38] <mandel> I'm off to lunch and will be later back from 3g... puto movistar de los huevos!
[12:39] <gatox> ack
[12:39]  * mandel goes to have lunch cursing..
[12:56] <dobey> lol
[13:10] <dobey> and it's release day
[13:18] <alecu> mandel, gatox: send reviews my way
[13:18] <dobey> haha
[13:18] <dobey> bug #1017220 is awesome
[13:18] <gatox> alecu, https://code.launchpad.net/~diegosarmentero/ubuntuone-client/darwin2-fsevents/+merge/111427
[13:18] <gatox> alecu, https://code.launchpad.net/~diegosarmentero/ubuntuone-client/darwin3-fsevents/+merge/111666
[13:19] <gatox> alecu, and i'm fixing the test in the last one..... i learn to never say again: "this should be easy" (refactor related)
[13:23] <alecu> gatox: great!. I need to go to the paint shop, because my flat is getting some fixes... and I'll do that review in 15'
[13:23] <gatox> alecu, no problem
[13:50] <mandel> alecu, gatox, ralsina, dobey I'm off some mins to move to a diff location with better connection
[13:50] <mandel> should just take min 10 mins max
[13:50] <gatox> mandel, ac
[13:50] <ralsina> dobey: since we still have not SRUd 3.0.2 and we barely released it on windows, what o you think of skipping a release?
[13:52] <dobey> what do you mean skipping a release?
[13:53] <ralsina> dobey: you said it's release day. We barely finished the previous release
[13:53] <ralsina> dobey: so, maybe there's no point in doing a new release today
[13:54] <ralsina> briancurtin: ping
[13:54] <briancurtin> ralsina: pong
[13:54] <ralsina> briancurtin: my XP VM has decided my windows is fake
[13:54] <ralsina> briancurtin: could you check that our latest release works on a clean XP?
[13:54] <briancurtin> ralsina: checking now
[13:54] <ralsina> briancurtin: if not, I will do it after I finish reinstalling
[13:54] <ralsina> briancurtin: thanks. By the symptoms described, I think the VS runtime is not being installed :-(
[13:56] <briancurtin> ralsina: it's packaged side-by-side now (i think that's the right term)...but im getting the VM up right now
[13:56] <ralsina> briancurtin: ack
[14:06] <briancurtin> ralsina: my VM already has the runtime installed and i cant find a way to get it off of there, so i'll need to setup a clean VM to try it
[14:07] <dobey> ralsina: well, unless there's a security update coming out of nowehre tomorrow, i'd prefer to do the release
[14:07] <ralsina> briancurtin: ok, I'll do the same thing
[14:07] <ralsina> dobey: ok, then
[14:07] <dobey> ralsina: even with no changes, i think there is a point to doing the releases
[14:07] <dobey> and with no changes, the release is really fast anyway :)
[14:07] <dobey> since there's no mucking about with triage and backport branches in that case
[14:07] <ralsina> dobey: plus we may get to test the MRE with 3.0.3 instead of 3.0.2
[14:08] <dobey> today isn't a 3.0.x release day
[14:08] <dobey> it's 3.99.x
[14:08] <dobey> for quantal
[14:08] <mandel> I'm back!
[14:08] <dobey> hide your children!
[14:08]  * mandel cannot believe that 3g is faster than the dsl connection
[14:09]  * ralsina goes to check back the schedule
[14:09] <ralsina> dobey: ok, 3.99.x is cool
[14:10] <dobey> we still don't have a schedule for 3.0.x releases
[14:13] <dobey> alecu: btw, the ubuntu-sso-client stable-1-4 tests aren't running on oneiric (because we can't run tests on oneiric because of twisted); all the oneiric stable branches are being merged on natty because of the twisted/python-gobject issues that weren't resolved in oneiric
[14:13] <ralsina> brilliant, my *physical* XP CD doesn't work anymore :-/
[14:16] <mandel> ralsina, alecu, I'll be working on landing the keyring patched on pykeyring trunk f that is ok with you
[14:16] <mandel> gatox, is there anything I have to review?
[14:17] <gatox> mandel, this: https://code.launchpad.net/~diegosarmentero/ubuntuone-client/darwin2-fsevents/+merge/111427  -  https://code.launchpad.net/~diegosarmentero/ubuntuone-client/darwin3-fsevents/+merge/111666
[14:17] <mandel> gatox, ack
[14:26] <mandel> gatox, I'd love to see how things were breaking when you added the events as class attrs
[14:26] <briancurtin> ralsina: doesn't work on XP.................
[14:26] <ralsina> briancurtin: could you try if installing the runtime fixes it?
[14:27] <gatox> mandel, is just a comment? or you really want to see it?? because that was on friday.....  i didn't save any trace, and i should redo all the code to reproducce that
[14:27] <ralsina> briancurtin: if it does, then we can revert the ubuntuone.xml changes, resign the installer and reupload
[14:28] <mandel> gatox, was not just a comment, but I guess I can take a look from here if that is the case (that you do not ave the traces)
[14:28] <mandel> gatox, I think it should be doable without doing any hacky things, I simply want to evaluate the problems, that is all
[14:28] <gatox> mandel, ack
[14:28] <mandel> briancurtin, I added a small needs fixing in one of the py3 branches, I think dobey is correct regarding the order of the imports
[14:31] <briancurtin> ralsina: 3.0.1 doesn't work either
[14:31] <ralsina> briancurtin: whoa
[14:31] <ralsina> briancurtin: 3.0.0? ;-)
[14:31] <dobey> 2.99.3?
[14:32] <dobey> or 2.0.3 or whatever it is
[14:32] <briancurtin> hmm, and 3.0.1 was the last release where we ran vcredist as an installer step
[14:32] <briancurtin> weird
[14:33] <ralsina> briancurtin: indeed
[14:33] <ralsina> briancurtin: did installing vcredist fix it?
[14:33] <ralsina> briancurtin: because it may be completely something else
[14:34] <briancurtin> ralsina: i sort of did that in a way by trying 3.0.1 since it installs that and it doesnt work. i'll try 3.0.2 now that 3.0.1 installed vcredist to see what happens
[14:34] <ralsina> briancurtin: ack
[14:36] <mmcc> happy monday, folks
[14:39] <dobey> meh, alpha freezes still on
[14:43] <briancurtin> ralsina: its gotta be something else. now that the machine has the redist installed, neither 3.0.1 nor 3.0.2 work
[14:43] <ralsina> briancurtin: sigh
[14:44] <ralsina> briancurtin: is it the right vcredist?
[14:44] <ralsina> briancurtin: what size is it?
[14:44] <briancurtin> yep
[14:44] <briancurtin> ralsina: 1779 kb
[14:45] <briancurtin> ralsina: for vcredist_x86.exe
[14:45] <ralsina> briancurtin: ok, let me check something
[14:45] <briancurtin> ralsina: i just ran a repair install of vcredist and it claims to have worked, but u1cp still doesn't start
[14:46] <ralsina> that seems to be the right one AFAICS
[14:46] <ralsina> briancurtin: no, that one's too new
[14:46] <briancurtin> ralsina: that's the same one ive been packaging all along
[14:46] <ralsina> we need the 1.1MB vcredist_x86.exe
[14:47] <ralsina> briancurtin: yeah, it's the same one I have uploaded
[14:47] <ralsina> briancurtin: but it's not the one my notes say
[14:47] <ralsina> briancurtin: and I have no idea why, either
[14:48] <briancurtin> ralsina: i just looked back and 3.0.0 was created with the 1779kb vcredist. it looks like i deleted the 3.0.1 folders
[14:49] <briancurtin> i dont have any 2.x installer folders around if i ever created them, but i only seem to have downloaded that 1779kb vcredist_x86.exe one time and used it everywhere
[14:49] <ralsina> briancurtin: I don't have any copies of the smaller one, either
[14:49] <briancurtin> i'll try to find this 1.1mb version
[14:49] <ralsina> briancurtin: however, I even blogged about it http://lateral.netmanagers.com.ar/weblog/posts/BB955.html
[14:50] <ralsina> briancurtin: and I specifically say "get the 1.1MB one"
[14:50]  * ralsina hates ralsina sometimes
[14:52] <mandel> mmcc, I did an update for: https://code.launchpad.net/~mandel/ubuntuone-fsevents-daemon/less-error-prone/+merge/111000
[14:52] <mandel> gatox, if you can take a look at that one ^ I would appreciate it :)
[14:53] <ralsina> briancurtin: latest version is 4.8MB too
[14:53] <mmcc> cool mandel, thanks, I'll go look
[14:53] <gatox> mandel, sure
[14:53] <mandel> cheers
[14:54] <briancurtin> ralsina: i found the SP1 version at 4.0mb
[14:54] <ralsina> briancurtin: the 2005 version is 2.6MB
[14:54] <ralsina> and the 2.8 is 1.7 which is probably the one we have
[14:54] <ralsina> 2008
[14:54] <briancurtin> ralsina: we would need 2008
[14:55] <ralsina> briancurtin: let's try the 4MB one then
[14:57] <ralsina> briancurtin: the 2.99.1 build was done with the 1.8MB one, too
[14:57] <ralsina> briancurtin: so it may be something else entirely
[14:59] <ralsina> briancurtin, mandel, dobey, alecu,gatox, thisfred, mmcc: stanup in 2'
[14:59] <gatox> ack
[14:59] <thisfred> sí jefe
[14:59] <mmcc> mandel, +1
[15:00] <gatox> me
[15:00] <thisfred> me
[15:00] <briancurtin> me
[15:00] <mmcc> me
[15:00] <ralsina> me
[15:01] <dobey> me
[15:01] <dobey> alecu, mandel?
[15:01] <alecu> me
[15:01] <mandel> me
[15:01] <gatox> DONE:
[15:01] <gatox> Couple of reviews, submit some branches for review (and add some corrections), working on the last branch.
[15:01] <gatox> TODO:
[15:01] <gatox> Finish fixing the broken tests in the last branch and propose
[15:01] <gatox> BLOCKED:
[15:01] <gatox> No
[15:01] <gatox> thisfred, go
[15:02] <thisfred> DONE: Bug #999569 Bug #999562 TODO Bug #999562 | Dentist apt. at 4 (now +5 hours), will work a little longer to make up for it BLOCKED: no, NEXT: briancurtin
[15:02] <briancurtin> DONE: python3 research/organization, also got antsy and started doing easy ports after looking at the 2to3 diff
[15:02] <briancurtin> TODO: find out whatever happened to XP releases, fix that
[15:02] <briancurtin> BLOCKED: XP sucks
[15:02] <briancurtin> NOTE: i have a PSF board meeting in 1 hour, should last for around 30 minutes
[15:02] <briancurtin> NEXT: mmcc
[15:02] <mmcc>  DONE: WWDC videos & 10.7/8 docs, uncovered some interesting FSEvents changes in Lion
[15:02] <mmcc>  TODO: chat about FSEvents? more killing imports that install reactors...
[15:02] <mmcc> BLOCK: none
[15:02] <mmcc>  NEXT: ralsina
[15:02] <ralsina> DONE: worked a bit more on cmake for u1db, askubuntu, canonicaladmin, misc stuff, worked on setting up a lot of VMs, Q VM  failed big time, retrying TODO: finish Q VM, try to help debug windows breakage, finish cmake'ing  u1db, BLOCKED: VBox is acting up badly NEXT:  dobey
[15:02] <dobey> DONE: reviews
[15:02] <dobey> TODO: release day
[15:02] <dobey> BLCK: None.
[15:02] <dobey> alecu
[15:03] <alecu> DONE: a few reviews, a fix for bug #1007109, tried to debug (and failed) why this branch won't merge: https://code.launchpad.net/~alecu/ubuntu-sso-client/use-pycurl-1-4/+merge/110636
[15:03] <alecu> TODO: heed dobey's warning re: merge, catch up with py3k with brian, do more mac reviews
[15:03] <alecu> BLOCKED: by non-merging branch
[15:03] <alecu> NEXT: mandel
[15:03] <mandel> DONE: reviews, reviews, reviews. Look at the state of pykeyring, not happy. Update fsevents last branch (we stay with sbjson mmcc :) )
[15:03] <mandel> TODO: more reviews. What to do with pykeyring.
[15:03] <mandel> BLOCKED: no yet stupid ISP left me with no internet at the office.
[15:03] <ralsina> briancurtin: it may be that we are doing it now with a new python build and the runtime is not compatible?
[15:04] <mandel> mmcc, superb, thx!
[15:04] <ralsina> briancurtin: OTOH, in the machine where you have the runtime it works, which makes it more confusing to me
[15:04] <mandel> mmcc, we are very very close to get a sd running with no problems on mac :)
[15:04] <briancurtin> ralsina: the only place it seems to work for me is 7
[15:04] <ralsina> briancurtin: ok
[15:05] <alecu> mmcc: "uncovered some interesting FSEvents changes in Lion" ???? tell us more!
[15:05] <briancurtin> ralsina: we build the exes with a stock python 2.7 which is built with VS2008. trying the bigger/newer vcredist now
[15:05] <ralsina> briancurtin: ack
[15:05] <mmcc> alecu: the short version, since Lion, FSEvents can give you per-file events. They just didn't really tell anyone
[15:06] <mmcc> I was watching the video for "what's new in the filesystem" at WWDC2012, and the guy mentioned it off-hand
[15:06] <briancurtin> those are the best kind of changes. "here's something people want...*fixes it, doesn't document it*"
[15:06] <mmcc> so I dig around, and it's listed in the API changes, but not documented
[15:06] <alecu> mmcc: is that on 10.8?
[15:06] <ralsina> mmcc: WTF
[15:06] <mmcc> 10.7
[15:06] <alecu> lovely
[15:06] <mmcc> ralsina: I KNOW
[15:07]  * ralsina goes check if his computers makes waffles and they just forgot to mention it
[15:07] <alecu> gatox: now we'll have to contribute fixes for macfsevents to do that
[15:07] <mmcc> the kicker is that they may still coalesce events in some cases. I'm digging up the little snippet of docs I found about that
[15:07] <ralsina> but hey, good news :-)
[15:07] <mandel> ralsina, mmcc, alecu so all the work we did is just for 10.6?
[15:07] <mmcc> I want to run a test once I get my new system with 10.7 (a couple days) - how often do they coalesce events?
[15:07] <briancurtin> ralsina: 2008 SP1 redist doesn't help...it has to be something else
[15:07] <gatox> alecu, it seems
[15:08] <ralsina> briancurtin: ok
[15:08] <briancurtin> or it doesnt have to, but this seems too weird
[15:08] <mmcc> mandel, maybe - if they coalesce events often, it might still have a lot of overhead to use fsevents
[15:08] <alecu> ralsina: btw: what was the problem with the Q vm?
[15:08] <ralsina> alecu: it doesn't freaking boot after install
[15:08] <alecu> ralsina: is that OpenGL/unity related?
[15:08] <ralsina> alecu: also, install took 3.5 hours
[15:09] <ralsina> alecu: what I get for using a daily ISO
[15:09] <mandel> mmcc, hm.. well, if it is the case (that we did it for nothing) we deserve it for using a not documented api
[15:09] <alecu> ralsina: did you try the alpha 1 as well?
[15:09] <ralsina> alecu: I am downloading it, 80% done
[15:10]  * briancurtin brb
[15:11] <mmcc> mandel heh, the new API is also not documented... :p
[15:11] <mandel> mmcc, lol
[15:12] <mmcc> so it's in the auto-generated header documentation but not the written guide to using fsevents. Here's the headerdoc: http://developer.apple.com/library/mac/#documentation/Darwin/Reference/FSEvents_Ref/FSEvents_h/index.html#//apple_ref/c/econst/kFSEventStreamCreateFlagFileEvents
[15:12] <mandel> dobey, pyflakes and python-mocker are not installed when doing sudo apt-get build-deps ubuntuone-client, is that a bug?
[15:13] <dobey> not installed where?
[15:13] <ralsina> mmcc: that feels just like linux. Really.
[15:13] <mandel> dobey, in P
[15:14] <dobey> mandel: no, it's not a bug really. you don't have ppa:ubuntuone/nightlies added i guess
[15:14] <mmcc> ralsina: except with linux at least we could've looked at the source. I'm quite fond of looking at the source...
[15:14] <mmcc> used to do that with opensolaris a lot, handy.
[15:14] <ralsina> yeah
[15:14] <mandel> dobey, oh..  that could be the reason, is a new set up
[15:14] <dobey> that's it then
[15:14] <ralsina> I think I will go have some coffee.
[15:15] <mmcc> so that fsevents header comment doesn't mention coalescing. I know I saw it, but my browser session died. looking through history now
[15:16] <dobey> need to get lunch. bbiab
[15:17] <mmcc> ah, ok - it's just down the page - the flag kFSEventStreamEventFlagMustScanSubDirs tells you that you get a dir path and you have to scan it and every subdir below it
[15:17] <mmcc> so if that happens a lot, it's not much better than old FSEvents
[15:19] <mandel> mmcc, they must have something for icloud to deal with this, right?
[15:26] <mandel> gatox, the only issue I see with the fact that the events are not class attrs is that we will have an interesting problem getting your work and my work together. I use diff values comming from the daemon
[15:26]  * briancurtin back
[15:26] <mandel> gatox, and we will not know which implementation will work until we try to connect to the daemon and get an error
[15:27] <gatox> mandel, maybe i was doing something wrong... my brain wasn't in his best shape
[15:27] <mandel> gatox, not to worry, I can take care of that :)
[15:27] <mandel> gatox, your brain I mean, you do the code!
[15:27] <mandel> heheh
[15:28] <gatox> jajajaa
[15:29]  * gatox lunch
[15:30] <mmcc> mandel, just saw your note - what do you mean about icloud? I don't think it necessarily uses fsevents
[15:30] <mandel> mmcc, can I have the +1 for https://code.launchpad.net/~mandel/ubuntuone-fsevents-daemon/less-error-prone/+merge/111872 I had to remove the prerequisite and it remove your vote.. stupid lp
[15:31] <mmcc> spotlight does, and time machine does, but icloud support seems to be built in to the frameworks, above the filesystem
[15:31] <mmcc> mandel ok, just a sec
[15:31] <mandel> mmcc, they most know some how what files changed.. well to be hones I have never used icloud
[15:31] <mmcc> mandel - icloud isn't a file sync service. think of it as being designed for the iphone first, where there is no user-visible file system
[15:32] <mandel> mmcc, ah.. so we are not in the same boat, right>
[15:32] <mandel> ?
[15:32]  * mandel has new keyboard..
[15:32] <mmcc> right, u1 and icloud have different goals
[15:32] <mmcc> very different technically, perhaps less different to the user, depending on what kind of user
[15:35] <mmcc> actually i think u1db and icloud potentially have more in common, although icloud is much bigger - they have a key-value store as one part of it, but there's also document-level stores and a core-data store, which is pretty interesting
[15:36] <rye> ralsina: ubuntuone nautilus plugin does not work properly for file publishing - the flaw is in libsyncdaemon and plugin (anybody actually depends on libsyncdaemon?) - any plans to make it work?
[15:36] <ralsina> rye: libsyncdaemon is used only for that plugin AFAIK
[15:37] <ralsina> rye: have the bug # handy?
[15:38] <mandel> mmcc, we had a key-value store using couch, we will have a new one soon :)
[15:39] <rye> ralsina: bug #753319 and bug #975989
[15:39] <mmcc> mandel are you referring to u1db or something else I'm not aware of?
[15:39] <mandel> mmcc, yes, u1db, we used to have desktop-couch but that did not work well :(
[15:39] <ralsina> rye: k, I will try to take a look myself this week, and if I can't fix it, I'll try to see if dobey has any time for it next week
[15:40] <ralsina> rye: 975989 looks easier
[15:40] <mmcc> mandel right, I knew about that project before and I've seen some old discussion about it around... nice idea, bummer it was so painful
[15:40] <mandel> mmcc, yep
[15:41] <rye> ralsina: yes
[15:42] <mandel> gatox_lunch, ignore the diff size of https://code.launchpad.net/~mandel/ubuntuone-fsevents-daemon/less-error-prone/+merge/111872 it seems that readding sbjson has made bzr get very very confused
[15:44] <mandel> facundobatista, quick question, if I set a file to be chmod u-w and then I ty to sync it, what should it happen? atm I think we fail due to the rights
[15:49] <mandel> gatox_lunch, there seems to be a merge issue in the other branch, set it to needs fixing
[15:50] <gatox_lunch> mandel, ack
[15:51] <nigelb> where's sil?
[15:59] <thisfred> nigelb: in a meeting, away from his laptop
[15:59] <nigelb> thisfred: ouch, he has a classroom session starting now-ish
[16:00] <thisfred> nigelb: I forwarded the message best I could
[16:00] <nigelb> thisfred: thanks, I think he may have rescheduled just now.
[16:00] <thisfred> ah
[16:02] <nigelb> thisfred: apparently not. the rescheduled list doesn't ahve him
[16:02] <nigelb> He's coming in I guess :)
[16:02] <nigelb> thisfred: thanks a bunch!
[16:03] <thisfred> np :)
[16:06] <nigelb> yay aquarius!
[16:07] <aquarius> mhall119, ping
[16:07] <aquarius> I didn't think I was doing this session :(
[16:08] <mhall119> aquarius: can you?  even if it's just an overview of the REST apis?
[16:08] <aquarius> mhall119, what do I have to do? I haven't prepped, but I can wing it
[16:08] <aquarius> do I need to start now?
[16:08]  * briancurtin afk for a short bit, PSF board meeting call
[16:08] <mhall119> aquarius: I'll start a hangout and invite you to it, then you just chat and screenshare
[16:09] <mhall119> aquarius: https://plus.google.com/hangouts/_/dcb85bf832b154aef74b1e5c5ac26057071f4d10?authuser=0&hl=en
[16:11] <facundobatista> mandel, we fail to sync it because we can not *write*?
[16:11] <mandel> facundobatista, I wonder, can we not try to set the rights to rw like we do in the read only shares?
[16:12] <mandel> facundobatista, or I think we should have a way to tell the user about it, that is, wrong rights and it wont be updated, do we have something like that?
[16:18] <dobey> i haven't had time to move it yet, but i was planning to rewrite/move libsyncdaemon into libubuntuone this cycle
[16:18] <dobey> rye, ralsina: ^^
[16:19] <dobey> of course, that doesn't really help existing installs
[16:19] <ralsina> dobey: we should try to find a way to make it happen or fix the bugs. I suspect fixing *all* the bugs is more expensive :-/
[16:23] <dobey> right. and i don't see any way to fix all the bugs without the rewrite anyway
[16:24] <ralsina> ok
[16:24] <ralsina> but this would only help us in Q
[16:25] <ralsina> unless we do something very difficult about P
[16:25] <dobey> right
[16:25] <ralsina> and we are to support P for 5 years
[16:25] <dobey> we need to do that very difficult thing for P at some point anyway I think
[16:26] <dobey> supporting 3.0.x for 5 years is not going to be fun
[16:26] <dobey> just like supporting 1.2.x for 3 years isn't fun
[16:27] <ralsina> so let's aim for it
[16:27] <ralsina> dobey: a firefox-style SRU
[16:28] <dobey> well, we are working toward it.
[16:28] <rye> dobey: agree with you re: rewriting.
[16:28] <ralsina> exactly
[16:28] <ralsina> so, we should rewrite and after Q release try to get it back into P
[16:28] <dobey> yep
[16:29] <dobey> there are some things that need to happen for that still
[16:29] <dobey> and i have already started doing some of it; trying to get the test suites running during build in Q, and having the necessary bits to build some of the packages all the way back to lucid
[16:30] <gatox> mandel, ping
[16:30] <ralsina> rye: so, basically, short term I will try to get a fix for the easy one, the fix for the one that causes bad performance/hangs will probably not happen
[16:30] <mandel> gatox, pong
[16:30] <dobey> there are a couple of problems with lucid not having things we need now, and such. but we're doing a good start
[16:30] <gatox> mandel, did you fix the conflicts you mention here_: https://code.launchpad.net/~mandel/ubuntuone-fsevents-daemon/less-error-prone/+merge/111000 ?
[16:30] <dobey> i'll look more after i get the releases done today
[16:30] <ralsina> dobey: things that take longer than 6 months are starting to not affect lucid much
[16:31] <dobey> yeah i'm not sure how many users we still have on lucid
[16:31] <dobey> probably not many :(
[16:31] <mandel> gatox, yes, there should be no merge conflits, is just that it was build on top of a previous branch that was removed and that is why the diff is huge
[16:31] <gatox> mandel, ack
[16:32] <dobey> natty is a bit bigger of a problem, but it's also going to be EOL come October anyway
[16:33] <ralsina> dobey: exactly
[16:34] <dobey> so maybe i can do some hacking to get 3.0.x built on lucid in the stable PPA, and we just tell people to use that, who are on lucid
[16:34] <ralsina> dobey: +1
[16:34] <ralsina> lucid +ppa sounds like a good idea
[16:34] <gatox> mandel, +1
[16:34] <mandel> gatox, superb! thx!
[16:35] <dobey> i'll poke at that after i get the releases done today
[16:35] <dobey> which i can hopefully actually get done today, as i don't have 50 surprises coming at me this week :)
[16:35] <mandel> gatox, can I have the +1 here, that MP is superseeded: https://code.launchpad.net/~mandel/ubuntuone-fsevents-daemon/less-error-prone/+merge/111872
[16:39] <gatox> mandel, done
[16:39] <mandel> gatox, gracias
[16:40] <mandel> alecu, can I have a re-review for https://code.launchpad.net/~mandel/ubuntuone-client/better-encoding/+merge/111580
[16:41] <alecu> mandel: sure. I'll have lunch and work on that.
[16:45] <rye> matiasb: the code in lp:~matiasb/ubuntuone-servers/accepting-tos-before-accepting-share - does that mean we'll be able to set up storage for accounts that for some reason don't have one like the lucky ones after the shard went live on 22nd?
[16:48] <matiasb> rye: that code would allow to create the root volume for a user that already have a storage user, taking the info from that storage user; this should allow to fix users without root volume related to the accepting share before TOS bug
[16:58] <mhall119> thanks aquarius, that went well
[16:59] <aquarius> mhall119, cheers, pal!
[17:05] <leo-unglaub> aquarius: according to the ubuntu one session right now. i have implemented a "flat sync" for thunderbird contacts in dropbox. with u1db i think it's very easy to port that to ubuntu one as well. anyting special i should have to keep in mind?
[17:06] <leo-unglaub> flat sync -> means i don't care in witch address book the contact is, i simply sync all of them
[17:19] <rye> matiasb: re: people w/o userstorage (2221970..2222049) - i am filing a bug, right?
[17:29] <matiasb> rye: yes, please
[17:32] <mandel> ok, EOD here, laters!"
[17:32] <gatox> mandel, bye!!
[17:52]  * mmcc is headed for some BBQ
[17:54]  * gatox finally understand the logic behind this method
[17:54] <gatox> now is time to fix it
[18:40] <alecu> gatox: you've left me wondering... which is the method that you've understood the logic?
[18:41] <gatox> alecu, jejeej it was a really silly thing...... but i was lost with the tests
[18:41] <gatox> let me remember
[18:41] <alecu> gatox: no prob :-)
[18:41] <alecu> gatox: don't worry!
[18:42] <gatox> alecu, i don't recall exactly, but was something checking that we are ignoring the proper path, and catching the events from another one....... the test was failing weird so i was a little confuse
[18:42] <gatox> and i'm kind of drained this days :P waiting for pycamp!
[18:42] <gatox> these days
[18:46] <joshuahoover> ralsina: heh, too many channels
[18:46] <Yancho> guys, i am trying to install ubuntuone on xubuntu. however after installing ubuntuone-control-panel-gtk when i go settings > ubuntu one control panel - the application is crashing .. any idea from where to start fixing please?
[18:47] <joshuahoover> ralsina: on the qa call just a minute ago we were discussing windows automated testing...we want to run automated tests against each of the major win platforms, which we don't currently do...there were 2 things that came out of that discussion:
[18:47] <joshuahoover> ralsina: 1) we really need bug #984964 fixed to get testability running on windows
[18:48] <ralsina> joshuahoover: agreed on 1)
[18:49] <joshuahoover> ralsina: 2) we need a basic validation that the install is good (considering bug 1017019)...we can do this but rmcbride mentioned that maybe there is a way to do this kind of validation as part of the installer build process (automated)?
[18:49] <ralsina> joshuahoover: running u1sdtool --help should be enough for that one
[18:50] <ralsina> joshuahoover: in fact, I am in the process of trying progressively older versions on a clean XP VM until I found when it started failing
[18:51] <briancurtin> joshuahoover: to get testability going is going to require once again that we drop everything and figure it out entirely on our own with zero documentation
[18:51] <joshuahoover> briancurtin: that sounds delightful...sigh
[18:52] <ralsina> joshuahoover, briancurtin: in fact, I am not even sure if anyone ever got it working on windows :-/
[18:52] <briancurtin> i know we need to have it, and i want it to work, but its painful and even after however many days i spent on it, even the example Qt project didn't work
[18:52] <joshuahoover> briancurtin: is the issue w/ testability on windows specifically? or testability in general (re: no docs/help)?
[18:52] <briancurtin> ralsina: i've read that people "got it working" but it's all message board posts or mailing list posts where they ask a question, then they just figure it out on their own, then just say "oh it works now"
[18:53] <ralsina> briancurtin: damn them ;-)
[18:53] <joshuahoover> briancurtin: right, i hear you... elopio and rmcbride have looked at various frameworks over the months and they all have significant drawbacks :(
[18:53] <joshuahoover> love that, "oh it works now"...very helpful insight people provide with follow ups like that
[18:53] <ralsina> specially since they have this one working on ubuntu
[18:54] <rmcbride> well, given that the top google result in the last year is https://bugs.launchpad.net/bugs/1008583 ...
[18:54] <rmcbride> I'm guessing having it work isn't common
[18:54] <briancurtin> joshuahoover: the problems i faced were that getting testability built in the first place, but it ends up being pretty easy. then associating it with the Qt install isn't too hard. actually getting it to do anything productive was the part i got stuck on. running the sample Qt calculator app that is supposed to support testability didn't work no matter what i tried
[18:55] <briancurtin> rather, it worked, but all it did was add numbers...it wouldn't associate with the testability visualizer
[18:55] <joshuahoover> heh, right, got ya
[18:57] <gatox> alecu, another one for review: https://code.launchpad.net/~diegosarmentero/ubuntuone-client/darwin4-fsevents/+merge/111914
[18:57] <gatox> this is the last one
[18:58] <joshuahoover> elopio: as much as it pains me, maybe we need to look at alternative frameworks again for automation? or at least start looking at other alternatives for windows? at least something to give us an idea of what some options are - spending time on (possibly) getting testability working on windows, or porting all tests to a different framework that works across windows, mac and ubuntu (in that order)...or maybe there is nothing that me
[19:04] <ralsina> joshuahoover, elopio: lots of people recommend squish but it's quite expensive
[19:04] <rmcbride> apparently LDTP has a windows version
[19:05] <rmcbride> as of April of this year Naggapan got permission from VMware to open source it. FWIW. I haven't done anythign with it
[19:05] <ralsina> briancurtin: can you point me to any notes on what you tried with testability?
[19:06] <ralsina> briancurtin: and/or a tarball of your most successful attempt :-)
[19:06] <briancurtin> ralsina: i don't have any written up, i can write something quick and zip up what's there
[19:06] <ralsina> briancurtin: cool
[19:13] <rmcbride> elopio: joshuahoover: ralsina: FWIW LDTP is not only available for windows now, it's going to be available for Mac "real soon now" https://github.com/nagappan/pyatom/commits/master
[19:13] <joshuahoover> rmcbride: hmmm
[19:14] <rmcbride> I haven't looked at it on Ubuntu in a while, since  we were looking for something cross=platforma nd I assumed it would not be
[19:14] <rmcbride> http://ldtp-soc.blogspot.com/2012/04/announce-windows-version-of-ldtp-gui.html
[19:16] <dobey> does qt work with it yet?
[19:17] <rmcbride> dobey: not at all certain, Jamie gave me a couple links referring to it. I'll ask rather than read
[19:18] <rmcbride> dobey: actually it does
[19:18] <rmcbride> dobey: forgot that was about the second thing he said to me when I asked about cross platform tools
[19:19] <dobey> hmm, ok
[19:20] <czajkowski> kazade: aloha
[19:20] <czajkowski> kazade: aq isnt here atm
[19:20] <kazade> hey czajkowski
[19:20] <kazade> yeah, I'll just hang around :)
[19:21] <kazade> how's things with you?
[19:21] <czajkowski> kazade: good thanks enjoying the tweeting conversation
[19:21] <kazade> :)
[19:23] <czajkowski> kazade: others in here might be able to help in the mean time until aq arrives
[19:24] <kazade> czajkowski: it's OK, I think I got enough info over Twitter for now
[19:24] <kazade> although, saying that, I'm sure I'll be back tomorrow ;)
[19:25] <kazade> czajkowski: it's for this: http://i.imgur.com/tYIhX.png
[19:26] <dobey> oh hi urbanape
[19:26] <czajkowski> kazade: ah
[19:27] <ralsina> briancurtin: I am setting up a new XP dev vm so I can try building the installer there
[19:27] <dobey> hmm
[19:27] <ralsina> briancurtin: I can find anything about the buildout in https://wiki.ubuntu.com/UbuntuOne/Contribute/WindowsTesting am I looking at the wrong page?
[19:27] <briancurtin> ralsina: i have a trunk installer built to run on XP, will do it right after i wrap up this wiki page for testability
[19:28] <ralsina> briancurtin: cool
[19:28] <ralsina> briancurtin: I also want to give testability a whack to see if it falls ;-)
[19:28] <briancurtin> ralsina: https://wiki.canonical.com/UbuntuOne/Windows/ReleaseChecklist contains some buildout-y stuff, installer building
[19:28] <ralsina> briancurtin: awesome thanks
[19:32] <briancurtin> wow this wiki software is garbage
[19:32] <briancurtin> hey heres an enumerated list, just jam it together on one line!
[19:33] <briancurtin> ralsina: here's the loose form documentation for right now: https://wiki.canonical.com/UbuntuOne/WindowsTestability
[19:34] <ralsina> briancurtin: thanks
[19:34] <briancurtin> ralsina: it's probably better that you build them locally rather than me zip things up, but i can do that if you want
[19:34] <ralsina> briancurtin: I'll try
[19:34] <briancurtin> ralsina: building is the easiest part. doing anything with what's built is the kicker
[19:34] <ralsina> he
[19:36] <urbanape> hey, dobey
[19:36] <urbanape> crazy weater.
[19:36] <urbanape> weather even
[19:37] <dobey> yeah, looks like it
[19:37] <dobey> and looks like it will be down here in a couple hours
[19:38] <urbanape> most likely.
[19:38] <urbanape> it's been moving in that direction
[19:39] <mmcc> ralsina, briancurtin: - not sure if it's relevant but when I was working on the PyQt plugin issue I got a lot of mileage out of the QT_DEBUG_PLUGINS=1 env var
[19:40] <mmcc> ralsina, briancurtin also if there's a dynamic loader debug flag along the lines of darwin's DYLD_PRINT_LIBRARIES=1, that was useful too
[19:40] <briancurtin> ralsina: oh, and if you get everything setup, when you start the visualizer, you may here a ding if you have sound turned on, and apparently there's a popup that shows up for like 1 microsecond and goes away. i tried figuring that out last time i worked on it. maybe this env var will help, not sure
[19:40] <ralsina> briancurtin: to build the plugin is VS express enough?
[19:41] <briancurtin> ralsina: all you really need is the VS2008 SDK since you just build on the command line using nmake. Express will include what you need
[19:41] <ralsina> briancurtin: awesome
[19:44] <ralsina> WTF there are no binaries of PyQt available for download!!!!
[19:44] <briancurtin> ralsina: i wish i got as far as even considering python/pyqt in this whole testability debacle...
[19:45] <ralsina> briancurtin: hehe
[19:45] <ralsina> briancurtin: but really, there is no way to install PyQt right now for people who don't have old copies
[19:45] <briancurtin> and whoa, you're right there are no binaries
[19:46] <briancurtin> oh maybe it's because that version is brand new, as in it just came out yesterday
[19:46] <ralsina> yeah, and the previous one had a bad regression
[19:46] <briancurtin> (not that creating windows installers should take this long)
[19:46] <ralsina> briancurtin: we can't say that
[19:47] <elopio> joshuahoover, rmcbride, ralsina: ok. I'll check the options again.
[19:47] <joshuahoover> elopio: thanks
[19:54] <dobey> spoke too soon. clouds are starting to roll in already
[19:58] <briancurtin> ralsina: not that i really thought this would work, but trunk installers also do not work on XP
[20:01] <ralsina> briancurtin: are you building them on 7?
[20:01] <briancurtin> ralsina: yeah i am, i don't currently have a source setup on XP. i could try that, though
[20:02] <ralsina> briancurtin: please try it
[20:02] <briancurtin> also, most everything i've found points to needing vcredist 2008 SP1...which is what ive run and rerun 100 times
[20:02] <briancurtin> ralsina: will do
[20:02] <ralsina> briancurtin: once upon a time, my installers built on 7 did notwork on xp either
[20:02] <briancurtin> ralsina: hahahah. running bzr also gets the same problem
[20:02] <ralsina> briancurtin: of course later they did but whatever :-(
[20:03] <ralsina> briancurtin: I got "invalid binaries" with the 2.6 bzr, I had to get 2.5
[20:03] <briancurtin> ralsina: it's not going to start now because of the CRT issue, even though i installed it. this machine is just hosed i think...
[20:03] <ralsina> briancurtin: oh, well
[20:04] <ralsina> I feel like I am waving a beheaded chicken around
[20:04] <ralsina> and not a delicious, deep-fried beheaded chicken
[20:07] <gatox> people! eod for me!! see you tomorrow! :D
[20:08] <dobey> ralsina: https://code.launchpad.net/~dobey/ubuntuone-storage-protocol/update-4-0/+merge/111929
[20:09] <ralsina> dobey: looking
[20:13] <mmcc> quick style question: anyone have a problem with moving 'from twisted.internet import reactor' in ssoclient's ubuntu_sso/utils/tcpactivation.py from the toplevel into the two methods that use it? It requires some test tweaks to patch twisted.internet instead of tcpactivation, but otherwise works fine (still in progress of testing on linux / win)
[20:14] <mmcc> the reason is that if we import reactor at toplevel, it'll install a default reactor too soon
[20:14] <dobey> yes
[20:14] <dobey> oh, maybe not
[20:14] <dobey> twisted reactors are a fun bunch of insanity regarding imports
[20:14] <mmcc> yeah, importing causes installation - not great
[20:14] <dobey> yeah
[20:15] <dobey> unless you already have a reactor installed
[20:16] <mmcc> yep. but in this case I need to import a bunch of stuff before I install the reactor, so I can creaete the QApplication before I install the qt4reactor, whee
[20:16] <mmcc> (or else qt4reactor will create a QCoreApplication for me, so helpful)
[20:24]  * briancurtin late lunch
[20:26] <dobey> ah right
[20:27] <dobey> mmcc: how many places is it importing reactor where that's an issue?
[20:28]  * popey waves
[20:28]  * popey has installed U1 files on IOS 6 beta
[20:29] <beuno> oh-oh
[20:29] <beuno> run urbanape!  run!
[20:29] <popey> nicely highlighted there beuno :)
[20:29] <popey> when you first start it the window is titled "Root view controller"
[20:30] <beuno> I've seen that in iOS4 as well
[20:30] <ralsina> mmcc: maybe moving it into a function that returns the reactor?
[20:30] <ralsina> mmcc: just to avoid needless duplication
[20:43] <ralsina> dobey: sorry, +1 on that branch, forgot to do it on launchpad
[20:44] <dobey> ok
[20:44] <dobey> ralsina: also have https://code.launchpad.net/~dobey/ubuntuone-client/update-4-0/+merge/111939
[20:45] <dobey> and https://code.launchpad.net/~dobey/ubuntuone-control-panel/update-4-0/+merge/111915
[20:45]  * briancurtin back
[20:50] <dobey> meh
[20:50] <dobey> power keeps blipping here
[21:02] <ralsina> dobey: +1 on the 1st one, the second one I can't check before EOD
[21:02] <dobey> :(
[21:02] <dobey> the last one can't land until the client one is landed/released/inubuntu/etc
[21:02] <ralsina> dobey: maybe mmcc or briancurtin can take a look? It's earlier for them
[21:02] <mmcc> argh, my chat-name notification thingy died or something
[21:03] <dobey> heh
[21:03] <dobey> mmcc, briancurtin: care to give a sanity check to https://code.launchpad.net/~dobey/ubuntuone-client/update-4-0/+merge/111939 ?
[21:03] <mmcc> sure, I can do that
[21:03] <ralsina> There, dev-env setup on windows at last
[21:04] <ralsina> now I can try to do stuff tonight
[21:04] <ralsina> so EOD, will do windows tinkering very late, will report to briancurtin if I find something tomorro
[21:04] <dobey> hrmm, i need to make a branch to fix a couple pep8 errors in protocol also
[21:04] <ralsina> w
[21:04] <mmcc> also - re the reactor import thing - there are only two functions where i had to import it.
[21:04] <mmcc> I like ralsina's idea, but in this case it's less code to just write the import in each function that uses reactor
[21:05] <dobey> mmcc: might be worth refactoring to a function, so that all the qapp/import/reactor.run stuff is in that one spot?
[21:05] <dobey> oh, i guess that's what he suggested
[21:05] <dobey> heh :)
[21:07] <mmcc> dobey: sort of. I think he was just suggesting to replace the import with a function that imports and returns the reactor. although now I'm not sure that makes sense
[21:08] <mmcc> anyway it'd be a much bigger change to put all the app/import/run stuff together, it's spread across several files right now. I assume for test-ability
[21:11] <briancurtin> dobey: checking that branch now
[21:11] <briancurtin> update-4-0
[21:12] <dobey> thanks
[21:20] <dobey> briancurtin: mmcc apparently gave a +1. should i wait for you?
[21:20] <briancurtin> i'll approve in a second, just getting to the end
[21:21] <dobey> ok, cool
[21:21] <briancurtin> dobey: done, approved
[21:21] <dobey> thanks briancurtin
[21:24] <mmcc> sorry, forgot to say anything
[21:25] <mmcc> should I expect pylint on windows to work? I keep forgetting if it's supposed to bleed out and die like this
[21:25] <briancurtin> mmcc: it works for me
[21:26] <mmcc> hmm
[21:30] <mmcc> well, I'll make a note. just in case you have a sec and this looks familiar: http://paste.ubuntu.com/1059797/
[21:30] <mmcc> but don't spend time on it...
[21:31] <briancurtin> mmcc: i see that part too and i just ignore it. after that you would still see regular lint warnings if there are any
[21:31] <briancurtin> which is why i never bothered looking into that traceback
[21:32] <mmcc> briancurtin: oh, heh, ok. thanks :)
[21:33] <mmcc> dobey, do you have cliffs notes for setting bugs to project/distribution/series ? my reactor change is in sso...
[21:34] <mmcc> hm, that wasn't a clear sentence. I'm sure you get what I meant. I want to know how to set all the bits on the bug correctly.
[21:35] <dobey> i don't. i still haven't gotten that e-mail written up :-/
[21:36] <dobey> and as soon as this u1client branch lands (or fails to do so), i am heading away from the computer
[21:36] <mmcc> ok np, I'll just make a note to fix it later.
[21:43] <mmcc> if anyone wants a short review, I'll just leave this here: https://code.launchpad.net/~mikemc/ubuntu-sso-client/fix-1017672-delayed-reaction-in-tcpactivation/+merge/111945
[21:47] <briancurtin> mmcc: approved, i saw the discussion earlier, makes sense
[21:47] <dobey> ok, i'm off. have a god evening guys
[21:47] <briancurtin> you too
[21:50] <mmcc> thanks briancurtin.
[21:51] <mmcc> bye dobey.


[17:30] <TheLordOfTime> oops sorry
[17:33] <TheLordOfTime> sorry if my bot was reporting stuff here, the Encyclopedia plugin iconfig script is broken and breaks one of the options for "factoid edit notifier channel"