[00:14] popey: can you file a bug and attach the click? [00:18] I haven't seen that before and no one has mentioned it [00:19] also, one would think we would have seen it before now... === _salem is now known as salem_ === salem_ is now known as _salem [02:38] robru: can you check why the status for line 66 is not reflecting the current state for the silo? [02:39] rsalveti: formula for cell C66 got lost, fixed [02:39] robru: thanks! [02:40] rsalveti: you're welcome [05:13] good morning! [05:14] trainguards: can I have a silo for line 83, please? [05:15] oSoMoN: one sec [05:16] oSoMoN: if robru wouldn't be so late-nighter, I'd assign you a silo, yes :) [05:16] Mirv: oh are you up early? go ahead ;-) [05:16] Mirv: but the line is wrong, needs package name mentioned [05:17] oSoMoN: package name missing from source package column [05:17] oh sorry, I’ll fix that [05:17] robru: I'm always up at this hour :) ok. [05:17] robru, fixed [05:17] assigning + copying [05:17] Mirv: oh really? usually I don't notice you for another couple hours. I guess it's just quiet at the start of your shift ;-) [05:17] Mirv: thanks [05:18] oSoMoN: Mirv goodnight! [05:18] robru, good night :) [05:18] robru: I don't say much but you might notice train choo chooing :) often though you've already published everything there's to publish and I'll just start on my Qt stuff and others [05:18] robru: good night! === chihchun_afk is now known as chihchun === oSoMoN_ is now known as oSoMoN [07:57] bzoltan: ping! [07:57] bzoltan: please approve https://code.launchpad.net/~marcustomlinson/qtcreator-plugin-ubuntu/refactor-scope-template/+merge/259083 [08:05] good morning; are there silos available this morning ? [08:28] Mirv, ogra_, popey: no meeting today if anything [08:28] Forgot to cancel earlier [08:28] oki [08:28] dbarth_: let me check [08:29] dbarth_: sadly... we have 0 [08:30] sil2100: oh, ok [08:32] ok sil2100 [08:36] hmm [08:36] We should have one soon though ;) [09:25] \o/ [09:25] all testing good phone + desktop wily [09:25] awesomeness syncing happening [09:26] (with debian) [09:28] \o/ [09:30] so qtbase will move to Debian git now that I was able to do this final cleanup. first https://launchpad.net/ubuntu/+source/qtbase-opensource-src/5.4.1+dfsg-3ubuntu1 and now this https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-020/+sourcepub/5089141/+listing-archive-extra [09:31] such work, much packaging [09:32] I shouldn't try doge or other memes when I don't do it well enough [10:06] * sil2100 preparing early lunch === oSoMoN__ is now known as oSoMoN [11:08] Mirv: ah! btw. did you add telepathy-ofono-ril-mc-plugin to the seed? I think Bill wanted that to happen [11:17] sil2100: yes I did add it [11:19] Mirv: yay! Thanks ;) [11:32] hmmm [11:38] slangasek: we build our images with -updates and -security enabled, right? [11:39] sil2100, my phone says yes :) [11:41] Then we need to copy oxide-qt from those to our overlay, as the pin priority makes the old version being prioritized [11:42] or rely on the fact that new versions go to -updates/-security as well anyway and drop it from the PPA :) [11:49] direct uploads to archives, nothing could go wrong [11:50] well, but they happen anyway [11:51] currently just the pinning saves you :) [11:51] I'm meaning what I'm just doing :) [11:51] just a small revert [11:52] * Mirv thinks compiler stuff is complicated [11:52] ah, i thought you refer to oxide :) [11:52] we should get rid of compilers! [11:52] yep [11:52] shell everywhere ! [11:52] busybox and a kernel is enough OS [11:55] I hope GCC5 fixes the world and we can use -fPIC on arm without Unity 8 breaking [11:55] if not, I'd welcome to know someone who could help with topics like that [11:55] this is bug https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1403758 [11:55] Launchpad bug 1403758 in binutils (Ubuntu) "Unity8 shows black screen with Qt 5.4.0" [Undecided,New] [11:56] I understood quite little of this copy-paste I did from upstream channel https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1403758/comments/8 [11:57] or this http://paste.ubuntu.com/9570566/ [11:57] well, I can approximate understanding the topic but not like having capability of doing something about it :) in the end, they didn't find out what the problem is, other than that there is a problem [11:58] and now Qt upstream is enforcing -fPIC and it'd be nice to not need to revert it. they refer to GCC5 when doing it. [12:38] josepht, ping === _salem is now known as salem_ === chihchun is now known as chihchun_afk === vrruiz is now known as rvr [13:53] bzoltan: Do you still upload uitk test logs anywhere? I think we can land silo 19, but there won't be enough time to run the full test suite before heading to the airport. === oSoMoN_ is now known as oSoMoN [14:04] ubuntu-qa: is vrruiz around? I need to discuss silo 15 with him [14:05] rvr: ^ [14:05] oSoMoN: I'm around [14:05] oSoMoN: I am re-installing the phone to re-check [14:06] rvr, heh, you changed nicknames :) [14:07] oSoMoN: In freenode I use this one :) [14:07] rvr, bfiller, artmello and myself tested and were not able to reproduce the issue you’re seeing, it’d be good if you could confirm whether you can reliably observe it [14:08] oSoMoN: Yesterday I could reproduce the issue following those steps [14:23] oSoMoN: I took me some tries, but I have just reproduced the problem [14:24] rvr, are you not able to reproduce it while not in private mode? this sounds like a rendering problem, most likely unrelated to private browsing [14:25] oSoMoN: The steps I follow are: open the browser, go to private mode, go to elmundo.es, wait until it has loaded. If I can scroll, I go back to normal browsing and then I repeat the steps in private mode. [14:26] rvr, can you try reproducing by doing the same, but opening the same page several times in a row in new (non private) tabs, until you hit (or not) the problem? [14:26] rvr, i.e. browse to elmundo.es, wait for it to load, if you can scroll open a new tab and repeat [14:27] oSoMoN: In regular mode I can't reproduce the problem [14:27] rvr, when the issue happens the page is rendered correctly? [14:27] oSoMoN: Yes, the page is rendered correctly [14:28] oSoMoN: When the scroll is blocked, I can still interact with the browser itself [14:34] oSoMoN: I'm flashing another krillin to check [14:35] rvr, thanks [14:35] rvr, artmello and myself are trying to reproduce on our side [14:36] Context. That last line from oSoMoN sounded vary strange out of context. [14:36] s/vary/very/ [14:36] It's too early in the morning. [14:36] ToyKeeper: lol [14:37] kgunn, "manual acking"... Is someone on this? [14:37] ToyKeeper, in this channel only issues/bugs are reproduced, nothing else [14:37] camako: nope...been busy with Cimi :) [14:40] rvr: any open tabs in "public" mode before switching to private mode? trying to reproduce the issue here [14:40] artmello: Nope [14:54] rsalveti: If you're around, do you know if any extra steps are needed to make the APNs update after installing the android silo? [14:54] awe: abeato: ^ [14:54] (after downloading, fastboot flashing, updating the system image, rebooting) [14:54] but basically you would kind of only test for the carriers you have [14:54] and to get that, you'd need to remove the ofono cache directories and reboot iircm [14:55] but abeato and awe should know more [14:55] oSoMoN: I have a video for you [14:55] ToyKeeper, as rsalveti says, the easiest way to test is to stop ofono, then wipe /var/lib/ofono/* [14:56] then reboot [14:56] +1 [14:56] Thanks, I was just looking for the cache. :) [14:56] rvr, please send it my way [14:56] ToyKeeper, remember to first stop ofono :) [14:56] I did. :) [14:56] ToyKeeper, that said... if you don't have a SIM that was affected by the update, you won't see any difference [14:56] I have a SIM affected by this update. :) [14:57] giffgaff? [14:57] Straight Talk via AT&T. [14:57] abeato, I don't remember a StraightTalk update. Do you? [14:57] On already-updated devices, it suddenly started working for the first time ever this week, and I'm testing it now on a mako. [14:57] awe, can't say [14:57] It doesn't identify as straight talk; it shows up as "TFDATA". [14:57] ToyKeeper, that may be some other fix... [14:57] Nope. [14:58] * awe checks the update diff [14:58] Hey lookkitthat, it worked. :) [14:59] ToyKeeper, I stand corrected, it was updated... glad it works for you! [14:59] https://code-review.phablet.ubuntu.com/gitweb?p=aosp/ubuntu/assets.git;a=commitdiff;h=9dc0982121521702867aa094ebcac536947fe18f [15:03] sil2100: hey there....trying to get that sync of mir done to wily [15:03] awe, abeato, rsalveti: Looks good on mako, now waiting on testing on another platform (which might be a while). [15:03] in silo 30, needs manual acking [15:04] sil2100: Chris Halse Rogers is here with me in Dallas :) and he's a core dev...if you need one [15:07] oSoMoN: http://people.canonical.com/~vrruiz/webbrowser-private-elmundo-freeze.mp4 [15:09] thanks ToyKeeper [15:09] ... and now MMS in Ubuntu works on this carrier for the first time ever. :) [15:13] oSoMoN: Did you see the video? [15:13] oSoMoN_: ^ [15:16] rvr, I’m on a 3G connection, is there any way you can reduce the quality of the video so I don’t have to download 170MB to view it ? [15:16] oSoMoN_: Let me see [15:17] cwayne_: you probably saw, but robru pushed apparmor-easyprof-ubuntu 1.3.11 last night [15:21] sil2100: yes, -updates and -security are enabled [15:22] jdstrand, yeap, scrambling to get custom ready for testing now [15:24] trainguards i have packages that need manual acking, silo 30 [15:26] Hi robru, can you suggest someone to ping re: the SRU process for that autopilot release of mine? [15:33] oSoMoN_: http://people.canonical.com/~vrruiz/webbrowser-private-elmundo-freeze.m4v [15:34] rvr, thanks! [15:40] rvr, when you get in this situation where the view can’t be scrolled, does double tapping to zoom/unzoom work, or does tapping on links to open them work? === oSoMoN_ is now known as oSoMoN [15:43] oSoMoN: Checking [15:44] kgunn: looking into that, I was otp for a minute [15:45] sil2100: thanks, if that migrates...we can do some unity8 landing [15:45] oSoMoN: Nope, doesn't zoom and doesn't open any links [15:46] oSoMoN_: I opened a new tab and the "screenshot" is empty (white) [15:46] oSoMoN_: I mean, in the blocked view [15:47] kgunn: ok, it's a sync and the changes were already signed off by someone to vivid, let me get that info and publish [15:47] sil2100, just a friendly reminder that silo 11 (mir 0.13.1) is also awaiting sync [15:49] camako: yes, in the middle of taking care of it :) [15:51] sil2100: camako ....we wanna source sync right ? [15:52] Yeah :) [15:53] hmmm [15:54] I actually thought that silo 30 already fetched 1.3.1, but indeed it did not [15:54] Ok, anyway, I'll prepare a sync for 1.3.1 too [15:54] I could have checked that and simply rebuilt silo 30 [15:55] Actually, hm, I think I can still do that [16:00] kgunn, camako: I'm rebuilding mir in silo 30 and will re-publish it [16:00] sil2100, mir 0.13.1 right? Not 0.13.0. [16:00] kgunn, camako: so then after silo 30 lands completely, both 0.13.0 and 0.13.1 are in [16:01] sil2100... I'm confused.. silo 30 has mir 0.13.0 and other downstreams... [16:01] sil2100, silo 11 has mir 0.13.1 which should land after silo 30 [16:01] s/land/sync [16:02] camako: silo 11 is android [16:02] There's no mir in silo 11, 0.13.1 landed in vivid already [16:02] So what I'm doing: [16:02] I published silo 30, so mir 0.13.0 + all the others have been pushed to wily [16:03] But now, before freeing up the silo, I'm also rebuilding mir as a sync to get 0.13.1 landed to wily through the same silo as well [16:03] sil2100, yeah ok it's no longer in silo 11 [16:03] And will re-publish the silo after it builds and you guys give a +1 [16:04] I'm doing this not to waste silos ;) [16:04] We're re-using silo 30 to build the 0.13.1 sync now [16:04] sil2100, so you're just recycling silo 30 to do the sync for Mir 0.13.1... got it [16:04] Yeah, sorry for the confusion, but sync silos are convinient enough that you can fetch latest changes if needed and re-build === oSoMoN__ is now known as oSoMoN [16:14] Woohooo, QA is on a roll! [16:17] woo [16:18] Uh oh [16:19] That got reassigned fast... [16:20] * charles hands davmor2 a virtual beer to enjoy responsibly this weekend [16:21] charles: can I have an English Coke instead [16:23] Yeah [16:24] We're low on silos so that's normal ;) [16:26] sil2100: hey do you mind pointing me in the direction WRT the SRU-ing process to get the autopilot silo/package released? [16:27] veebers: hey! [16:28] veebers: ah, ok, I see the silo is for vivid, right? Let me fetch the links for you [16:28] sil2100: hey o/ how are things? :-) [16:28] sil2100: coolio thanks, I've looked at the wiki page and updated the bug and asked on ubuntu-bugs but unsure how to proceed from there [16:28] veebers: good good, busy as always, but productive :) So you probably know this right? https://wiki.ubuntu.com/StableReleaseUpdates [16:29] Ok, so the bug is SRUed then, right? [16:29] sil2100: good to hear you are well. Um,, not sure how to answer that, how do I get the bug SRUed? /me re-reads the wiki as he seems to have missed something [16:30] veebers: so, first thing the bugs need to be updated to follow the outlined SRU template [16:30] sil2100: right, done [16:30] There's a template there that tells about regression risks etc. [16:30] well, I'm pretty sure its done: https://bugs.launchpad.net/autopilot/+bug/1425721 [16:30] Launchpad bug 1425721 in Autopilot "Extension classes with multiple base classes aren't merged correctly." [High,Fix released] [16:31] Ah, you would need to update the description with that :) [16:31] Oh? [16:32] Since I saw you put the info as a comment, just paste it into the description of the bug [16:32] I'll try nominating your bugs to the right series [16:32] sil2100: D'oh I see that's dumb of me, thanks for catching that [16:33] sil2100: done :-) [16:34] o/ What about https://bugs.launchpad.net/autopilot/+bug/1376996 ? Is that also fixed/touched in this upload? [16:34] Launchpad bug 1376996 in Autopilot "test_customised_proxy_classes_have_extension_classes started failing all of a sudden" [High,In progress] [16:35] veebers: hm, the other problem that might be causing the package to sit in UNAPPROVED is that there are no bugs linked to this release [16:35] sil2100: oh aye it is, hmm good point. The fix of the first bug means that bug for the selftest is resolved [16:36] veebers: https://code.launchpad.net/~autopilot/autopilot/trunk/+merge/258580 from which the package was built didn't have any bugs assigned to it - in this case it would have been best if the commit-message had the bug numbers listed [16:36] The SRU team only knows what they see in the uploaded package's changelod [16:37] sil2100: hmm, am I able to fix the bug->release issue? (Looks like I've really screwed this process up :-P ) [16:37] And currently it doesn't say which bugs are being fixed, so they might have issues with approving that [16:37] No worries, we can fix this easy I suppose ;p [16:37] Would you mind rebuilding the autopilot package in the silo? [16:37] I mean, would it be a big bother? [16:37] Since what could be done is: [16:37] sil2100: understood. No that should be fine, nothing has changed [16:39] Changing the commit-message of the merge being released to include at the very end a list of bugs being fixed (e.g. (LP: #1425721, LP: #1376996) ) [16:39] Launchpad bug 1425721 in autopilot (Ubuntu Vivid) "Extension classes with multiple base classes aren't merged correctly." [Undecided,New] https://launchpad.net/bugs/1425721 [16:39] Launchpad bug 1376996 in Autopilot "test_customised_proxy_classes_have_extension_classes started failing all of a sudden" [High,In progress] https://launchpad.net/bugs/1376996 [16:39] Then rebuilding the silo and re-publishing it once again [16:39] Since it would be a no-change rebuild, we wouldn't have to re-test it but just publish [16:39] If the bugs are following the SRU template, the SRU team would then review them and accept the package to -proposed [16:40] sil2100: nice, makes sense. I'll need to update that second bug for SRU process, yes? [16:43] veebers: yes, that would be best :) [16:43] veebers: as you can see it's a lot of paperwork ;p [16:49] sil2100: Yeah :-) Hey thanks for the patience and guidance [16:53] sil2100: FYI re-building now :-) [16:57] \o/ === oSoMoN_ is now known as oSoMoN [17:18] veebers: sil2100 ^ what's up? I thought I published that yesterday ;-) [17:19] sil2100: also what's going on here? https://ci-train.ubuntu.com/job/ubuntu-landing-009-1-build/286/console looks like some of your new version mangling code is broken. [17:30] robru, can I please get a silo for line 68, and I need a vivid+overlay one too [17:32] jhodapp: k we're quite low, start with wily first and then we can do vivid afterwards [17:32] robru, alright [17:33] jhodapp: dual landings are coming, hopefully by monday it'll be possible to have one silo that does boht. [17:33] charles: you got silo 3 [17:33] robru, epic! :) [17:33] robru, thanks [17:33] robru: hey, I had to re-do some stuff due to the SRU process, sil2100 helped me out [17:33] charles: you're welcome [17:34] veebers: so that's ready to publish again? [17:34] jhodapp: you got silo 32, note you have conflicts in silo 24 [17:34] robru, yes, silo 24 is on hold for now [17:35] robru, thanks [17:35] jhodapp: you're welcome [17:35] robru: yeah if the rebuild is done. I've updated the bugs and the commit message to adhere to sru process (hopefully successfully :-)) [17:36] whups [17:37] veebers: ok published [17:37] veebers: make sure to poke SRU people to move that along. [17:37] robru: sweet cheers. Who would I poke? [17:38] veebers: SRU. people. ;-) [17:38] robru: lol [17:38] veebers: https://launchpad.net/~ubuntu-sru/+members#active somebody from here [17:39] veebers: preferrably somebody that you know, it's less weird that way [17:39] robru: understood [17:46] robru: no, it's not version mangling's fault [17:46] robru: someone tried releasing a wily-based trunk to vivid [17:46] sil2100: oh hrm [17:47] sil2100: how have I never seen that before? lol [17:47] robru: dch won't allow (without -b) a lower version than the previous ;) Already happened once [17:47] In the past it wasn't a problem since RTM used the same series version for versioning as the ubuntu distro [17:47] Here, well, upstreams need to make sure they release the right branches to the right distro [17:48] Releasing from one trunk to vivid, then next ver to wily and next one just to vivid is something that shouldn't be allowed [17:50] sil2100: ah that makes sense. so that project should have branched. [17:52] I suppose so, most probably - anyway some action from the upstream is required to sort this out [17:52] :) [18:01] sil2100: do you know what's going on in silo 30? === oSoMoN_ is now known as oSoMoN [18:56] jhodapp: https://ci-train.ubuntu.com/job/ubuntu-landing-032-2-publish/4/console need those merges approved [18:57] robru, yes indeed [18:57] charles: need this merge approved: https://code.launchpad.net/~charlesk/indicator-power/lp-1370791-15.10-adjust-slider-when-brightness-is-changed-by-powerd/+merge/259963 [18:57] robru, been short on people able to review my code lately [18:57] robru, ack [18:59] robru, alecu's top-approved it for ubuntu/landing-003 [19:00] charles: ok published [19:00] jhodapp: ping me when yours are approved [19:00] \o/ [19:00] robru, alrighty, thanks [19:01] jhodapp: you're welcome [19:29] robru, silo 32 is ready to land now, branches have been approved [19:36] jhodapp: thanks [20:41] robru, silo 30 (Wily sync for Mir 0.13.1) has been built and tested. Can you please publish? [20:43] camako: uh yes? that silo is stuck in proposed due to a test regression. http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#mir [20:45] robru, note that the same silo was used previously for syncing Mir 0.13.0 and its downstreams... The silo was then recycled to sync Mir 0.13.1 and that's what my request is about.. (just to give you the full picture) [20:46] camako: right, but if you check the actual version numbers, the silo PPA contains 0.13.1+15.10.20150520-0ubuntu1 which is the same version that's in wily-proposed and the same version that's blocked as per the link I just gave ^ [20:47] robru, ack [20:47] camako: what I'm trying to say is that I published it 2 hours ago and it's broken, your turn to go fix it now. [20:47] camako: I'd check with cihelp if you need help interpreting the test failures (I know those jenkins pages can be a bit hard to find the relevant info from) === salem_ is now known as _salem [21:17] robru, can I get a silo for line 69 please? [21:18] jhodapp: but but.. you just landed media-hub in wily ;-) k you got 23 [21:19] robru, hehe, there's a lot of backed up MRs that have been waiting to land :) [21:19] thanks man [21:19] jhodapp: you're welcome [21:24] robru, I take it this error is because media-hub from silo 32 hasn't quite landed yet? https://ci-train.ubuntu.com/job/ubuntu-landing-023-1-build/68/console [21:25] jhodapp: yeah, if you want you can force that build now and then rebuild it later, or you can wait for silo 32 to auto merge & clean, then a normal build will work. [21:25] robru, awesome, I'll just wait then thanks [21:25] jhodapp: oh actually [21:26] jhodapp: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#qtubuntu-media looks like there was a regression with that silo. better check that out [21:26] robru, what does that mean? [21:27] jhodapp: it means that your package failed an automated test when it was in wily-proposed, which is preventing it from landing in wily. [21:28] robru, ugg [21:28] jhodapp: https://jenkins.qa.ubuntu.com/job/wily-boottest-qtubuntu-media/lastBuild/console I have no idea how to interpret that, you should poke cihelp [21:29] robru, how could publish have been clicked with this error existing (I don't see an obvious error in there)? [21:30] jhodapp: because this error is discovered after publish gets clicked. [21:30] robru, also, that log looks like the infrastructure needed to run qtubuntu-media's tests failed in that build [21:30] jhodapp: that error is in -proposed, let me retry that, should be unrelated to whatever happens before package hits -proposed [21:31] jhodapp: it could very well be an infra issue [21:31] Ursinha, ok thanks [21:31] jhodapp: the way it works is, you run your tests, confirm it live on the phone, then we click publish. then it goes into -proposed and more tests get run. those extra tests don't always pass. [21:32] robru, ok, what are those extra tests that get run out of curiosity? not the unit tests in the package right? [21:32] hm, I think fginther already retried that but didn't tell anyone :) [21:33] Ursinha, any idea what the issue is then? I don't see anything obvious that points to qtubuntu-media unit tests failing there [21:33] jhodapp: there's a few. mostly they make sure that your new package doesn't put other packages into a situation where they can no longer be installed. in this case the failure was boottest, which means theoretically your ppackage prevents the device from booting. https://wiki.ubuntu.com/ProposedMigration [21:33] jhodapp: it seems there is an apt race condition that leads to that problem sometimes, many times retrying solves that (for that specific issue) [21:34] it's unrelated to unit tests, it's boottesting [21:34] jhodapp, Ursinha yes. I had noticed a bunch of failures and was trying to see if something more serious was afoot [21:34] ok, so doesn't sound like something for me to solve with qtubuntu-media, at least not yet? [21:34] jhodapp: it has nothing to do with unit tests [21:34] ok great [21:34] :) [21:34] :) [21:35] jhodapp: nooo! your changes made the phone unbootable. ITS ALL YOUR FAULT WHY DO YOU HATE UBUNTU!!! [21:35] ;-) [21:35] haha [21:35] because it's not Windows? /me runs [21:35] j/k [21:37] thems fightin words... [21:39] Ursinha, anything I need to do then? [21:39] jhodapp: nope :) [21:39] Ursinha, excellent, thanks [22:04] trainguards: QA has signed off silo 15 (thanks rvr!), can it be published? [22:05] oSoMoN: that silo is configured as an SRU for vivid desktop/server, is that what you want, or is it really just for the overlay ppa (phone only)? [22:06] robru, that’s line 55 right? the spreadsheet says it targets the overlay PPA [22:06] oSoMoN: yeah 55. spreadsheet is just wishful thinking; silo is configured wrong. dashboard is authoritative. I'll fix it. [22:07] robru, that’s weird, I don’t know how that happened, I targetted the overlay PPA when I created the landing request, and haven’t changed it since then [22:08] oSoMoN: I guess whoever assigned it clicked it just before youset the overlay ppa [22:08] could be, although I tend to set the destination PPA column before setting the "ready for silo" one [22:10] oSoMoN: well, anyway, reconfigured, and published [22:12] robru, thanks :) [22:12] oSoMoN: you're welcome! [22:24] yay, silo landed, thanks whomever took care of that!