[00:37] <thomi> balloons: still around?
[07:01] <jibel> Good morning
[07:03] <elfy> morning jibel
[07:04] <jibel> morning elfy
[08:20] <DanChapman> morning all
[08:25] <smartboyhw> Hello DanChapman
[09:21] <slickymaster> morning all
[09:21] <DanChapman> morning slickymaster
[09:21] <slickymaster> hi DanChapman
[09:31] <rvr> Good morning
[11:52] <elfy> afternoon people
[11:53] <knome> hello elfy
[11:53] <elfy> hi knome
[12:14] <slickymaster> hi elfy
[12:14] <slickymaster> knome: :)
[12:16] <slickymaster> elfy: can you tell me please when is going to be the meeting you mentioned on the xubuntu-devel mailing list, last 17th
[12:17] <elfy> slickymaster: my qa update mail?
[12:17] <elfy> that meeting was the same day as my mail - I left it as late as possible to be as up to date as I could be
[12:18] <slickymaster> elfy: my bad, i've misread your mail
[12:18] <elfy> slickymaster: logs not posted yet - but you can read them if you want at http://irclogs.ubuntu.com/2013/09/17/%23xubuntu-devel.html#t15:02
[12:19] <elfy> there was talk of another yesterday - but that didn't happen
[12:20] <slickymaster> elfy: thanks, you're always helpful
[12:20] <slickymaster> I'll get up to date with those logs
[12:20] <elfy> not everyone would say that :)
[12:21]  * slickymaster thinks that everyone would be completely wrong if they see it otherwise 
[12:26] <elfy> balloons: am I right in assuming that there won't be a mail from -release about Final Beta participation, assumption being everyone will?
[12:26] <elfy> slickymaster: next time I get a PM that doesn't say that - I'll show you a copy :D
[12:27] <smartboyhw> elfy, technically, it is everyone "must":P (But not sure of Touch)
[12:28] <elfy> :)
[12:28] <slickymaster> elfy: well, here in Portugal we have an old saying that roughly translated goes like donkey voices do not reach the sky
[12:29] <elfy> I can understand the meaning behind that :)
[12:29] <elfy> I'm just glad the forum has a language filter lol
[12:30]  * slickymaster agrees
[12:30] <elfy> time for lunch I think
[12:31] <slickymaster> yeah, same over her
[12:32] <slickymaster> good lunch everybody
[12:35] <pitti> Good morning
[12:35] <DanChapman> morning pitti
[12:36] <pitti> hey DanChapman
[12:37] <smartboyhw> elfy, slickymaster I just finished dinner:P
[12:37] <davmor2> morning pitti
[12:38] <elfy> hi smartboyhw
[12:38] <smartboyhw> elfy, you are hi-ing me again?
[12:38] <smartboyhw> -.-
[12:38]  * smartboyhw thought we just talked about the Beta 2 stuff
[12:38] <elfy> wut?
 elfy, technically, it is everyone "must":P (But not sure of Touch)
 :)
[12:39] <smartboyhw> (That's after I finished dinner:P)
[12:39] <elfy> oh ...
[12:39] <elfy> didn't read the name - thought that was slickymaster lol
[12:39] <smartboyhw> elfy, ha ha
[12:40] <elfy> and it sort of made sense in that context too
[12:40] <elfy> well I've not seen anything that says everyone must
[12:41] <elfy> and why you're answering someone else's question I've no idea ;)
[12:42]  * smartboyhw finds "must" double-quoted:)
[12:47] <thomi> morning
[13:04] <balloons> elfy, yes I woul dsay you are correct. Final beta is everyone :-)
[13:04] <elfy> thanks balloons
[13:04] <pitti> thomi: calling the phone, I think that might currently be easiest with umockdev, so that we can test through the real ofonod stack
[13:05] <pitti> thomi: /usr/share/doc/umockdev/README.rst.gz explains how to do that
[13:05] <pitti> thomi: eventually I think we should create an ofonod mock with dbusmock, which is more flexible; but that doesn't exist yet
[13:05] <pitti> thomi: if that's a blocker, I can work on that
[13:16] <thomi> pitti: would I need a sim card in the phone in order to use that?
[13:16] <thomi> pitti: also, perhaps we should integrate this with autopilot
[13:16] <thomi> somehow...
[13:42] <pitti> thomi: you need a SIM card to do the recording; for replay you don't even need Android or a phone
[13:42] <pitti> thomi: I'm still in the US, so I can't do a proper record here; can do one next week, or anyone else produces one; umockdev is in the archive and the steps are documented
[13:43] <balloons> DanChapman, going to do a review of autopilot-gtk before the day sweeps me away
[13:43] <thomi> pitti: so, when you replay it, I guess you're forced to replay *exactly* the same thing, right?
[13:44] <pitti> thomi: yes, i. e. dial the same number
[13:44] <thomi> pitti: so, for example, you'd want 1 recording of a call where the remote end hung up, one recording where you answered etc. etc.
[13:44] <pitti> thomi: of course you can have/load different records for different scenarios
[13:44] <thomi> right, so there's not a lot of flexibility about controlling that programmatically
[13:44] <pitti> thomi: but I'm not even sure that we actually have that much control over that; rild abstracts a lot of that away
[13:45] <pitti> thomi: as I said, for more flexibility, and if we are only concerned about UI testing, it would be better to mock ofonod
[13:45] <thomi> I mean, how would that work in the scenario where I want to answer an incoming call? I push the "answer call" button, and the recording has to start replaying different events?
[13:45] <thomi> ok
[13:45] <thomi> that might be something to talk about
[13:45] <pitti> that's harder to do, but you can then easily test corner cases
[13:46] <pitti> thomi: you'd still umockdev-record ofonod, so in that case on replay ofonod would get the same answer back from rild and then emit its own dbus signals (I guess, I didn't try that case)
[14:07] <elopio> good morning friends.
[14:08] <cgoldberg> elopio, hola amigo
[14:08] <elopio> cgoldberg: hola compadre.
[14:10] <cgoldberg> thomi, found an AP bug that's causing the CI failure on my branch... question:  if I have a CI failure, and now I push a fix, will Jenkins automagically  re-run it, or do I have to trigger something after I push?
[14:19] <elopio> cgoldberg: it will rerun it. But is faster if you go to the retrigger URL left on the bottom of the comment.
[14:20] <cgoldberg> elopio, i saw that, but the url it gives doesn't resolve.. do I need to be on VPN or something? (it points to s-jenkins:8080)
[14:23] <elopio> cgoldberg: yes, QA vpn.
[14:28] <elopio> cgoldberg: my hard drive is dying, so I'm getting an SSD
[14:29] <elopio> what would you recommend? Samsung, intel, kingston?
[14:31] <thomi> cgoldberg: s-jenkins is a dumb alias for 10.97.2.10
[14:33] <pitti> thomi: re-thinking your "obsolete package" problem: it sounds a bit weird why apt would know about newer versions of individual packages in the first place
[14:34] <pitti> thomi: it seems we still run the daily apt-get update cronjobs on phones although we don't even support apt-get there?
[14:37] <cgoldberg> elopio, i usually get whats on sale :)  but I've had good luck with samsung, crucial, and samsung
[14:38] <cgoldberg> samsung, crucial, and Intel rather
[14:39] <cgoldberg> elopio, what size SSD are you looking for?
[14:39] <elopio> cgoldberg: a cheap one. 120GB sounds fine.
[14:40] <cgoldberg> elopio, and most importantly.. do you have SATA3 in your machine?  if not, you can prob save a few bucks and get a SATA2 drive
[14:42] <cgoldberg> elopio, I'm using this one now in my main machine:  http://www.amazon.com/Samsung-MZ-7PD128BW-SATAIII-Solid-State/dp/B009LI7CKI/
[14:42] <cgoldberg> samsung 840 Pro (128 gb)
[14:42] <cgoldberg> it's super fast and have had no probs
[14:43] <elopio> cgoldberg: I have sata3
[14:44] <cgoldberg> elopio, there is a newer version of mine.  this one looks really good and the price is right:  http://www.amazon.com/Samsung-Electronics-EVO-Series-2-5-Inch-MZ-7TE120BW/dp/B00E3W15P0
[14:45] <elopio> cgoldberg: that's the one I was looking at. $100 sounds perfect.
[15:01] <DanChapman> balloons: awesome thanks :-)
[15:25] <balloons> DanChapman, it's weird though I get errors running the tests
[15:25] <DanChapman> balloons: what errors?
[15:25] <balloons> DanChapman, 7 errors to be exact I'll have to go back and look quickly, but I assume it's error free for you
[15:25] <balloons> you use the sandbox?
[15:25] <DanChapman> no i havn't tried it yet
[15:26] <DanChapman> Yeah it runs sweet for me.
[15:29] <thomi> someone remind me: what's the magic invocation to get the current build number?
[15:29] <thomi> getprop something.something.something?
[15:30] <pitti> thomi: on phones?
[15:30] <thomi> yeah
[15:30] <pitti> thomi: cat /etc/media-info for classic, system-image-cli -i for readonly system images
[15:31] <thomi> pitti: thanks!
[15:35] <balloons> DanChapman, hmm.. Well I can give you the specific logs of what's failing, but I wonder why the difference
[15:35] <balloons> I'm on saucy
[15:35] <smartboyhw> what's up balloons, we are close to Beta 2!
[15:35] <DanChapman> balloons: me too. let me just run them again
[15:36] <balloons> DanChapman, I'll paste the log
[15:36] <balloons> hey smartboyhw , yes yes we are close
[15:36] <balloons> the release is very close now
[15:37] <smartboyhw> balloons, time to move your world-known press effort to promote Beta 2 QA.
[15:39] <balloons> DanChapman, http://paste.ubuntu.com/6128772/
[15:39] <balloons> smartboyhw, yes, there is much to talk about
[15:44] <DanChapman> balloons: your running the wrong tests. Thats the libap-gtk tests the emulator tests are in further in /tests/autopilot/emulators/tests
[15:50] <DanChapman> balloons: did you find them? :-)
[15:53] <balloons> DanChapman, yes.. thanks for noticing.. still the ap-gtk tests shouldn't be failing :-)
[15:55] <balloons> Ok, so now for the more fun part, running commentary
[15:56] <balloons> DanChapman, have you found the labels to be consistent across applications? You have selects against english text names spread about
[15:58] <balloons> I take it it works out since something like say the file dialog is fairly well reused -- any issues with non-english locales?
[15:59] <balloons> also, is logger.info the right level for some of these statements? perhaps they should be logger.debug?
[16:09] <DanChapman> balloons: The selects against labels are only in the GtkFIleCHooserDialog I believe. I hadn't thought about non-english locale. :-S
[16:10] <balloons> DanChapman, I left my comments in the review, since, well others will be using it
[16:10] <DanChapman> and for logging Its the first time i have used it so wasn't sure on what levels should be what
[16:10] <DanChapman> balloons: ok cool will go and look
[16:11] <balloons> might consider a couple tweaks, but overall, it's a +1 from me
[16:14] <DanChapman> balloons: great thanks. Well its a good start for it anyway. SO with logging, would the level mainly be .debug ? The py docs aren't to clear on when to use what
[16:15] <balloons> DanChapman, I would consider it to be all on the debug level.. however, it gets interesting when logging a module
[16:18] <elfy> DanChapman: this autopilot-gtk stuff going to be useful for us on xubuntu?
[16:32] <DanChapman> balloons: Ok well i will change them around.
[16:33] <DanChapman> elfy it should be useful for everyone. It makes writing tests alot easier :-)
[16:35] <balloons> elfy, yes, it makes the process much sane
[16:35] <balloons> *saner
[16:37] <elfy> thanks both
[17:15] <pitti> jibel: I've been poking arm retraces for a while now; I keep getting "wrong size gregset struct in core file" with gdb-multiarch on amd64 :(
[17:16] <pitti> that used to work (for most crashes anyway), but it seems our toolchain has changed somehow
[17:19] <pitti> I'll try that on a phone tomorrow (after lunch I'll have Plumber talks)
[17:19] <pitti> there are still some missing ddebs, but it shouldn't be that broken
[17:37] <balloons> ping thomi
[17:39] <thomi> balloons: yo
[17:41] <balloons> thomi, so I'll be to the point, though we can go deeper if needed. Calendar app tests have been failing for a long time, for unknown reasons. One of the tests seemed to hang for a long time. Turns out there was a big select_many that grabbed many things at once (it had a filter, but probably was client-side). Can we someone generate a message when people do things like this? A warning that you selected a huge amount of objects?
[17:42] <thomi> balloons: what was the query?
[17:42] <balloons> Increasing the performance would also be good, but a warning in the log would alert people invesigating things
[17:42] <thomi> balloons: 1.4 (due to land in T) will help this a lot
[17:42] <balloons> thomi,  labels = self.select_many("Label", text=title).. You know how many labels there are :-)
[17:43] <thomi> yeah
[17:43] <thomi> depending on what the title is, that may be much faster in 1.4
[17:43] <balloons> it was a bit of a silent killer.. the fix was to limit it to a specific view.. in other words grab a child node first and look under that
[17:44]  * elopio <- lunch
[17:44] <thomi> yeah.
[17:45] <thomi> balloons: I'm not sure how we could tell that the query is large before you execute it
[17:45] <balloons> thomi, yes I'm perfectly ok with a warning saying hey, this query returned 500 objects
[17:45] <balloons> it could be after the fact, it would just let those trying to figure out what the issues are do so more easily..
[17:46] <thomi> ahh, I see - AFTER the query returned :)
[17:46] <balloons> you can't save the test author from themselves in this case, but you can provide a helpful hint I think for those looking at what's wrong
[17:46] <thomi> balloons: yeah, I think we can do that
[17:47] <balloons> thomi, shall I file a bug?
[18:26] <balloons> thomi, https://bugs.launchpad.net/autopilot/+bug/1227830
[19:11] <cgoldberg> thomi... hey... is there anything specific for 13.10 release that needs to be done for any tools?  I'm looking for some work besides the automation of found bugs.  Anything for AutoPilot (or anything else)?   feel free to throw stuff my way
[19:12] <thomi> cgoldberg: I remembered something yesterday... what was it. ummm...
[19:12] <thomi> uhhh...
[19:13] <thomi> I'll go make a coffee, hopefully that'll jog my memory
[19:13] <thomi> I told jfunk, maybe he remembers?
[19:13] <knome> balloons, hey :)
[19:14] <balloons> knome, hello!
[19:14] <knome> balloons, what's up?
[19:14] <balloons> well, trying to finish off some things before a long weekend
[19:14] <balloons> there's some cool stuff going on in QA, gotta share it all :-)
[19:14] <knome> heh, trying to avoid the freeze fuzz?
[19:15] <letozaf> balloons, hi
[19:15] <balloons> yea, freeze smeeze
[19:15] <balloons> :-p
[19:15] <balloons> letozaf, buonasera
[19:15] <letozaf> balloons, buonasera :D
[19:16] <thomi> cgoldberg: there are certainly some bugs that would be good to fix. I can't remember what the thing from yesterday was
[19:16] <balloons> how about yourself? Trying to think about and share the manual/automated story moving forward knome.
[19:16] <cgoldberg> thomi, i'll check the bug list
[19:16] <thomi> cgoldberg: want me to suggest a few?
[19:17] <balloons> knome, basically trying to move manual testing forward to the exciting exploratory break it testing and out of the repetitious stuff :-)
[19:17] <knome> balloons, have been quite hectic with getting last uploads in for the beta (and not all have landed yet), but it seems we're again making it!
[19:17] <letozaf> balloons, I was trying to run  phablet-test-run -n ubuntu-clock-app on my device but I get a error: closed message :(
[19:17] <cgoldberg> thomi, sure... if you can ping me a list of bug numbers, I'll triage and get on them for fixing
[19:17] <balloons> letozaf, can you share what you got exactly? can you adb shell in ok?
[19:17] <thomi> cgoldberg: there's this, which may end up being already fixed, but there's no test for it: https://bugs.launchpad.net/autopilot/+bug/1206805
[19:17] <knome> balloons, do you think a blog article or something would help? if you had some questions thought out, could easily answer to them
[19:18] <thomi> cgoldberg: but you should be able to mock out the dbus call that's in that stack trace and see what happens to wait_for
[19:18] <letozaf> balloons, yes adb shell is ok
[19:18] <balloons> knome, I've got a least one article in draft talking about it.. Trying to get it all out :-)
[19:18] <cgoldberg> thomi, ok.. i'll write a test for it and fix up
[19:19] <letozaf> balloons, after installing yesterday's software, I tried to run the ubuntu-clock-app with
[19:19] <thomi> cgoldberg: awesome! maybe I'll remember what the other thing was :-/
[19:19] <knome> balloons, we probably should sit down together some time and think about that, probably after b2 testsing
[19:19] <knome> *testing too
[19:19] <cgoldberg> hah.. let me know if you do
[19:19] <letozaf> balloons, phablet-test-run -n ubuntu-clock-app
[19:20] <letozaf> balloons, I just get two error: closed messages and the shell again
[19:20] <letozaf> balloons, maybe I forgot to install something ?
[19:20] <balloons> knome, yes, I would like us all to have a think about it. I'm just mentioning it to you so you can think about it. We have autopilot tests for ubiquity for many of the iso tests. We can probably re-think how we handle respins, particularly for non-impacting packages
[19:20] <balloons> letozaf, ohh, lol
[19:20] <balloons> don't adb sheel in first.. run it from your desktop :-)
[19:21] <knome> balloons, would what you are saying be simply not updating the "build" on the iso tracker, but only in packages tracker
[19:21] <letozaf> balloons, ahhhh! :P
[19:22] <letozaf> balloons, thanks :P
[19:27] <letozaf> balloons, :(     ImportError: No module named ubuntu-clock-app
[19:27] <balloons> letozaf, that is the type of error you should see. It means you didn't install ubuntu-clock-app-autopilot on the device. Ohh, also watch the dashes '-'.. it should look like this: phablet-test-run -b ubuntu_clock_app
[19:29] <letozaf> balloons, oh! I wrote ubuntu-clock-app :( anyway ubuntu-clock-app-autopilot was non installed on the device,  I will do it now
[19:29] <balloons> yes, the module name uses underscores
[19:29] <balloons> keeps you on your toes
[19:29] <letozaf> balloons, yeah!
[19:30] <jibel> pitti, thanks for looking into this. Tell me I can be of any help.
[19:31] <letozaf> balloons, cool it's running ... the test :P
[19:36] <thomi> elopio: I think I've fixed this bug, but I wonder if you could confirm for me please? https://bugs.launchpad.net/autopilot/+bug/1225026
[19:40] <balloons> letozaf, awesome.. So you got the hang of the device now?
[19:41] <letozaf> balloons, "the hang of the device"  :)
[19:41] <letozaf> balloons, I'm starting to figure out how things work
[19:45] <letozaf> balloons, is there a way to be sure that I have the latest updates on the device, I mean I see  "version 56" under settings/updates but how do I know I have the last one ?
[19:49] <balloons> letozaf, if there is no update available, you are running the latest :-)
[19:49] <balloons> letozaf, https://plus.google.com/104307250302998042813/posts/f4viizsY2v5
[19:49] <balloons> letozaf, sorry, https://wiki.ubuntu.com/QATeam/TouchTesting#Which_build_am_I_running.3F
[19:51] <letozaf> balloons, mmm Ubuntu Saucy Salamander (development branch) - armhf (20130916.3)
[19:52] <letozaf> balloons, doesn't look like the last, shouldn't it be 20130918.1 ?
[19:52] <balloons> letozaf, indeed.
[19:52] <letozaf> balloons, I will try to update again
[19:53] <balloons> if needed, you can phablet-flash ubuntu-system, and that will do that same thing, albeit it you'll have to download the full image
[19:55] <letozaf> balloons, if updating from the device won't work I will  phablet-flash ubuntu-system
[19:55] <letozaf> balloons, wow, no, it updated it's rebooting now! thought i hit a bug :P
[19:57] <letozaf> balloons, this is weired, after reboot I have the same previous version
[19:58] <thomi> cgoldberg: I wonder if you have the time to process a couple of AP code reviews?
[19:58] <letozaf> balloons, could it be a bug or should I just  phablet-flash ubuntu-system
[19:59] <thomi> cgoldberg: also, I notice you changes tox.ini to run the AP functional tests, but it doesn't really work very well, since the applications it launches still appear in the desktop, so I think we should revert that change
[20:01] <WebbyIT> Hi all :) Hi letozaf, do you have 5 minutes for a query?
[20:01] <letozaf> WebbyIT, hello!
[20:02] <letozaf> WebbyIT, yes
[20:03] <WebbyIT> thanks
[20:03] <balloons> letozaf, what does adb shell cat /etc/media-info now?
[20:03] <balloons> letozaf, ohh, why lookey there, hehe
[20:04] <letozaf> balloons, Ubuntu Saucy Salamander (development branch) - armhf (20130916.3)
[20:06] <balloons> letozaf, yea, it should have updated. did the phablet-flash download a new build?
[20:06] <balloons> what did it say it was installing?
[20:07] <balloons> can you do a system update?
[20:07] <letozaf> I just got an orange button saying install and reboot
[20:07] <letozaf> balloons, when I clicked it the device rebooted in recovery mode
[20:08] <letozaf> balloons, so I chose just to reboot, if I choose install it asks me what to install, not sure if I had to select the .zip
[20:08] <letozaf> balloons, file ... the name was
[20:09] <balloons> letozaf, ohh no, let phablet-flash do it's thing
[20:09] <balloons> you shouldn't need to touch the phone at all.. it'll do everything and when it's done it will boot into ubuntu
[20:10] <balloons> letozaf,  did system-settings, updates not work for you however?
[20:10] <balloons> it should
[20:11] <letozaf> balloons, when I choose to update from system-settings updates, it askes me to install and reboot, just that it reboots in recovery, so I select just to reboot, ubuntu starts but the version is the old one
[20:12] <balloons> letozaf, that all sounds correct. it will reboot into recovery and update itself, then reboot into ubuntu
[20:13] <letozaf> balloons, well maybe my problem is that, when I first installed ubuntu touch, with the phablet-flash ubuntu-system --channel devel --no-backup
[20:14] <letozaf> balloons, command the device rebooted but recovery did not launch, I just got the green android figure with a yellow triangle
[20:14] <balloons> letozaf, well I'd say flash with phablet-flash ubuntu-system. then tomorrow when an update hits, do the update
[20:15] <letozaf> balloons, yes I was also thinking to do a phablet-flash
[20:15] <balloons> the update goes to a weird android looking screen with a progress bar along the bottom.. takes a bit, but then it reboots and your updated
[20:15] <knome> you're
[20:15] <letozaf> balloons, not for me
[20:15] <balloons> knome, :-)
[20:15] <letozaf> balloons, it reboots into recovery :(
[20:16] <balloons> letozaf, k, well just reflash and see if the update works tomorrow.. if it doesn't, that's a bug, hah
[20:16] <balloons> mine have actually worked well
[20:17] <letozaf> balloons, ok I will do so
[20:22] <elopio> thomi: yes, I'll give it a try.
[20:24] <thomi> elopio: thanks
[20:36] <letozaf> balloons, reflashing worked fine :)
[20:37] <letozaf> balloons, let's see tomorrow that happens when I update
[20:37] <balloons> :-)
[21:22] <knome> hey slickymaster
[21:23] <slickymaster> hi knome. Hope everything is fine with you
[21:23] <knome> yep
[21:24] <slickymaster> knome, I haven't forgot the Xubuntu Documentation translation, but I've been pretty busy with editing the upcoming 13.10 manual
[21:25] <knome> slickymaster, no problem, we're not going to be able to use the docs translations this cycle anyway
[21:26] <slickymaster> knome, yeah, I know. Documentation string freeze today
[21:26] <knome> slickymaster, that's not the culprit :)
[21:27] <knome> slickymaster, there is another freeze for translated strings anyway
[21:27] <slickymaster> knome, didn't knew that
[21:30] <slickymaster> knome, anyway as it seems that there's nothing besides that for me to help in the xubuntu team
[21:31] <slickymaster> knome, I will try to finish it before the end of next month
[21:31] <knome> slickymaster, no problem, take your time :)
[21:32] <Noskcaj> slickymaster, " nothing besides that for me to help in the xubuntu team" ? test things, fix bugs, learn a coding language.
[21:32] <Noskcaj> ;)
[21:33] <slickymaster> Noskcaj, I spent my work days coding in Java and in SQL
[21:35] <Noskcaj> Then if you ever run out of things to do, we've got a gint bug tracker
[21:35] <Noskcaj> *giant
[21:36] <slickymaster> Noskcaj, well I was thinking to take a plunge at wiki.documentation as they seem to need a few extras pair of hands
[21:36] <Noskcaj> slickymaster, That would also be great
[21:37] <Noskcaj> i need food, i'll be back later
[21:37] <slickymaster> Noskcaj, like the French say: Bon appetit
[21:49] <elopio> thomi: I'm fully updated with the autopilot/experimental ppa and the issue is still happening.
[23:27] <slickymaster> cyu all tomorrow. good night