[00:27] <balloons> not you forestpiskie, just elfy
[00:28] <elfy> I saw that too :p
[06:30] <jibel> Good morning
[07:40] <DanChapman> good morning
[07:40] <elfy> morning DanChapman
[07:41] <DanChapman> hey there elfy :-)
[10:03] <elfy> ubuntu-bug is fighting me and unfortunately winning - won't let me report something
[10:08] <jpds> Are you experiencing a bug while running ubuntu-bug?
[10:09] <slickymaster> good morning all
[10:10] <DanChapman> morning slickymaster o/
[10:10] <elfy> jpds: it refuses to do anything - it refuses to do anything even if I try and manually push the crash report
[10:11] <slickymaster> morning DanChapman
[10:11] <elfy> jpds: but - time is my enemy just now - back later to read backlog if you can think of anything :)
[10:59] <davmor2> Morning all
[13:56] <elopio> good morning.
[15:44] <balloons> elfy, congrats
[15:45] <elfy> thanks balloons :)
[15:45] <DanChapman> balloons, what are we congratulating elfy on?
[15:45] <elfy> I rid myself of forestpiskie :p
[15:46] <elfy> DanChapman: I got voted onto the Community Council for my sins :)
[15:46] <DanChapman> lol. Oh awesome! congratulations! \o/
[15:47] <knome> something fishy going on there
[15:47] <elfy> I'm English, not schooled at Eton so tend to not blow my own trumpet and didn't say anything :)
[15:47] <knome> are you sure the polling website is fine?
[15:47] <elfy> apprently not knome
[15:47] <knome> yeah
[15:47] <knome> :/
[15:47] <knome> have to avoid that in the future
[15:47] <knome> otherwise it'll raffles you as the xubuntu project lead next
[15:48] <balloons> yes, apparently the last minute campaigning worked :-p
[15:48] <elfy> no it won't knome ;)
[15:48] <balloons> seriously tho, congrats..
[15:48] <elfy> thanks :)
[15:48] <knome> i'm serious! who the heck voted for him!
[15:48] <knome> wait, i did
[15:48] <knome> :|
[15:48] <elfy> :)
[15:48] <knome> my bad!
[15:48]  * elfy had a block vote too
[15:49]  * balloons says he did too
[15:49] <elfy> reminiscent of trade unions
[15:49] <knome> balloons, you just "say", but didn't?
[15:49]  * elfy voted for everyone on the list
[15:49] <knome> me too, just *down*voted some
[15:49] <knome> har har
[15:49] <knome> :P
[15:49] <balloons> yep.. I voted for everyone
[15:49] <knome> you kind of have to do that with the CIVS
[15:49] <balloons> not everyone I voted for made it tho
[15:50] <knome> balloons, of course not if you voted for everyone :P
[15:50] <elfy> knome: well you kind of do - but you could mark one as 1 and the others as last
[15:50] <elfy> which is kind of silly
[15:50] <knome> elfy, which is the same as marking them one 1 and rest 2
[15:50] <elfy> I guess
[15:50] <knome> elfy, which is really close to just voting for one person regularly
[15:51] <knome> it is, because CIVS is about preference
[15:51] <knome> it doesn't matter if it's 1/2 or 12/13
[15:51] <knome> you still prefer the guy in 1/12
[15:51] <knome> or gal
[15:51] <elfy> confuses me - so I sorted everyone out :)
[15:51] <knome> hehe
[15:51] <knome> well that's fair as well
[15:51] <balloons> I put 1 through 12 in
[15:51] <balloons> yes, I like the system
[15:51] <knome> if you can make a difference, you probably should
[15:52] <knome> i couldn't on a few occasions
[15:56] <balloons> elfy, btw now I get to refer to you in fun ways; https://plus.google.com/104307250302998042813/posts/G8dqRSJamwL
[15:56] <elfy> :)
[16:29] <DanChapman> balloons, I'm just going through all the ubuntu-autopilot-tests creating a list of todo's, So first they are all going to need porting to 1.4 but what is the choice on python version are we wanting to port them to py3 at the same time. Not much really needs changing for that, so my question is rather which py version are we to suggest writing tests with going forward?
[16:29] <balloons> python3 :-) Starting with 1.4 we should look to python3
[16:30] <balloons> that said, I've not converted any tests just yet
[16:30] <balloons> they have to be run with the py3 runner as well
[16:31] <balloons> I would say something to keep in mind.. as of now I don't know of concrete plans to rid all py2 tests this cycle
[16:31] <balloons> https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1249235
[16:36] <DanChapman> balloons, ok cool, well if we are going to look to py3 for ap-1.4 for new tests then really the current ones will need to be ported at some point, so we don't have a mixture of py2/3 in ubuntu-ap-tests.
[16:36] <balloons> DanChapman, I would look to port them all at once I think.. the py2 -> py3 work is simple enough
[16:37] <DanChapman> balloons, thats what i was thinking
[16:37] <DanChapman> :-)
[16:37] <balloons> still, let's note it's something to be done :-)
[16:37] <balloons> not completely trivial
[17:16] <cgoldberg> balloons.. porting to Py3 is usually simple (a cutover).... but using a single code base that runs under Py2 *and* Py3 is not always simple
[17:16] <cgoldberg> so if it all possible... drop Py2
[17:17] <balloons> I tried to do the dual py2 and pt3 thing once
[17:17] <cgoldberg> balloons, it usually the best upgrade path.. but it's tricker
[17:17] <cgoldberg> trickier even
[17:22] <balloons> it worked for a little bit, but it was annoying. you would break one or the other quite often
[20:04] <Letozaf_> balloons, buonasera
[20:04] <balloons> Letozaf_, buonasera
[20:05] <Letozaf_> balloons, howzit ?
[20:06] <balloons> Letozaf_, good.. just looking at rssreader actually
[20:07] <Letozaf_> balloons, oh thanks, was about to ask you about it
[20:07] <balloons> the wait_until_destroyed isn't doing it as-is, but now I'm hitting other things
[20:07] <balloons> wait.select_single should be wait_select_single
[20:07] <balloons> :-)
[20:08] <Letozaf_> balloons, where, let me check...
[20:08] <balloons> in emulators
[20:08] <Letozaf_> balloons, found it :(
[20:09] <Letozaf_> balloons, I will re-run the tests
[20:10] <balloons> trying to use the wait_until_destroyed
[20:15] <Letozaf_> balloons, I keep on getting that IndexError: list index out of range for ActionSelectionPopover
[20:15] <balloons> I'm not getting that at all
[20:15] <Letozaf_> balloons, are you running the tests on the Desktop or the device ?
[20:16] <balloons> desktop for now.. I'm trying to get the activity indicator check to work
[20:16] <balloons> it doesn't for me atm
[20:18] <Letozaf_> balloons, see this drives me mad, now I had no failures, and I didn't change the code, just re-ran the test
[20:19] <Letozaf_> balloons, I'm also running them on the dekstop
[20:19] <balloons> Letozaf_, yes it simply means we need some more asserts
[20:19] <balloons> the tests don't run reliably
[20:20] <balloons> well, lol, it might not be asserts we need, I simplify too much
[20:20] <balloons> but yes, we need them to run reliably
[20:22] <Letozaf_> balloons, ok, let me see if I can fix something...
[20:24] <balloons> hmm
[20:25] <balloons> I really want this activity indicator check to work
[20:25] <balloons> we could use it several spots
[20:34] <Letozaf_> balloons, it's hard to write something on ActivityIndicator as it disappears and cannot see it in vis
[20:35] <Letozaf_> balloons, I can only see the running property form the QML
[20:35] <balloons> right
[20:35] <balloons> you can do it in vis, but
[20:41] <balloons> hmm.. got something I like
[20:41] <Letozaf_> balloons, what ?
[20:43] <balloons> I'll push if it works
[20:43] <Letozaf_> balloons, ok
[20:52] <balloons> sweetness
[20:52] <Letozaf_> balloons, for what ?
[20:53] <balloons> bzr merge lp:~nskaggs/ubuntu-rssreader-app/add-activity-indicator-check
[20:54] <balloons> Letozaf_, I added a _wait_for_refresh function, and tweaked the check for the activity indicators
[20:54] <balloons> seems to work
[20:54] <balloons> full test checks now, then on the phone
[20:55] <Letozaf_> balloons, let me try :)
[20:56] <balloons> Letozaf_,  what is the Not(Is([]))?
[20:57] <Letozaf_> balloons, I copied it from somewhere, do not remember where, wanted to avoid a Not(Is(None)) I think
[20:58] <Letozaf_> balloons, is that bad ?
[20:58] <balloons> Letozaf_, just different, hah..
[20:58] <balloons> I'm open to why you didn't want to use a Not(Is(None)). but anyways we can probably add wait_select_single's in there instead and drop them all
[21:00] <balloons> so it worked, save for test_view_feed failed because the editFeed was null
[21:01] <balloons> probably just a timing thing.. so I think we can clean those up and hopefully be set
[21:02] <Letozaf_> balloons, just ran the test now and saw the failure
[21:05] <Letozaf_> balloons, weired now it worked fine all 3 tests
[21:10] <balloons> Letozaf_, that's not weird.. it's a timing issue, which sometimes occurs and sometimes doesn't
[21:10] <balloons> we need to squelch them all so it will run reliably
[21:11] <Letozaf_> balloons, yes ok got it, I will run the test again an again to veryfy it does not happen, if it does fix the timing issue
[21:12] <balloons> Letozaf_, yep.. but basically just go cleanup anything like this: self.assertThat(editFeed, Not(Is([])))
[21:13] <Letozaf_> balloons, yea already done that
[21:26] <balloons> Letozaf_, alrighty :-)
[21:35] <Letozaf_> balloons, nope I have two issues now,
[21:35] <Letozaf_> balloons, CanonicalTopic is not removed
[21:37] <Letozaf_> balloons, and I have a    raise MismatchError(matchee, matcher, mismatch, verbose)
[21:37] <Letozaf_> MismatchError: None matches Is(None)
[21:37] <Letozaf_> balloons, if I put self.assertThat(editFeed, Not(Is(None)))
[21:40] <Letozaf_> balloons, I get failure using Not(Is(None)) instead of Not(Is([])) but do not understand why
[21:40] <Letozaf_> balloons, MismatchError: After 10.0 seconds test failed: <testtools.matchers._higherorder.Not object at 0x2f38bd0> != [
[21:42] <balloons> Letozaf_, ohh I would do it differently.. let me see
[21:46] <balloons> Letozaf_, I'm changing get_feed_in_feedlist to always return something
[21:46] <balloons> and eliminate the check
[21:48] <Letozaf_> balloons, so you will check that the feed is different form the one deleted ?
[21:48] <balloons> hmm.. actually not so easy
[21:48] <balloons> I think i will use the not is none
[21:52] <balloons> I'm confused by this test now
[21:52] <balloons> #click on list view toolbar button
[21:52] <balloons>         toolbar.click_button("changemodebutton")
[21:52] <Letozaf_> balloons, it's to change from shorts view to list view
[21:54] <balloons> ok, but I'm confused what you are trying to do in that test
[21:54] <Letozaf_> balloons, well I think you don't have to do it, I just chose to do it
[21:54] <Letozaf_> balloons, I think the test works all the same if you remove that
[21:55] <Letozaf_> balloons, it was just for changing view type
[21:55] <balloons> Letozaf_, :-) What are you trying to do with the selecting a feed? you never make it to the edittopic tab
[21:55] <balloons> it's just really confusing
[21:56] <Letozaf_> balloons, I was changing from the shorts view to the list view of the topics
[21:57] <balloons> What I'm trying to say is what does "test_view_feeds" test?
[21:57] <Letozaf_> balloons, it's  a way to check that it works
[21:57] <balloons> do we just want to make sure we can change the view?
[21:57] <balloons> if so, we can radically simplify this testcase
[21:57] <Letozaf_> balloons, oh, it just tests that you open the feed to read it
[21:57] <Letozaf_> balloons, I both test it opens a feed and changes view mode
[21:58] <Letozaf_> balloons, maybe the test name should be changed
[21:58] <balloons> yea, we could be more desciptive
[21:58] <balloons> ok, so test switching the view
[21:58] <balloons> then open a feed and view an article?
[21:58] <Letozaf_> balloons, yes
[21:58] <balloons> wow, ok.. good test, but I don't see where this test does that, hah
[22:01] <Letozaf_> balloons, for this : https://bugs.launchpad.net/ubuntu-rssreader-app/+bug/1188713
[22:01] <balloons> Letozaf_, k. So, do we need to add a topic and feed first? there are default feeds
[22:01] <balloons> I'd guess we can use one of those
[22:02] <balloons> that will simplify things
[22:02] <Letozaf_> balloons, I used the canonical ones as in the beginning there weren't only canonical and ubuntu ones
[22:02] <Letozaf_> balloons, but also other ones
[22:02] <Letozaf_> balloons, then they changed
[22:03] <Letozaf_> balloons, so on every test I added the canonical feed to test on those
[22:05] <Letozaf_> balloons, in other words I wanted to test the same feed on every test and so used the canonical one everywhere
[22:06] <Letozaf_> balloons, added it at the beginning and tested on that one and then removed it at the end
[22:07] <balloons> hmm
[22:07] <balloons> ok, fair enough. I'll playing around with it
[22:09] <Letozaf_> balloons, it's late for me now, I will be back tomorrow. let me know what you decide
[22:10] <Letozaf_> balloons, going to bed
[22:10] <Letozaf_> balloons, good night
[22:10] <balloons> Letozaf_, ciao.
[22:10] <balloons> thanks for your help
[22:10] <Letozaf_> balloons, ciao
[22:10] <Letozaf_> balloons, yw


[06:00] <OvenWerks> Eickmeyer: was just wondering if you had repacked mcpdisp so I can test it. before releasing it. (built from latest git)
[06:00] <OvenWerks> The big change is making it -o0 :)
[06:01] <OvenWerks> The rest is spelling kinds of things.
[06:01] <Eickmeyer> OvenWerks: I packaged it, but the version I have is kinda not working, and I haven't rebuilt it since. Do you have a new release?
[06:02] <OvenWerks> I want to make sure it works when packaged before I mark a release
[06:03] <Eickmeyer> Ok, I'll see if I can do a git pull and push that in, but I probably won't get to it until tomorow.
[06:03] <OvenWerks> no problem
[06:07] <OvenWerks> the problem was getting it to build while packaging... worked fine otherwise
[06:19] <Eickmeyer> Right. That's why I did it via my PPA before.
[06:22] <OvenWerks> evrything is 0.1.2 except the tag.
[06:36] <Eickmeyer> Ok. I'll do it in the morning. Headed to bed now.
[06:50] <OvenWerks> gn
[17:21] <Eickmeyer> OvenWerks: Here's my build of mcpdsp: https://launchpad.net/~eeickmeyer/+archive/ubuntu/ppa/+build/19533996/+files/mcpdisp_0.1.1+git20200621-0ubuntu1_amd64.deb
[17:21] <Eickmeyer> Give it a whirl.
[18:56] <OvenWerks> Thankyou lets see if I can do this by remote :P
[19:02] <OvenWerks> Eickmeyer: that looks old
[19:02] <OvenWerks> Say june 21
[19:04] <OvenWerks> ok build log looks right though
[19:09] <OvenWerks> Ok, that loads and runs
[19:09] <OvenWerks> so setting -O0 worked
[19:11] <OvenWerks> That probably means in the long run I need to explicitly manage memory differently because something in -O1 is trying to put all my buffers (well some the ring buffer will be right) on the stack
[19:14] <OvenWerks> firefox seems to explicity open nauty-lis instead of the DE default file manager. There are so many things one cannot do with naughty-lis that Thunar can do... like open remote locations (at least it is hard to find)
[19:15] <OvenWerks> one more test to do.
[19:19] <OvenWerks> Ok, it does actually display the info when hooked up to Ardour :)
[19:21] <OvenWerks> Eickmeyer: So if I tag it as a 0.1.2 release will that work for packaging? is there anything else I need to do?
[19:22]  * OvenWerks hates "naughty loss of functionality"
[19:31] <OvenWerks> Looks pretty good: https://i.imgur.com/KenRrmX.png
[19:33] <OvenWerks> somethings not right -V still shows 0.1.0
[20:27] <Eickmeyer> OvenWerks: If you tag for 0.1.2, it has very little impact on packaging except the version number that gets submitted at this point.
[20:28] <Eickmeyer> And if -V is wrong, it's a good thing you *haven't* done that. :D
[20:31] <OvenWerks> except the -V, -h show the right version on a self build
[20:39] <OvenWerks> also looking at the build log: Project version: 0.1.2 and: -DVERSION="0.1.2"... let me try downloading the file again.
[20:50] <OvenWerks> Eickmeyer: I do not know how the Version 0.1.0 ends up in the package. The build log shows 0.1.2, the build from the same package shows right version here.
[20:51] <OvenWerks> The file name for the resulting package does not look like today however.
[22:07] <Eickmeyer> OvenWerks: So, the version number I used is 0.1.1+git20200621: the date of the commit.
[22:07] <OvenWerks> right.
[22:07] <Eickmeyer> That's all I saw. I didn't see any newer commits.
[22:07] <OvenWerks> Eickmeyer: I did remove the Makefile which should not be needed/used
[22:08] <Eickmeyer> Yes, if it's a meson build. Debhelper is smart enough to figure out how to build with what the package build deps are.
[22:09] <OvenWerks> the makefile was left over from before meson, I thought I had removed it already.
[22:09] <Eickmeyer> It probably wasn't being used anyhow.
[22:10] <OvenWerks> doing a grep 0.1.0 * shows nothing.
[22:10] <Eickmeyer> Weird.
[22:11] <OvenWerks> so anyway, I am going to tag a release (bug fix)
[22:11] <Eickmeyer> Ok
[22:11] <OvenWerks> The main thing is that it runs
[22:11] <OvenWerks> maybe I would be better calling it 0.2.0?
[22:12] <OvenWerks> but really it is a bugfix for 0.1.0
[22:13] <OvenWerks> so 0.1.2 is correct
[22:22] <OvenWerks> Eickmeyer: here it is: https://github.com/ovenwerks/mcpdisp/releases/tag/mcpdisp-0.1.2
[22:23] <Eickmeyer> OvenWerks: Ok.
[22:49] <Eickmeyer> OvenWerks: So, I'm trying to test it, but I'm in a pickle: I can't get studio controls to start Jack.
[22:53] <OvenWerks> Latest from cit?
[22:53] <OvenWerks> git
[22:53] <Eickmeyer> Yep.
[22:53] <OvenWerks> yes
[22:54] <OvenWerks> known problem
[22:54] <Eickmeyer> Oh?
[22:54] <OvenWerks> fixed here already
[22:54] <OvenWerks> git was not ready for use, but needed to be made so I could have a full install
[22:55] <OvenWerks> (on 18.04
[22:55] <Eickmeyer> Oh, I see. Yeah, I yeeted it into Groovy. My bad.
[22:56] <OvenWerks> I can push to working (still not ready)
[22:56] <Eickmeyer> Of course. "1.99.x" implies not ready until 2.0.
[22:57] <Eickmeyer> Not much of a matter anyhow. I used qjackctl to test.
[23:54] <OvenWerks> found out why -V might be 0.1.0... it seems there is an old copy in /usr/local/bin
[23:56] <OvenWerks> when I run the one in /usr/bin/ everything works
[23:58] <OvenWerks> fixed