[07:11] morning [08:03] morning [08:13] good morning pstolowski [08:16] mvo: pstolowski: morning [08:18] PR snapd#9864 closed: gadget/gadget.go: rename ubuntu-* to system-* in doc-comment [08:28] mvo: i've restarted https://github.com/snapcore/snapd/pull/9771 beacuse of some random unrelated failures, if it fails again, it'd be great to use your superpowers and land it [08:28] PR #9771: boot: boot config update & reseal [08:34] mborzecki: sure [08:38] PR snapd#9817 closed: cmd/snapd-generator: don't create mount overrides for snap-try snaps inside lxc [08:39] yay [08:43] pstolowski: do you think you could have a look at 9844 should be simple [08:43] pstolowski: and yes, YAY :) [08:43] yay^2 re snapshots PR [08:43] mvo: sure will take a look [08:43] PR snapd#9820 closed: o/snapshotstate: handle conflicts between snapshot forget, export and import [08:43] PR snapd#9866 closed: osutil/stat.go: add RegularFileExists [08:43] pstolowski: yeah, yay for finishing the snapshots, really nice, thanks again [08:47] mvo: i hope there are no more surprises there :} [08:56] mvo: one question to 9844 [08:56] pstolowski: thanks, looking [08:58] mvo: if amurray gets a chance to look at https://github.com/snapcore/snapd/pull/9865 soonish and it lands, maybe we could cherry pick that to 2.49? [08:58] PR #9865: interfaces/browser-support: allow sched_setaffinity with browser-sandbox: true [09:01] mborzecki: +1 - I think it has 2.49 already [09:01] yeah, added the milestone there [09:20] pstolowski: replied under https://github.com/snapcore/snapd/pull/9844#pullrequestreview-577107365 [09:20] PR #9844: cmd: make string/error code more robust against errno leaking [09:27] mvo: meh, failed again, can you land https://github.com/snapcore/snapd/pull/9771 ? [09:27] PR #9771: boot: boot config update & reseal [09:29] pstolowski: hi, is #9234 in your queue to look at again? [09:29] PR #9234: systemd/systemd.go: support journald JSON messages with arrays for values [09:44] pedronis: it escaped me, will look soon === alan_g_ is now known as alan_g [10:24] PR snapd#9771 closed: boot: boot config update & reseal [11:24] PR snapd#9862 closed: github, run-checks: do not collect coverage data on subsequent test runs [11:46] ijohnson, hi [11:46] dis you see the failure again? [11:46] the one you reported yesterday [11:46] do you have a link? [11:58] pedronis, mborzecki we discussed reworking how we resolve the kernel refs internally yesterday and the idea of something like LaidOutContent came up, it seems we could/should use LaidOutContnet (and maybe rename), a draft is here http://paste.ubuntu.com/p/nTMkM84W86/ but I want to double check with you first as there will be quite a bit of work updating the tests etc. I think it's a nice route. I decided to not create ResolvedContent in parallel [11:58] to LaidOutContent as we will also want to resolve kernel refs for raw content so it seems like using the struct for both is ok. but happy to change my mind, doing two different structures has some other upsides too. no rush, I have lunch now :) but thoughts would be great [11:58] mborzecki, pedronis maybe a quick chat after the standup or so [11:58] mborzecki mvo: security review done on PR #9865 :) [11:58] PR #9865: interfaces/browser-support: allow sched_setaffinity with browser-sandbox: true [11:58] * mvo hugs amurray [11:58] amurray: thank you! [11:59] thanks amurray ! [11:59] well that was an easy one - I wish all were as straight forward :) [12:29] PR snapd#9867 opened: overlord/devicestate: task for updating boot configs, spread test [12:40] mvo: can you land https://github.com/snapcore/snapd/pull/9844 ? the failures on centos and arch are unrelated [12:40] PR #9844: cmd: make string/error code more robust against errno leaking [12:42] ijohnson, there?= [12:46] hey cachio I'll be around a bit later [12:51] ijohnson, ok, thanks [12:51] I'll ping you later [12:59] PR snapd#9844 closed: cmd: make string/error code more robust against errno leaking [13:17] * pstolowski bbiab [13:40] PR snapd#9868 opened: tests: fix umount for snapd snap on fsck-on-boot test [13:45] PR snapd#9869 opened: cmd: make string/error code more robust against errno leaking (2.49) [13:50] re [13:55] PR snapd#9234 closed: systemd/systemd.go: support journald JSON messages with arrays for values [15:49] pedronis: I pushed a PR with the go-tpm2 update [15:50] PR snapd#9870 opened: vendor: update go-tpm2 to latest version [15:57] * cachio lunch [16:20] PR snapd#9871 opened: daemon: move query /snaps/ tests to api_snaps_test.go [16:30] PR snapd#9858 closed: cmd/snap-repair/runner.go: add SNAP_SYSTEM_MODE to env of repair runner [17:21] PR snapd#9871 closed: daemon: move query /snaps/ tests to api_snaps_test.go === strohalm is now known as strohi [17:33] ijohnson: I commented again/asked a question on https://github.com/snapcore/snapd/pull/9784/files#r565499762 [17:33] PR #9784: interfaces/builtin/network-setup-{control,observe}: allow using netplan directly [17:33] pedronis: ack I'll have a look [17:54] PR snapcraft#3415 closed: cli: enable SNAPCRAFT_TARGET_ARCH envvar matching --target-arch [17:59] PR snapcraft#3267 closed: ci: re-enable appveyor artifact collection [18:30] How doth one go about utilizing snap when building docker images? I'm trying to get chromedriver installed and it is only available via snap which is messing with automation a bit. [18:39] PR snapcraft#3432 opened: spread tests: remove legacy plugin tests [20:34] PR snapcraft#3433 opened: Allow revoking validation assertions (LP: #1912332)