[00:53] <mup> PR # closed: snapcraft#1649, snapcraft#1720, snapcraft#1875, snapcraft#1905, snapcraft#2020, snapcraft#2135, snapcraft#2176, snapcraft#2229, snapcraft#2239, snapcraft#2289, snapcraft#2354, snapcraft#2359, snapcraft#2369
[05:11] <mborzecki> morning
[06:20] <zyga> good morning
[06:20] <zyga> mborzecki: hey :)
[06:20] <mborzecki> zyga: hey hey
[06:20] <zyga> I walked my daughter to school today
[06:20] <zyga> it's so misty I was afraid of letting her go by herself
[06:20] <zyga> how are you doing?
[06:20] <mborzecki> and  it's cold too
[06:21] <mborzecki> glad i swapped the tyres in the car on friday
[06:22] <zyga> yeah, scarfs, hand gloves and caps
[06:25]  * zyga reads some news about the election yesterday
[06:25] <zyga> then back to patches
[06:28] <mborzecki> zyga: heh, elections, the situation in lodz is 'stable' :)
[06:37] <zyga> mborzecki: so nothing changed?
[06:38] <mborzecki> zyga: yeah, exit polls suggest the same president as before with 70+% votes
[06:40] <zyga> I signed up to Apple Music yesterday as a trial to show my dad how it works
[06:40] <zyga> I'm in love :) it's fantastic
[06:41] <mborzecki> zyga: btw. https://status.github.com/messages
[06:41] <zyga> DRM free music, everything in iTunes seems to be available, 19zł a month
[06:41] <zyga> oh
[06:41] <zyga> github is down? I'm reading reviews now and it's ok so far
[06:41] <zyga> woah
[06:41] <zyga> data corruption
[06:41] <zyga> well
[06:41] <zyga> monday :)
[06:42] <mborzecki> zyga: appl music? basically like spotify?
[06:42] <zyga> no
[06:43] <zyga> it's like iTunes (you buy music, it's DRM free on your disk)
[06:43] <zyga> all you can eat
[06:43] <zyga> you can stream but you can also just download and keep offline forever
[06:43] <zyga> I usually spend 20-50 a month per music
[06:43] <zyga> so this is much cheaper
[06:44] <zyga> there's also a family plan but I didn't look at that yet, for up to six people
[06:44] <mborzecki> zyga: download as some format and keep forever elsewhere or are you forced to use the app?
[06:44] <zyga> it's just mp4
[06:44] <zyga> normal format
[06:44] <zyga> one sec
[06:56] <mborzecki> zyga: heh, have you tried doing reviews today?
[06:56] <dot-tobias> Good morning everyone
[06:56] <zyga> well, I'm trying now
[06:56] <zyga> hey dot-tobias :-)
[06:56] <zyga> mborzecki: what are you observing?
[06:56] <mborzecki> zyga: ui getting stuc waiting for response when adding comemnts
[07:00] <mborzecki> zyga: and got a unicorn erorr page :P
[07:00] <mborzecki> haha and the review was not sent
[07:00] <mborzecki> omg
[07:02] <mborzecki> so much for reviews
[07:06] <zyga> re
[07:06] <zyga> that's not encouraging :/
[07:08] <dot-tobias> quite possibly a dumb question, but … can I assume that the “last modified” date for edge images (http://cdimage.ubuntu.com/ubuntu-core/16/edge/current/) can be completely ignored and the build is in fact “daily”?
[07:08] <zyga> hmmm, good question dot-tobias
[07:08] <zyga> it looks fishy to me
[07:08] <zyga> I think it's not the latest one
[07:09] <pstolowski> morning
[07:10] <mborzecki> pstolowski: hey
[07:50] <mup> PR snapcraft#2378 opened: Release chagelog for 3.0 <Created by sergiusens> <https://github.com/snapcore/snapcraft/pull/2378>
[07:51] <Chipaca> mo'in
[07:51] <zyga> oi
[07:52] <Chipaca> mborzecki: https://pastebin.ubuntu.com/p/B6QY2h3gwB/
[07:52] <mborzecki> Chipaca: nice
[07:53] <Chipaca> I wish we had a "can run things from such-n-such snap" interface
[07:53] <mup> PR snapcraft#2378 closed: Release chagelog for 3.0 <Created by sergiusens> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/2378>
[07:53] <Chipaca> then taht wouldn't need classic :-)
[07:53] <zyga> Chipaca: we could
[07:53] <zyga> we have the capability
[07:53] <Chipaca> mborzecki: if you want to push it feel free; otherwise i could
[07:54] <Chipaca> zyga: it's like a content interface but different
[07:54] <zyga> haha
[07:54] <zyga> yes
[07:54] <zyga> not content ;)
[07:55] <zyga> it'd be an interface where we'd have a set of snap commands that a given snap can run
[07:55] <zyga> enforced at snap-confine level, I suspect
[07:55] <Chipaca> mborzecki: otoh we could also package shellcheck into the snap ourselves
[07:55] <Chipaca> mborzecki: or offer spread-shellcheck upstream
[07:55] <Chipaca> mborzecki: the latter needs a bit of paperwork
[07:56] <mborzecki> Chipaca: shellcheck gets frequent updates, at least here on arch, it's probably upstream pushing new changes
[07:58] <Chipaca> on a completely unrelated subject: WTH https://i.imgur.com/YcjvITL.png
[07:59] <zyga> Chipaca: promoted!
[07:59] <zyga> WAT
[07:59] <Chipaca> exactly
[07:59] <Chipaca> somebody paid money to do that
[07:59]  * zyga puts on pants
[07:59] <zyga> must be important
[08:01] <Chipaca> zyga: maybe it's a US/UK thing
[08:01] <mborzecki> Chipaca: no pants?
[08:01] <Chipaca> mborzecki: https://en.wiktionary.org/wiki/pants
[08:01] <Chipaca> mborzecki: look at the pics
[08:05] <mup> PR snapcraft#2378 opened: Release chagelog for 3.0 <Created by sergiusens> <https://github.com/snapcore/snapcraft/pull/2378>
[08:06] <zyga> hmmm
[08:06] <zyga> github is indeed wonky
[08:06] <Chipaca> oh, nice, github's databases are eventually inconsistent right now
[08:06] <zyga> chipaca's critical PR is marked as approved
[08:06] <zyga> but if you click on it, it is not, no comment history
[08:07] <Chipaca> https://mobile.twitter.com/TheRegister/status/1054267789232431104
[08:07] <zyga> the pic is very representative of IS work
[08:07] <zyga> not
[08:08] <mborzecki> Chipaca: did you get my review of https://github.com/snapcore/snapd/pull/6026 ? when i go to the PR there's like 3 reviews pending (?)
[08:08] <Chipaca> well, it's the reg
[08:08] <mup> PR #6026: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[08:08] <Chipaca> mborzecki: i got yours
[08:08] <Chipaca> mborzecki: nobody else's yet
[08:08] <mup> PR snapcraft#2378 closed: Release chagelog for 3.0 <Created by sergiusens> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/2378>
[08:08] <mborzecki> Chipaca: well i got a unicorn in return :P
[08:08] <Chipaca> mborzecki: but as above, github's hard drive is full
[08:09] <zyga> unicorns
[08:09] <zyga> unicorns everywhere
[08:10] <Chipaca> zyga: https://www.youtube.com/watch?v=DX1iplQQJTo&feature=youtu.be&t=90
[08:11] <zyga> https://imgflip.com/i/2knjpg
[08:12] <zyga> I guess the windows upgrade went well at GitHub today
[08:24] <zyga> GH reviews are still in read only mode
[08:25] <mborzecki> zyga: at least one got through :P
[08:26] <zyga> oh? I keep try to send a trivial comment to see what happens
[08:33] <mborzecki> haha got zyga's review email, but the reviews are not visible https://github.com/snapcore/snapd/pull/6026
[08:33] <mup> PR #6026: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[08:34] <Chipaca> well I got mborzecki 's review twice
[08:34] <Chipaca> so there
[08:34] <mborzecki> hahah
[08:34] <Chipaca> zyga: and i just got a review from you as well
[08:34] <mborzecki> oh and in zyga's review the comment was doubled
[08:34] <Chipaca> yes
[08:35] <Chipaca> zyga: so, depends how you look at it :-) that was the thing that triggered the panic, so that's the immediate cause
[08:35] <Chipaca> zyga: but before that, cmdTry was different from other snap ops in that it didn't pass the error to errorToCmdMessage
[08:35] <mborzecki> https://blog.github.com/2018-10-21-october21-incident-report/
[08:35] <Chipaca> zyga: so that's the deeper cause
[08:36] <Chipaca> zyga: because there _is_ an opts for this error, it's just not in main
[08:36] <Chipaca> zyga: which one of those causes is the crux, i guess it depends on how you look at it?
[08:44] <zyga> mmm, I see
[08:45] <zyga> I made exceptionally hot coffee
[08:45] <zyga> my hands are freezing here
[08:49]  * Chipaca hands zyga a "crux of the matter" trophy
[08:49] <Chipaca> (just got another few emails)
[08:49] <zyga> hahah
[08:49] <zyga> it's still being published?
[08:50] <zyga> I see them now
[08:51] <mborzecki> zyga: github liked you comment so much it keep on sending it ;)
[08:51] <zyga> haha
[08:51] <zyga> eventually it will stop ;-)
[08:51] <mborzecki> haha
[09:22] <mborzecki> is it just me or are none of the 2 reviews posted in https://github.com/snapcore/snapd/pull/6026 visible?
[09:22] <mup> PR #6026: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[09:32] <sil2100> zyga: hey! Did you have a moment to check the dragonboard image?
[09:32] <zyga> yes!
[09:32] <zyga> let's do it :)
[09:32] <zyga> is the one from last week good?
[09:32] <zyga> or shall I pick lastest
[09:33] <sil2100> http://cdimage.ubuntu.com/ubuntu-core/18/pending/ubuntu-core-18-arm64+snapdragon.img.xz <- latest is always the best ;)
[09:33] <sil2100> Oh, no mvo today?
[09:34] <zyga> sil2100: no, sprinting
[09:34] <zyga> sil2100: flashing
[09:34] <sil2100> zyga: do you maybe know when's the ETA for a stable-channel release of snapd?
[09:34] <zyga> no idea
[09:34] <zyga> maybe mid sprint?
[09:35] <zyga> but really no idea
[09:36] <Chipaca> sil2100: are you talking about 2.36?
[09:37] <sil2100> Chipaca: I'm talking about the snapd snap
[09:37] <sil2100> Chipaca: we don't have any version of it in stable from what I can see at least
[09:37] <Chipaca> ah
[09:37] <Chipaca> ok :-)
[09:37] <Chipaca> no idea
[10:01] <mborzecki> Chipaca: shall we try posting the reviews again?
[10:02] <Chipaca> mborzecki: zyga: please
[10:02]  * Chipaca afk for a bit
[10:02] <zyga> yep
[10:02] <Chipaca> bah
[10:02] <Chipaca> 10:47 British Summer TimeWe continue to monitor restores which are taking longer than anticipated. We estimate they will be caught up in an hour and a half.
[10:02] <Chipaca> so maybe let's check after lunch
[10:02] <Chipaca> zyga: mborzecki ^
[10:03] <Chipaca> (that was 15 minutes ago)
[10:03] <mborzecki> too late, already clicked :P
[10:03] <mborzecki> aand unicorn!
[10:09] <zyga> unicorn days
[10:10] <zyga> I tried to fork a repo just now
[10:10] <zyga> 404 and errors
[10:15] <zyga> sil2100: it works
[10:16] <zyga> https://www.irccloud.com/pastebin/bPMblg1d/
[10:16] <zyga> dragon board is operational :)
[10:16] <zyga> 11:47 CESTWe continue to monitor restores which are taking longer than anticipated. We estimate they will be caught up in an hour and a half.
[10:16] <zyga> from status.github.com
[10:17] <mup> Issue # closed: classic-snap#7, classic-snap#8, classic-snap#14, classic-snap#15
[10:17] <mup> PR # closed: classic-snap#24, classic-snap#27, classic-snap#28, classic-snap#30
[10:19] <sil2100> Let's SHIP IT
[10:20] <mup> PR core-build#11 closed: remove cruft from the writable-paths <Created by mvo5> <https://github.com/snapcore/core-build/pull/11>
[10:20] <mup> PR core-build#22 closed: unit testing for sync_dir() <Created by mvo5> <https://github.com/snapcore/core-build/pull/22>
[10:20] <mup> PR core-build#26 closed: move most of the customization into the core snap build <Created by mvo5> <https://github.com/snapcore/core-build/pull/26>
[10:20] <mup> Issue # opened: classic-snap#7, classic-snap#8, classic-snap#14, classic-snap#15
[10:20] <mup> PR # opened: classic-snap#24, classic-snap#27, classic-snap#28, classic-snap#30
[10:21] <mup> PR core-build#11 opened: remove cruft from the writable-paths <Created by mvo5> <https://github.com/snapcore/core-build/pull/11>
[10:21] <mup> PR core-build#22 opened: unit testing for sync_dir() <Created by mvo5> <https://github.com/snapcore/core-build/pull/22>
[10:21] <mup> PR core-build#26 opened: move most of the customization into the core snap build <Created by mvo5> <https://github.com/snapcore/core-build/pull/26>
[10:21] <zyga> everything is broken :)
[10:22] <zyga> apparently ceph fails universally ;)
[10:23] <pstolowski> Chipaca finally figured Friday's issue greyback hit
[10:23] <mup> PR # closed: snapcraft#1649, snapcraft#1720, snapcraft#1875, snapcraft#1905, snapcraft#2020, snapcraft#2135, snapcraft#2176, snapcraft#2229, snapcraft#2239, snapcraft#2289, snapcraft#2354, snapcraft#2359, snapcraft#2369
[10:24] <greyback> pstolowski: oh nice!
[10:24] <mborzecki> pstolowski: what was it?
[10:25] <pstolowski> mborzecki: a commit i introduced on sep 7, to conflict & retry on discard-snap. I missed the fact that discard-snap is created sometimes by install as well to remove inactive revision. so, auto-refresh conflicts with itself
[10:26] <pstolowski> mborzecki: in this case it tries to refresh lxd and also schedules removal of old inactive revision of lxd
[10:26] <mborzecki> pstolowski: nice
[10:26] <mup> PR # opened: snapcraft#1649, snapcraft#1720, snapcraft#1875, snapcraft#1905, snapcraft#2020, snapcraft#2135, snapcraft#2176, snapcraft#2229, snapcraft#2239, snapcraft#2289, snapcraft#2354, snapcraft#2359, snapcraft#2369
[10:27] <mborzecki> pstolowski: sounds like a scenario we'd like to have a test for
[10:27] <pstolowski> mborzecki: yes, definately. i added a test for conflict, but no we have a case where we shouldn't conflict
[10:27] <pstolowski> *now we have
[10:28] <mborzecki> great
[10:48] <zyga> sil2100: there are some wifi errors on screen after a while
[10:49] <zyga> Oct 22 10:40:55 localhost kernel: wcn36xx: ERROR hal_remove_bsskey response failed err=6
[10:59] <sil2100> zyga: I think we need to poke the kernel team about those
[11:00] <zyga> where shall I report those?
[11:06] <mborzecki> any idea if it's possible to do spread -repeat=<n> but directly in task.yaml?
[11:10] <mborzecki> heh after/before test is fiddly
[11:18] <zyga> mborzecki: no idea
[11:18] <zyga> count: 10?
[11:21] <mborzecki> zyga: doesn't appear to be anything like that
[11:44] <zyga> :/
[11:44] <Chipaca> pstolowski: sounds like another critical 2.36 pr
[11:44] <Chipaca> how's our favourite unicorn factory?
[11:44] <pstolowski> Chipaca: sure, i'm in touch with mvo on that
[11:44] <pstolowski> and fix is in progress
[11:45] <Chipaca> pstolowski: 👍
[11:45] <Chipaca> or maybe 🖒
[11:45] <Chipaca> ¯\_(ツ)_/¯
[11:47] <mborzecki> can i get 2nd reviews on https://github.com/snapcore/snapd/pull/6023 ?
[11:47] <mup> PR #6023: overlord/snapstate, snap, wrappers: start services in the right order during install <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/6023>
[11:50] <mborzecki> off to pick up the kids
[11:57] <zyga> FYI, latest GitHub status
[11:57] <zyga> The majority of restore processes have completed. We anticipate all data stores will be fully consistent within the next hour.
[11:57] <zyga> I just pushed a patch without erorrs
[12:01] <zyga> I take that back
[12:01] <zyga> comments I added just disappeared
[12:06] <zyga> comment showed up and disappeared again
[12:06] <zyga> fun
[12:11] <Chipaca> zyga: were any of your reviews of 6026 a +1?
[12:11] <zyga> Chipaca: let me look
[12:12] <Chipaca> zyga: all I see are a bunch of "crux of the issue" comments :-)
[12:12] <Chipaca> was wondering if I should merge it
[12:12] <zyga> let me try to give it a +1
[12:12] <zyga> my changes elsewhere on GH just go away after I reload
[12:12] <sborovkov> Hi, is there some interface that allows me to change the scaling_governor on the core?
[12:13] <zyga> sborovkov: let me look
[12:13] <zyga> Chipaca: green, merge it
[12:13] <Chipaca> zyga: ooh i see your +1
[12:13] <zyga> sborovkov: no, I'm afraid not
[12:13] <Chipaca> would that be cpu_control, or do we need power_control?
[12:14] <sborovkov> zyga, is it something that's possible to add? basically we are running on rpis. we want to change the scaling governor to performance. Otherwise while it winds up video performance goes down
[12:14] <ogra> cpu-control sounds about right
[12:14] <sborovkov> and it goes down by a lot
[12:14] <zyga> yeah, I agree with ogra
[12:14] <mup> PR snapd#6026 closed: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <Closed by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[12:14] <zyga> feels like a reasonable tweak
[12:14] <ogra> sborovkov, thats weird, the ondemand governor sshould surely cope
[12:15] <mup> PR snapd#6026 opened: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[12:15] <sborovkov> ogra, it does work properly after some time. But when we have a fresh run - the times it takes us to render a frame goes upo from 32 to 64 ms for first 20 seconds and so
[12:15] <Chipaca> ogra: it takes about a second to ramp things up though, doesn't it?
[12:15] <ogra> (while we should add thiss to the interface, you should definitely not see much differenec in system behaviour when switching governors ... just that it doesnt clock down after it is done with processing)
[12:15] <sborovkov> that looks so bad on the customer screens
[12:15] <Chipaca> oh wow that's more than i'd expect
[12:15] <sborovkov> basically the timings were 2 times worse
[12:16] <sborovkov> once we enabled performance governor we never saw anything like that
[12:16] <zyga> sborovkov: can you add this to your snap
[12:16] <ogra> wow, is that with accelerated graphics or plain framebuffer?
[12:16] <zyga> and show me the --devmode denial
[12:16] <zyga> I can make a modification to the interface
[12:16] <mup> PR snapd#6026 closed: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[12:16] <ogra> i definitely dont see that with the kms driver
[12:17] <Chipaca> aaaaah now my pr is half-merged
[12:17] <ogra> non-kms indeed means you fully utilize the CPU and completely leave the GPU alone
[12:17] <zyga> Chipaca: what?
[12:17] <ogra> zyga, github fun today :)
[12:17] <zyga> wow,
[12:17] <zyga> yeah
[12:17] <zyga> I think today is not a good GH day
[12:17] <ogra> i actually learned their 404 pick is interactive !
[12:17] <ogra> *pic
[12:18] <ogra> i never stayed long enough on it to even notice
[12:18] <ogra> but if you wiggle the mouse it makes nice layer shifting effects
[12:18] <mup> PR snapd#6026 opened: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <Closed by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[12:18] <sborovkov> alright I will need to build a devmode snap though or try it from some other one guys, I will write back when I do that. ogra  what do you mean accelerated graphics or plain framebuffer? we do use h/w decoder. and yeah showing stuff with qt's qml, so it's using framebuffer
[12:19] <mup> PR snapd#6026 closed: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <Closed by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[12:20] <ogra> sborovkov, i mean the kms drm driver when you set "dtoverlay=vc4-kms-v3d" in config.txt (this turns on accelerated GLES )
[12:21] <sborovkov> that's not enabled at the moment
[12:21] <sborovkov> it was breaking our qt app previously on the core
[12:21] <sborovkov> I should try to see if it works now actually
[12:22] <ogra> well, probably not without a compositor ... not sure
[12:23]  * ogra curses about this silly x11 restriction that forces you to add a .desktop file for a kiok app 
[12:23] <ogra> *kiosk
[12:23] <zyga> re
[12:23]  * zyga turned on the heater 
[12:26] <mup> PR snapd#6026 opened: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <Merged by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[12:27] <mup> PR snapd#6026 closed: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[12:28] <mup> PR snapd#6026 opened: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <Merged by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[12:28]  * Chipaca hugs mup
[12:29] <zyga> Pushing stuff to GH feels pointless now
[12:29] <zyga> the patches show up
[12:29] <zyga> the diff stays stale
[12:29] <mup> PR snapd#6026 closed: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <Merged by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[12:29] <Chipaca> zyga: let's move back to launchpad
[12:29] <zyga> mborzecki: anyway, I pushed trivial fixes to https://github.com/snapcore/snapd/pull/6010
[12:29] <mup> PR #6010: cmd/snap-discard-ns: add support for per-user mount namespaces <Created by zyga> <https://github.com/snapcore/snapd/pull/6010>
[12:32] <Chipaca> zyga: … or did you?
[12:35] <mborzecki> heh gh is the new single point of failure of modern software dev
[12:36] <mborzecki> pretty much that what we try to avoid when  designing stuff ;)
[12:37] <zyga> mborzecki: wait until Microsoft moves GitHub to azure ;-)
[12:38] <mup> PR snapd#6026 opened: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <Merged by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[12:38] <mborzecki> 13h+ of outage
[12:39] <mup> PR snapd#6026 closed: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[12:41] <mup> PR snapd#6026 opened: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <Closed by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[12:42] <mup> PR snapd#6026 closed: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <Merged by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[12:43] <mup> PR snapd#6026 opened: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[12:44] <mborzecki> so does it make any sense to push stuff now or not?
[12:47] <mup> PR snapd#6026 closed: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <Closed by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[12:49] <Chipaca> mborzecki: probably not
[12:49] <mup> PR snapd#6026 opened: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <Merged by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[12:49] <mborzecki> ehh
[12:49] <mborzecki> damn
[12:50] <mborzecki> hmm 2018-10-22 14:50:23 Cannot allocate google:ubuntu-18.10-64: cannot find any Google image matching "ubuntu-os-cloud-devel/daily-ubuntu-1810-cosmic-v20181002" on project "ubuntu-os-cloud-devel"
[12:51] <mup> PR snapd#6026 closed: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <Merged by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[12:51] <Chipaca> mborzecki: get master
[12:51] <Chipaca> mborzecki: that was fixed by the cachio late friday
[12:51] <mborzecki> ah ok
[12:51] <Chipaca> #6024
[12:51] <mup> PR #6024: tests: new cosmic image for spread tests on gce <Created by sergiocazzolato> <Merged by chipaca> <https://github.com/snapcore/snapd/pull/6024>
[12:52] <Chipaca> you'd call that "saturday"
[12:52] <Chipaca> :-)
[12:59] <mup> PR snapd#6026 opened: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <Closed by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[12:59] <zyga> yeah, mup, thanks for reminding us
[12:59] <mborzecki> probably integration hooks firing as they restore the data
[13:00] <zyga> feels like starting an old card with water instead of gas
[13:00] <mup> PR snapd#6026 closed: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <Merged by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[13:00] <zyga> *cough* *cough* maybe this time it will wrok
[13:00] <zyga> lol
[13:01] <mup> PR snapd#6027 closed: overlord/ifacestate: don't conflict on own discard-snap tasks when refreshing & doing garbage collection <Complex> <Squash-merge> <⚠ Critical> <Created by stolowski> <https://github.com/snapcore/snapd/pull/6027>
[13:01] <mup> PR snapd#6026 opened: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <Merged by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[13:02] <zyga> Chipaca: standup?
[13:02] <mup> PR snapd#6026 closed: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <Merged by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[13:03] <mup> PR snapd#6027 closed: overlord/ifacestate: don't conflict on own discard-snap tasks when refreshing & doing garbage collection <Complex> <Squash-merge> <⚠ Critical> <Created by stolowski> <https://github.com/snapcore/snapd/pull/6027>
[13:03] <mup> PR snapd#6026 opened: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <Closed by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[13:05] <mup> PR snapd#6026 closed: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <Merged by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[13:07] <zyga> holly smokes GH, calm down
[13:12] <mup> PR snapd#6027 closed: overlord/ifacestate: don't conflict on own discard-snap tasks when refreshing & doing garbage collection <Complex> <Squash-merge> <⚠ Critical> <Created by stolowski> <https://github.com/snapcore/snapd/pull/6027>
[13:13] <mup> PR snapd#6026 opened: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <Merged by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[13:14] <mup> PR snapd#6026 closed: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <Merged by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[13:15] <mup> PR snapd#6026 opened: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <Merged by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[13:16] <mup> PR snapd#6026 closed: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <Merged by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[13:16] <mup> PR snapd#6027 opened: overlord/ifacestate: don't conflict on own discard-snap tasks when refreshing & doing garbage collection <Complex> <Squash-merge> <⚠ Critical> <Created by stolowski> <https://github.com/snapcore/snapd/pull/6027>
[13:17] <mup> PR snapd#6026 opened: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <Merged by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[13:18] <zyga> https://media.ccc.de/v/ASG2018-173-libcapsule
[13:18] <zyga> I think mborzecki will find it interesting
[13:18] <mup> PR snapd#6026 closed: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <Merged by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[13:19] <mborzecki> zyga: thanks, will watch it
[13:21] <mup> PR snapd#6026 opened: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <Merged by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[13:22] <mup> PR snapd#6026 closed: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <Merged by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[13:22] <mup> PR snapd#6027 opened: overlord/ifacestate: don't conflict on own discard-snap tasks when refreshing & doing garbage collection <Complex> <Squash-merge> <⚠ Critical> <Created by stolowski> <https://github.com/snapcore/snapd/pull/6027>
[13:23] <mup> PR snapd#6026 opened: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <Closed by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[13:24] <mup> PR snapd#6026 closed: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <Closed by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[13:26] <ogra> looks like they are wiggling the cable at GH
[13:27] <mup> PR snapd#6026 opened: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <Merged by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[13:29] <mup> PR snapd#6026 closed: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <Merged by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[13:30] <mup> PR snapd#6026 opened: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <Merged by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[13:31] <mup> PR snapd#6026 closed: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[13:31] <mup> PR snapd#6027 opened: overlord/ifacestate: don't conflict on own discard-snap tasks when refreshing & doing garbage collection <Complex> <Squash-merge> <⚠ Critical> <Created by stolowski> <https://github.com/snapcore/snapd/pull/6027>
[13:33] <mup> PR snapd#6027 closed: overlord/ifacestate: don't conflict on own discard-snap tasks when refreshing & doing garbage collection <Complex> <Squash-merge> <⚠ Critical> <Created by stolowski> <https://github.com/snapcore/snapd/pull/6027>
[13:34] <mup> PR snapd#6027 opened: overlord/ifacestate: don't conflict on own discard-snap tasks when refreshing & doing garbage collection <Complex> <Squash-merge> <⚠ Critical> <Created by stolowski> <https://github.com/snapcore/snapd/pull/6027>
[13:41] <mup> PR snapd#6026 opened: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <Merged by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[13:42] <mborzecki> mup really likes that PR
[13:44] <mup> PR snapd#6026 closed: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[13:44] <mup> PR snapd#6027 opened: overlord/ifacestate: don't conflict on own discard-snap tasks when refreshing & doing garbage collection <Complex> <Squash-merge> <⚠ Critical> <Created by stolowski> <https://github.com/snapcore/snapd/pull/6027>
[13:46] <mup> PR snapd#6026 opened: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <Closed by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[13:47] <niemeyer> Yeah, something is not quite right there
[13:47] <mup> PR snapd#6026 closed: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[13:47] <niemeyer> Hello all
[13:47] <zyga> hey
[13:47] <zyga> GH is broken for the last ~14 hours
[13:48] <niemeyer> Wow.. that's a long trail at status.github
[13:48] <mup> PR snapd#6026 opened: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <Closed by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[13:48] <zyga> trail of fire
[13:49]  * Chipaca pushes his luck
[13:50] <zyga> I get 404 on pull request pages now
[13:50] <mup> PR snapd#6026 closed: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[13:50] <Chipaca> I just created #6028
[13:50] <ogra> at least you can play with your mouse with the 404 pic
[13:50] <Chipaca> … i'm feeling lucky
[13:51] <zyga> 404
[13:52] <mup> PR snapd#6026 opened: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[13:52] <Chipaca> I've got an idea
[13:53]  * Chipaca considers taking the afternoon off
[13:53] <zyga> hah
[13:53] <zyga> I was thinking the same thing
[13:53] <zyga> I can go on a bike
[13:53] <zyga> it's bright still
[13:53] <zyga> and not like gh is now back and working
[13:54] <zyga> btw, all systems go has plenty of other interesting videos\
[13:54] <zyga> I strongly recommend them
[13:54] <mup> PR snapd#6026 closed: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <Merged by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[13:54] <Chipaca> it's lovely out
[13:55] <Chipaca> I'll take the dog for a walk, then take the boys for a run, then go have tapas
[13:55] <zyga> enojy
[13:55] <Chipaca> I see *ZERO* problems with this plan
[13:55] <zyga> refresh
[13:55] <Chipaca> :-)
[13:55] <mup> PR snapd#6027 closed: overlord/ifacestate: don't conflict on own discard-snap tasks when refreshing & doing garbage collection <Squash-merge> <⚠ Critical> <Created by stolowski> <https://github.com/snapcore/snapd/pull/6027>
[13:55] <mup> PR snapd#6026 opened: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[13:55]  * Chipaca refreshes
[13:55] <zyga> self :)
[13:55] <Chipaca> zyga: still 404
[13:58] <mup> PR snapd#6026 closed: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <Closed by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[13:59] <ogra> i think mup would appreciate if the snap command wouldnt panic on "snap try" ...
[14:00] <ogra> (just a guess though)
[14:01] <seb128> Chipaca, bug 1773174 ... did the fix got merged? there has been a recent comment which seems to suggest it's still an issue (but that has no details on version used, distro serie, etc)
[14:01] <mup> Bug #1773174: Dutch lowercase translation warnings <amd64> <apport-bug> <bionic> <snapd (Ubuntu):In Progress> <https://launchpad.net/bugs/1773174>
[14:01] <mup> PR snapd#6026 opened: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <Merged by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[14:02] <mup> PR snapd#6026 closed: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <Closed by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[14:03] <mup> PR snapd#6027 closed: overlord/ifacestate: don't conflict on own discard-snap tasks when refreshing & doing garbage collection <Squash-merge> <⚠ Critical> <Created by stolowski> <https://github.com/snapcore/snapd/pull/6027>
[14:03] <mup> PR snapd#6026 opened: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[14:04] <Chipaca> seb128: the bug is in the translations in 18.10
[14:04] <Chipaca> seb128: when the bug was reported we filed suggestions in the translations thing
[14:05] <sborovkov> ogra, it's not possible to set force_turbo to 1 right now on the rpi, right?
[14:05] <Chipaca> seb128: last time i checked, two had not been reviewed yet
[14:05] <Chipaca> i thought i'd answered that person though
[14:05]  * Chipaca writes it out again
[14:06] <seb128> Chipaca, so you rely on ubuntu langpacks or how does it work?
[14:06] <mup> PR snapd#6026 closed: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[14:07] <Chipaca> ogra: can you mute mup for a bit?
[14:07] <Chipaca> i keep on getting pinged :-)
[14:07] <Chipaca> i could ignore him
[14:07] <Chipaca> hm
[14:07] <Chipaca> seb128: translations in ubuntu come from langpacks yes
[14:08] <Chipaca> at least that's my understanding
[14:08] <seb128> but snapd is not Ubuntu specific
[14:08] <seb128> you can't rely on the Ubuntu langpacks to be providing your .mo
[14:08] <mup> PR snapd#6026 opened: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <Merged by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[14:09] <Chipaca> seb128: but the bug is about ubuntu
[14:09] <mup> PR snapd#6026 closed: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <Merged by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[14:09] <mup> PR snapd#6028 opened: testutil, cmd/snap: introduce and use testutil.EqualsWrapped and fly <Created by chipaca> <https://github.com/snapcore/snapd/pull/6028>
[14:09] <sborovkov> ogra, would you accept PR that adds force_turbo to the list of rpi-config options. Looks like it's super critical for us to set it (most likely for others). Our rendering time when it's set goes from 32 to 16 ms per frame on the videos.
[14:10] <seb128> Chipaca, right, but I guess snapd source includes those translations, do you fix them directly there?
[14:10] <mup> PR snapd#6028 closed: testutil, cmd/snap: introduce and use testutil.EqualsWrapped and fly <Created by chipaca> <https://github.com/snapcore/snapd/pull/6028>
[14:10] <mup> PR snapd#6026 opened: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[14:11] <Chipaca> seb128: we sync them from launchpad, and the last pull we noticed we weren't getting the fixes so we also fixed them there, yes
[14:11] <seb128> k, good, thx
[14:13] <mup> PR snapd#6026 closed: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[14:14] <Chipaca> seb128: a little bit more info and my thoughts on this just added to the bug
[14:14] <Chipaca> (i thought i'd done it over the weekend, but must've gotten side-tracked before hitting submit)
[14:14] <mup> PR snapd#6027 closed: overlord/ifacestate: don't conflict on own discard-snap tasks when refreshing & doing garbage collection <Squash-merge> <⚠ Critical> <Created by stolowski> <https://github.com/snapcore/snapd/pull/6027>
[14:14] <mup> PR snapd#6026 opened: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[14:15]  * Chipaca adds mup to the ignore list
[14:15]  * Chipaca breathes in relief
[14:16] <mup> PR snapd#6026 closed: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[14:17] <seb128> Chipaca, thx
[14:18] <mup> PR snapd#6026 opened: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[14:20] <mup> PR snapd#6026 closed: cmd/snap: try not to panic on error from "snap try" <⚠ Critical> <Created by chipaca> <https://github.com/snapcore/snapd/pull/6026>
[14:22] <ogra> Chipaca, done (sorry, was in a call) ... a reminder later to unquieten it again would be nice (i might forget)
[14:23] <ogra> sborovkov, doesnt that void the warranty of the board ? (not sure, but i think i remember something like that)
[14:23] <sborovkov> nope
[14:23] <sborovkov> https://elinux.org/RPiconfig#force_turbo_mode
[14:24] <sborovkov> we can increase voltage and set this flag without voiding the warranty
[14:26] <ogra> sborovkov, well ... https://www.raspberrypi.org/forums/viewtopic.php?p=176865#p176865
[14:27] <ogra> looks like manually setting the single values doent void it but using the force_turbo option doe
[14:27] <ogra> *doesnt/does
[14:29]  * cachio afk
[14:29] <sborovkov> I am confused about how you word it :)
[14:29] <sborovkov> https://www.raspberrypi.org/documentation/configuration/config-txt/overclocking.md
[14:29] <sborovkov> this also states that setting only force_turbo is fine
[14:29] <sborovkov> and we don't really want to set anything else/overclock
[14:30] <ogra> force_turbo -> "Forces turbo mode frequencies even when the ARM cores are not busy. Enabling this may set the warranty bit if over_voltage_* is also set."
[14:30] <ogra> so you cant combine it with over_voltage_* stuff
[14:30] <sborovkov> right, but we are not going to do that
[14:31] <ogra> not sure if we offer any over_voltage settings in the core config ... if not, just adding force_turbo hould be fine
[14:31] <sborovkov> https://github.com/snapcore/core/blob/master/hooks/configure#L131
[14:31] <sborovkov> no over voltage
[14:31] <ogra> well, its not a question about what you do but about us offering a setting where you can void the warranty without any warning :)
[14:32] <sborovkov> sure, but is not it the user responsibility https://github.com/snapcore/core/pull/98
[14:32] <ogra> after all you could always add a hack that modifies the config.txt from the gadget ... since you own the gadget ... so we need to be sure what we offer for the general users is safe
[14:33] <sborovkov> ogra, no, core overwrites the config options
[14:33] <sborovkov> and can't users actually void warranty if they want :) it's their own device
[14:33] <ogra> sborovkov, i'd upvote the PR if GH weould not sshow me a 404 :)
[14:34] <ogra> they can ... but we dont really have a way to warn them if they just blindly call snap set
[14:34] <sborovkov> yeah I can't load it anymore
[14:34] <ogra> once GH is back to live i'll vote for it
[14:34] <sborovkov> hm, since this value is not in the list of supported options
[14:34] <sborovkov> if I set it in config.txt
[14:34] <sborovkov> core won't overwrite it, right?
[14:34] <ogra> yeah
[14:35] <ogra> it only touches stuff it knows
[14:35] <ogra> for everything else the gadget owner is the master
[14:36]  * zyga EODs and goes to take some time off from screens
[14:37] <sborovkov> ogra, the problem though is that if it's not in snapd we can't push out the change to the old users. even with gadget snap update
[14:37] <ogra> yep
[14:37] <ogra> i know :) ... so let get that change in
[14:37] <ogra> *letss
[14:37] <ogra> geez ! ... i hate my "S" key
[14:38] <ogra> (50% of the time it doesnt work, when it works it duplicates the char)
[14:38]  * Chipaca EODs as well
[14:38]  * Chipaca puts 20 "S" keys in the mail for ogra 
[14:38] <ogra> haha
[14:39] <ogra> i really dont get how i manage to kill every keyboard within a year ... i had a model-M for 10 year that never had issues ...
[14:39] <ogra> *yearss
[14:40] <ogra> (GRRR)
[14:40] <Chipaca> ogra: remap the s to the z and viceversa
[14:40] <Chipaca> ogra: zuddenly you'll be zuper zmart
[14:41]  * Chipaca runs away
[14:41] <sborovkov> ogra, at least you have one keyboard. on my laptop I had US keyboard. When I went for the battety replacement (on warranty_ they replaced it with a Russian keyboard where enter key is completely diffrent.
[14:43] <ogra> i have like 20 keyboards ... each with a different broken key though :)
[14:44] <sborovkov> and they told me that it's my problem that I don't like it... Nevermind that they sold me laptop with the US layout.
[14:44] <ogra> i just need to combine them into a single one one day
[14:44] <ogra> luckily my laptop kbd still fully works
[14:45] <ogra> but i prefer a proper mechanical keyboard with clicky switches and all
[14:55] <pstolowski> zyga: 6017 needs you re-review
[15:43] <zyga> Ack
[15:45] <zyga> pstolowski: can you reply to https://github.com/snapcore/snapd/pull/6017/files#r226451342
[15:46] <pstolowski> zyga: ah, thanks, got confused. applied.
[15:47] <zyga> pstolowski: approved now
[15:51] <pstolowski> thanks
[15:55] <pstolowski> cachio: ping
[16:06] <kyrofa> Hey there pstolowski, do you know if we have any docs about `assumes`?
[16:06] <pstolowski> kyrofa: no, degville may know?
[16:06] <pstolowski> kyrofa: and hi btw :)
[16:08] <degville> kyrofa / pstolowski: I've not seen any, actually.
[16:09] <kyrofa> Alright, thanks guys-- I'll experiment!
[16:13] <pstolowski> kyrofa: please document your findings ;)
[16:14] <kyrofa> pstolowski, overlord/snapstate/check_snap.go
[16:15] <kyrofa> It seems one can rely on both snapd versions as well as specific features, but that set of features has long languished
[16:15] <pstolowski> yeah i remember hearing about that, never used it nor seen in action
[16:16] <kyrofa> There also at first glance seems to be no way to list the features supported by your version of snapd
[16:16] <pstolowski> kyrofa: might be a good forum topic
[16:17] <kyrofa> I've never used it/seen it used either, but we're about to start using command-chain in snapcraft so we've started thinking about adding an assumes to essentially every snap. I'm getting increasingly nervous using a feature that no one uses though :P
[16:22] <kyrofa> pstolowski, mvo is it too late to get a PR adding a feature to the featureset into 2.36?
[16:22] <pstolowski> kyrofa: he is at the sprint in us this week
[16:22] <kyrofa> Ah yes, because zyga can't I suppose
[16:23] <pstolowski> indeed
[16:29] <kyrofa> pstolowski, what do YOU think about that? Not sure what your release process is
[16:31] <pstolowski> kyrofa: depends on the complexity/risk i suppose, at this moment we're trying to land fixes for last-minute critical release blockers found in last couple of days
[16:33] <cachio> pstolowski, hey
[16:33] <kyrofa> Well, I'll propose it anyway, would be nice to get it into the actual release that contains the feature, but will still be useful if not
[16:33] <pstolowski> cachio: hey, sent you an email
[16:35] <cachio> pstolowski, ok, I'll play with the nested vm to see if I can make the serial usb adapter visible
[16:36] <cachio> pstolowski, I'll ping you once I have some news
[16:36] <pstolowski> cachio: ok, please reply to the email if you have something, i'm about eod
[16:38] <cachio> pstolowski, sure
[16:39] <pstolowski> kyrofa: sure, do that
[16:40] <kyrofa> If github will actually work...
[16:44] <kyrofa> pstolowski|afk, https://github.com/snapcore/snapd/pull/6029, easiest review of your life
[16:46] <pstolowski|afk> kyrofa: ah, that looks simple and very safe indeed!
[16:52] <kyrofa> degville, by the way, how would you suggest handling documentation changes for an upcoming release? Wait until it's released and then update everything?
[16:58] <degville> kyrofa: I'd right the documentation anyway, if feasible, with a caveat or 'engineering' blockquote as a caveat.
[16:58] <degville> kyrofa: we could then remove the caveat on release, and add any new documentation to the outline (I wouldn't add them to the outline before features are available in stable).
[16:59] <degville> s/right/write <- terrible!
[16:59] <kyrofa> degville, what if it was an update to existing docs?
[16:59] <kyrofa> (something already in the outline)
[17:00] <degville> kyrofa: the current plan is to have both side-by-side, with a clear note saying "This is for version/upcoming version."
[17:00] <kyrofa> Alrighty, thanks!
[17:01] <degville> kyrofa: np. but really, whatever's easier to work with. If you wanted to create a separate post, that would work too. I could then work it into the docs when it's ready to go.
[17:31] <mvo> 6022 needs a second review - should be trivial :)
[17:31] <mvo> and good morning
[18:06] <kyrofa> Nooo, webhooks are down again
[18:56] <cjwatson> sergiusens: Uh, so do we have to finish the launchpad-buildd rollout as an emergency?  (bug 1791201)
[19:02] <kyrofa> cjwatson, I'm not sure what you've discussed in the past, but note that's only for bases
[19:04] <cjwatson> kyrofa: Doesn't the new version of snapcraft significantly change behaviour if SNAPCRAFT_BUILD_ENVIRONMENT=host isn't passed, then?
[19:05] <kyrofa> cjwatson, yes, but only if using bases
[19:05] <cjwatson> kyrofa: You're sure nobody's using base: 16?
[19:05] <cjwatson> sergiusens: Also, please don't mark launchpad-buildd bugs Fix Released.  That fix isn't rolled out yet
[19:08] <cjwatson> (base: core16, I mean)
[19:11] <kyrofa> cjwatson, such snaps fail to build as far as I'm aware, and don't install either. There are some using core18, but if I remember correctly they aren't using LP to build. sergiusens will of course know more
[19:12] <Gargoyle> Hey there.
[19:12] <kyrofa> Hey there Gargoyle, welcome
[19:15] <Gargoyle> This is currently the file dialogue for atom (and slack, so probably all electron apps). Is this something in my snapd setup that needs fixing or do the individual snaps need updating? https://www.dropbox.com/s/pblpsnbyvuvez1z/atom.png?dl=0 ( snap versions = https://paste.ubuntu.com/p/JG6FkgDZCK/)
[19:15] <cjwatson> kyrofa: Yeah, I know core18 won't work yet.  OK, maybe not an emergency then
[19:21] <kyrofa> Gargoyle, what does it look like normally?
[19:21] <kyrofa> Gargoyle, popey might be able to help here, he's much more familiar with those snaps
[19:23] <Gargoyle> kyrofa: It's missing any kind of colour, padding or icons compared to say LibreOffice dialogue.
[19:23] <Gargoyle> OK. Thanks. I'll wait and see if he chimes in.
[19:24] <kyrofa> Gargoyle, for what it's worth, the vscode dialog looks unremarkable to me: native. What OS are you on?
[19:26] <Gargoyle> Ubuntu 18.10.
[19:26] <Gargoyle> I'll throw a screen grab of LibreOffice for comparison.
[19:27] <Gargoyle> https://www.dropbox.com/s/hacpaoxi58djukq/lo.png?dl=0
[19:30] <kyrofa> Perhaps theming is having some issues on 18.10
[19:30] <kyrofa> (I'm on 18.04)
[19:33] <Gargoyle> Does anything theme wise in snapd rely on the system as it was when snapd or snaps were installed (I recently reverted back to ubuntu-session and removed gnome-session.)
[19:55] <indio> Hi. I'm on trisquel linux 8 which is package compatible with ubuntu xenial 16.04 and would like to install snapd. Since there's no snapd in trisquel repo I needed a snapd package from a PPA and the only one I could find is ppa:snappy-dev/edge. I just wanted to know if there is a stable PPA ? Thanks.
[20:21] <Saviq> cachio: hey, I saw you have a dedicated -nested-vm image for spread, is that something available in general for GCE or are you building this image yourself for this purpose?
[20:37] <sergiusens> cjwatson: sorry about that, was a glitch in my brain, I have the impression I quickly switched it back though, sorry if that was not the case
[20:39] <sergiusens> cjwatson: about `base: core16` or bases in general, I did have a conversation with wgrant here on how to move that forward, we need to iron it out a bit, but there is nothing to worry about today at all
[20:39] <cachio> Saviq, hey, I am building this vm
[20:39] <cachio> Saviq, kyrofa requested that for snapcraft
[20:39] <cachio> why?
[20:41] <kyrofa> Saviq, we're using it for build VM tests, using multipass. It's all mine though, you can't have it
[20:41] <Saviq> cachio: we'd use it for multipass with spread for sure, but we've had someone try multipass on GCE and I was wondering if nested vm is even supported by default
[20:41] <Saviq> cachio: what's special about it?
[20:42] <Saviq> kyrofa: I'll remember that! ;P
[20:42] <kyrofa> Saviq, :P
[20:42] <kyrofa> You have to enable it, cachio worked his magic: https://cloud.google.com/compute/docs/instances/enable-nested-virtualization-vm-instances
[20:42] <cachio> Saviq, nested vms are supported but if you want to use kvm you need to build an image for taht
[20:43] <Saviq> aha, interesting
[20:43] <cachio> Saviq, otherwise you are able to create a nested vm using qemu by default
[20:43] <Saviq> cachio: qemu without kvm, that is? so not really virtualization :)
[20:49] <cachio> Saviq, yes, kind of virtualization
[20:50] <Saviq> == emulation
[20:50] <Saviq> cachio: if I wanted to run spread tasks on GCE do I need to get added to the project or something?
[20:51] <cachio> Saviq, you want to use those images to run the spread tasks?
[20:53] <Saviq> cachio: yup
[20:54] <cachio> Saviq, so, you need just to use
[20:54] <cachio> image: ubuntu-1604-64-nested-vm
[20:54] <cachio> image: ubuntu-1804-64-nested-vm
[20:54] <cachio> for xenial and bionic
[20:55] <cachio> I'll create tasks to keep them updated next week
[20:55] <cachio> then you can use them normally
[20:57] <kyrofa> Saviq, for reference: https://github.com/snapcore/snapcraft/blob/master/spread.yaml#L37
[20:59] <Saviq> cachio: yeah, but to run that from my laptop?
[20:59] <Saviq> like I go to https://console.cloud.google.com/compute and I have no projects there, should I?
[21:01] <cachio> Saviq, you should have computeengine
[21:02] <cachio> Saviq, this is ou rproject
[21:02] <Saviq> ah maybe I should switch to the right account...
[21:03] <cachio> to the canonical one :)
[21:04] <Saviq> still, I can only create a new project, can't see any existing one
[21:04] <cachio> Saviq, did you see computeengine before?
[21:04] <Saviq> no
[21:04] <cachio> or it is the first time you try that
[21:05] <cachio> Saviq, in that case you need gustavo
[21:05] <Saviq> ack
[21:05] <Saviq> tx
[21:05] <cachio> Saviq, he manages the permissions, roles, etc
[21:06]  * cachio afk
[21:08] <niemeyer> Saviq: You were already in the account
[21:08] <niemeyer> Saviq: You should be able to login and use our project
[21:16] <Saviq> niemeyer: not sure what I'm doing wrong, then, I can only create a new project :/
[21:17] <niemeyer> Saviq: Well, you can do lots of things I'm sure :)
[21:17] <niemeyer> Saviq: The question would be why the one thing you can do, which is logging in with your Canonical credentials so you get proper spread access, not working?
[21:17] <niemeyer> Saviq: I'm out of context, though..
[21:18] <niemeyer> Saviq: What's failing?  Which error are you getting?
[21:18] <Saviq> niemeyer: I go to https://console.cloud.google.com/projectselector/compute/ and I can't see any projects
[21:18] <Saviq> (and if I create a project it wants my credit card :P)
[21:20] <niemeyer> Saviq: Yep, sounds expected
[21:20] <Saviq> oh ok I thought I should be able to see it there
[21:21] <niemeyer> Saviq: No, the role provides only enough permissions for Spread to work
[21:21] <Saviq> ack, trying that then
[21:31] <ackk> hi, is there a way to inject ssh config/keys into the vm used by snapcraft when building?
[21:33] <ijohnson> ackk: I don't know about the actual build VM work going into snapcraft 3.0, but I don't think there's a supported way for the lxd container that `snapcraft cleanbuild` creates, however if this is a git project you could store the credentials in a file that is ignored by git and have a part in the snapcraft.yaml that reads that file and uses it
[21:33] <ijohnson> ackk: there may be a way to configure the default lxd profile to contain what you need, I'm not sure though
[21:34] <ackk> ijohnson, but lxd is not the official way to build with 3.0 right?
[21:34] <ijohnson> yeah with 3.0 I think currently only multipass is supported, but I'm not familiar with how 3.0 works with the VM yet so I can't speak to that
[21:35] <ackk> ok, thanks
[21:36] <ijohnson> kyrofa may know
[21:42] <kyrofa> ackk, ijohnson indeed, I believe that's a problem today. I'm not sure what the ideal solution would be. sergiusens, any thoughts there?
[21:43] <kyrofa> It's not a problem we ever solved for cleanbuild, either
[21:44] <ijohnson> kyrofa: is there any obvious way that someone could accidentally leak credentials by storing such files in the source tree and using it in a part in snapcraft.yaml? I don't think that the sentry error reports include file contents, but I'm not sure
[21:44] <ijohnson> I don't think the manifest.yaml file would leak anything if they turned that on
[21:46] <ackk> ijohnson, in my case it's not credentials, I need to checkout a private branch using ssh keys
[21:46] <ackk> so the config is actually in .ssh/config
[21:46] <kyrofa> ijohnson, yeah I'm not sure what you mean, I'm just thinking of SSH keys as well
[21:46] <ackk> kyrofa, precisely
[21:46] <kyrofa> A short-term solution might be snapcraft bind-mounting that into place in the VM
[21:47] <kyrofa> But I figure there's a good reason we didn't do that for cleanbuild
[21:47] <kyrofa> Just not sure what it is :)
[21:47] <ackk> kyrofa, sigh. and cleanbuild is the only way to properly build a core18 snap right?
[21:48] <kyrofa> Build VMs, but yeah same concept
[21:48] <ijohnson> I guess I was just referring generally to the files like private ssh keys, etc. You could always have a part that copies the private key from your snapcraft tree into the containers ~/.ssh/
[21:49] <kyrofa> Yeah that might work around it for now. Would make me pretty nervous, make sure you filter it out
[21:50] <ijohnson> right my concern was rather that even if you filter it out and be careful that snapcraft doesn't automatically include the file contents in an oops report or something, subverting all your efforts to keep it safe
[21:50] <ackk> also not very generic, not everyone has the config and keys in the same place
[21:50] <kyrofa> Nah, those reports are pretty spartan, and aren't automatic unless you make it so
[21:51] <kyrofa> ackk, you can also use --destructive-mode which will run on the host like it does without bases, but then you exit supported territory
[21:51] <ijohnson> kyrofa: ack, good to know
[21:51] <kyrofa> ackk, I'm assuming you're using edge?
[21:54] <ackk> kyrofa, well I was trying edge yes. I'm currently using stable for builds
[21:56] <kyrofa> ackk, alright, yeah, on edge you can run `snapcraft --destructive-mode` and it won't spin up a VM, it'll run the build on the host. So you take responsibility for ensuring you're on the right host for the base, and make sure your environment isn't dirty, etc.
[21:57] <kyrofa> But then you have access to things on the host, like SSH keys
[21:57] <ackk> kyrofa, so that's the equivalent of the old plain "snapcraft" ?
[21:57] <kyrofa> Yeah, like running `snapcraft` without bases
[21:57] <ackk> I see
[21:58] <ackk> kyrofa, is there an ETA on when snapcraft 3.0 will be published to stable?
[21:58] <kyrofa> If you think you hit a bug in destructive mode, though, reproduce it in a build VM before reporting
[21:59] <kyrofa> ackk, not of which I'm aware beyond "soon", but it should be in candidate any time
[21:59] <ackk> kyrofa, cool, thanks
[22:02] <Saviq> cachio: any pointers on how to set up auth for spread on google? when I run spread it bails out pointing at https://developers.google.com/accounts/docs/application-default-credentials - that then redirects to https://cloud.google.com/docs/authentication/production... all of that seem to require me to be able to see the project, and being able to create a service account on it...
[22:02] <Saviq> ... but $ gcloud projects list
[22:02] <Saviq> Listed 0 items.
[23:19] <cjwatson> sergiusens: panic over then, thanks :-)  I will try to get that deployed this week though