[06:25] <OvenWerks> Eickmeyer[m]: hows your python :) it appears dict == dict only works so far, should I add python3-deepdiff as a depends or create a call that does much nthe same thing?
[06:31] <OvenWerks> I think I will add deepdiff, I expect it has had some optimization. I think I would end up doing two for loops looking to see if the second dict contains each part, then sub part and then go back and exchange the two and start over.
[06:32] <OvenWerks> shouold be two sets of for loops because nesting.
[12:30] <wonko> Don't reinvent the wheel. :)
[12:32] <strogon14_> OvenWerks: not sure about the context , but what about stdlib deepcopy?
[14:48] <OvenWerks> strogon14_: turns out that wasn't the problem
[14:48] <Eickmeyer> OvenWerks: My python is only as good as to work on Plasma scripts, and requires a LOT of help, so not that great. :)
[14:49] <OvenWerks> it's ok, turns out dict == dict was doing the job
[14:49] <Eickmeyer> Perfect.
[14:50] <strogon14_> oh, sorry, I didn't read properly. I thought this was about copying a dict, not comparing two. nvm.
[14:54] <OvenWerks> strogon14_: I actually do use deepcopy elsewhere.
[16:05] <OvenWerks> Eickmeyer: do I need to add a bug report to controls before you can package for 21.04?
[16:18] <OvenWerks> Eickmeyer: new controls
[17:07] <Eickmeyer[m]> OvenWerks: Nope, it's just a bug fix.
[17:07] <Eickmeyer[m]> Minor at that.
[17:08] <Eickmeyer[m]> If it were beta freeze, sure, but this is only feature freeze.
[17:08] <Eickmeyer[m]> strogon14_: How's jack_mixer looking?
[17:11] <strogon14_> just writing the changelog
[17:11] <strogon14_> expect it to be released this evening
[17:13] <Eickmeyer[m]> strogon14_: This evening? Trying to beat feature freeze here. Feature freeze should also be this evening.
[17:13] <strogon14_> didn't you say friday?
[17:13] <Eickmeyer[m]> Nope, Thursday the 25th. Everything Ubuntu happens on a Thursday typically.
[17:14] <strogon14_> anyway, +1 hour or so
[17:14] <Eickmeyer[m]> Ok. :)
[17:59] <strogon14_> https://github.com/jack-mixer/jack_mixer/releases/tag/release-15
[18:03] <Eickmeyer[m]> strogon14_ I just got the email notification. :)
[18:15] <wonko> OvenWerks: So, 5.11 is definitely better than 5.10 but my xruns came back overnight. I think I understand why though. I did a find today and immediately got crackling in the audio. Looked and sure enough it was racking up xruns. Disk access really kills it. Probably cron stuff running over night doing disk related activites.
[18:15] <wonko> I look forward to testing 5.10/5.11 lowlatency in 21.04 instead of using the liquorix kernel
[18:16] <OvenWerks> Yeah, turning cron off makes a difference
[18:16] <wonko> also, I don't know how well (if at all) rtirq is working under liquorix
[18:17] <wonko> the output of rtirq status is.... weird looking.
[18:17] <wonko> https://paste.ubuntu.com/p/N88YHFffxv/
[18:17] <wonko> so I could possibly see major improvements with a 5.11-lowlatency
[18:18] <OvenWerks> I think that even though cron runs at nice = 10, There are some disk and net accesses that are atomic
[18:19] <OvenWerks> Huh, the priorities are not set. If you run sudo /etc/init.d/rtirq restart, does that fix it?
[18:19] <OvenWerks> (maybe a timing thing)
[18:20] <wonko> nope, that's just how they look under liquorix
[18:20] <wonko> but, it's not the ubuntu kernel so don't put too much energy into figuring it out. :)
[18:21] <OvenWerks> yeah, obviously it is not built with the right params
[18:22] <wonko> I don't know how (or care) to tweak it, so whatever. :)
[18:22] <OvenWerks> There _may_ be a kernel commandline switch that fixes it
[18:22] <wonko> I'd rather chase down the status of a 5.11-lowlatency kernel
[18:22] <OvenWerks>  :)
[18:22] <OvenWerks> (Thanks)
[18:23] <wonko> so, do we have one? Will we? How is one built if it doesn't exist?
[18:25] <wonko> I'm installing the latest hirsute daily now and will try to answer some of my own questions. :)
[18:41] <wonko> Ok, no 5.11 in apt
[18:56] <Eickmeyer[m]> wonko: I'm pretty sure that we're not going to see a 5.11 in Hirsute. Probably for II (21.10) we'll see 5.12 or so.
[18:56] <wonko> Maybe if not the default kernel how about like you can install 5.8 on 20.04? Is that a thing we could see?
[18:56] <Eickmeyer[m]> https://launchpad.net/ubuntu/+source/linux
[18:57] <Eickmeyer[m]> It's in 20.04.2 by default. If not, the HWE suite is what's needed.
[18:57] <Eickmeyer[m]> !hwe
[18:58] <Eickmeyer[m]> They don't do that for non-LTS.
[18:59] <wonko> that's for LTS though, which 21.04 won't be
[19:00] <wonko> Right, so if I wanted to test 5.11-lowlatency on 21.04 how would I go about doing that (when the time comes)
[19:01] <Eickmeyer[m]> There's no real method for doing that. Probably just testing 21.10 is the way to go in that case.
[19:01] <wonko> Hmmm, that's certainly less than convenient. :)
[19:02] <Eickmeyer[m]> Well, that's the way Ubuntu releases work.
[19:02] <wonko> Yeah, I'll probably just be happy with 5.10 then wait for 21.10
[19:02] <wonko> it's not *super* important
[19:03] <wonko> just a curiosity
[19:03] <Eickmeyer[m]> Gotcha.
[19:07] <wonko> I'm mostly just curious if rtirq on 5.11-lowlatency would solve the disk related xruns I'm seeing on 5.11-liquorix.
[19:07] <wonko> but that testing can wait half a year. :)
[19:07] <wonko> I'm kinda super busy these days with work and the move anyway
[19:09] <Eickmeyer[m]> There's an open bug for new rtirq: https://bugs.launchpad.net/ubuntu/+source/rtirq/+bug/1914110
[19:09] <Eickmeyer[m]> I just haven't had time to update it.
[19:09] <Eickmeyer[m]> I'd rather the Debian maintainers do it, but they're in a freeze now.
[19:10] <OvenWerks> Eickmeyer[m]: update to systemd?
[19:10] <Eickmeyer[m]> OvenWerks: No, just rtirq. I don't know about systemd.
[19:11] <Eickmeyer[m]> Why?
[19:11] <OvenWerks> the main thing with rtirq is that I think it is still /etc/init.d
[19:24] <Eickmeyer[m]> systemd still recognizes things in there.
[19:27]  * OvenWerks is trying to think what else might be upgraded...
[19:30] <Eickmeyer[m]> OvenWerks: Looking at the source, it seems as though he's got systemd .service files, but I don't know where he's developing it.
[22:27] <wonko> he's got the latest version in a PPA if that's at all helpful?
[22:29] <wonko> I mean, it's just a script
[22:29] <wonko> we could easily see if anything actually changed or not with it
[23:21] <Eickmeyer[m]> wonko: I was looking at it, and in order to test it and make sure it's actually working with systemd, can build properly and without lintian issues, then sure. Unfortunately, since it has new features (systemd scripts qualify) there's just no time since today is feature freeze.