[07:07] morning [07:09] good morning [07:10] hey mborzecki, mvo [07:10] Friday :) [07:10] zyga, mborzecki good morning! [07:10] hey guys [07:10] yeah, friday finally [07:11] mborzecki I spent some time on DCO checks recently [07:11] developer certificate of origin [07:12] sent some patches to https://github.com/christophebedard/dco-check/ which seems like a nice solution in _any_ CI [07:13] today is hopefully a slower day, I want to send some stuff to Debian for review / sponsorship [07:13] mostly python stuff related to REUSE [07:13] but I can check if spread is ready as well [07:13] (in the sense of dependencies) [07:15] zyga: hm it checks for signed-off-by in all commits? [07:16] in the relevant range [07:16] so new pushes [07:16] or what's in the MR [07:16] yeah [07:16] it's fairly nice and supports github and gitlab natively [07:16] (as in getting relevant information about the context before asking git anything) [07:16] PR snapd#9998 closed: tests: turn modules off explicitly in spread go unti test (2.49) [07:16] I've prepared a Debian package, fixed some things and maintain a minimal container [07:17] one of the things to upstream, but I think the last big bug needs fixing, and one more release is needed if you want to use it on a non-free gitlab instance with all the PR features it offers [07:21] mborzecki: 9976 has a conflict now [07:21] PR snapd#9983 closed: tests: use new commands of os.query tool on tests [07:21] PR snapd#9990 closed: tests: fix tumbleweed spread tests part 2 [07:21] PR snapd#9993 closed: tests/lib/prepare.sh: use /etc/group and friends from the core20 snap [07:22] mvo: ah, the tweak from ian landed, that's fine it should be a quick update [07:23] mborzecki: thank you! I want to push the PR count below 70 again today :) [07:27] mvo: and pushed [07:48] mvo: we should be able to land 2 more of my prs when the tests finish [07:50] mborzecki: yeah and a bunch of sergios stuff is relatively easy to review/land [08:05] morning [08:12] PR snapd#10003 opened: configstate: add config options for systemd-networkd and systemd-resolved [08:12] good morning pstolowski [08:17] PR snapd#10002 closed: gadget: simplify filterUpdate (thanks to Maciej) [08:19] mvo: some comments in https://github.com/snapcore/snapd/pull/10000 [08:19] PR #10000: client: protect against reading too much data from stdin [08:19] and wow, what a nice round PR # [08:19] pstolowski: hey [08:26] hmm our tests queue is a bit long atm apparently [08:37] mborzecki spawn more overlords, er... workers [08:40] mvo I plan to EOD early for day job today and look at https://github.com/snapcore/snapd/pull/9999 [08:40] PR #9999: snapstate: add "kernel-assets" to featureSet <β›” Blocked> [08:40] is this something I can test in practice or are some other pieces still unalinged? [08:41] zyga: we have no kernel/gadget yet but it's on my list for today [08:41] I would love to do a "field" upgrade of the broken PI [08:41] to all-new set [08:41] zyga: I plan to create updated gadget/kernel and then also update ubuntu-image [08:41] do we know if it will work in one reboot "hop?? [08:41] "? [08:41] oh [08:41] zyga: it will require two updates [08:41] right, more pieces [08:42] mvo two reboots or two updates? [08:42] zyga: but I think the gadget is a non-reboot one [08:42] zyga: so I *think* it's just one reboot [08:42] the reason I'm asking is that for everythting to work it has to be in sync with the kernel [08:42] now IIRC gadget/kernel update is that last element breaking pi [08:42] core18 is updating fine now [08:42] mvo anyway, I'm happy to have a look [08:42] I will try to EOD in 2-3 hours [08:42] need to record some demos today [08:43] zyga: nice [08:43] I've been working so late recently I have lots of "overtime" to burn [08:43] * zyga goes to his standup [08:43] I really really want our standups to be totally public at some point [08:43] being a weird non-business is good [08:44] zyga: heh, yeah, that makes sense [09:06] pstolowski: hi, did another pass on #9922, looking good but some comments [09:06] PR #9922: api: validation sets monitor mode [09:07] mvo: about https://bugs.launchpad.net/snapd/+bug/1916552 do you think it's some we break? afaict we only stage binaries from squashfs-tools [09:07] Bug #1916552: Snapcraft 4.5.1 - cannot pack β€œ/data/prime”: mksquashfs call failed: signal: segmentation fault (core dumped) [09:10] pedronis: thanks [09:17] PR snapd#10004 opened: asserts: mode where Database only assumes cur time >= earliest time [09:40] mborzecki: iirc sergio told me that using a different qemu fixed it but it's still strange [09:44] mborzecki: I commented a bit on #9940, a bit confused by of the code there though [09:44] PR #9940: boot: cmd/snap-bootstrap: handle a candidate recovery system v2 [09:44] *some of the code [09:44] pedronis: thanks, i'll take a look [11:01] hey folks, I want to add some spread tests for the vendored apparmor PR I am working on - and I want these to run against the snapd snap built from my PR itself - is there an existing example of this sort of thing? [11:02] PR snapd#9995 closed: tests: improvements for snap-seccomp-syscalls [11:35] pedronis: i've replied under https://github.com/snapcore/snapd/pull/9940#discussion_r588227927 let me know if that makes sens now, or maybe we should ahve a quick chat [11:35] PR #9940: boot: cmd/snap-bootstrap: handle a candidate recovery system v2 [11:38] mborzecki: I'm still confused [11:39] pedronis: a chat then? :) [11:39] yes [11:39] ok, heading to standup [11:39] I'm there === popey8 is now known as popey [12:03] uhh core prepare failed for me: https://paste.ubuntu.com/p/XNXkFgRXV6/ [12:05] mvo: can you use your superpowers and merge https://github.com/snapcore/snapd/pull/9976 ? [12:05] PR #9976: tests/unit/go: use tests.session wrapper for running tests as a user [12:05] the failures are unrelated afaitc [12:14] mvo: thanks! [12:17] PR snapd#9976 closed: tests/unit/go: use tests.session wrapper for running tests as a user [12:18] yw [12:23] PR snapcraft#3464 opened: meta: add support for `kernel.yaml` for kernel snaps [12:36] degville: I noticed in the whats new page a bit about the --experimental-gdb-server option, however for 2.50 we renamed that to just --gdbserver option and deprecated --gdb (though it will still be there), so maybe you could point out that in future releases --gdb will be deprecated in favor of the --experimental-gdb-server option (and also that --experimental-gdb-server will become --gdbserver)? [12:38] degville: also thanks for the edits to the snap try doc, looks really good to me! (though I fixed one little typo) [12:48] PR snapcraft#3458 closed: requirements: pip freeze [13:08] PR snapcraft#3302 closed: build providers: configure apt according to runtime environment arch [13:11] ijohnson: thanks for the gdb hint (and for looking over the what's new doc). I'll update the text and gdbserver page. And thanks for the typo fix :) [13:20] np, thanks for writing all that too :-) [13:22] mvo: I proposed the next piece as well, only a draft though because it's missing some unit tests [13:23] PR snapd#10005 opened: asserts: ReadSystemEssentialAndBetterEarliestTime [13:23] mvo: ^ [13:51] ijohnson: maybe you are aware of this but #9932 isn't blocked just needs reviews [13:51] PR #9932: o/configstate/configcore: support snap set system swap.size= [13:52] pedronis: yes I know I have some updates adding tests locally, I just haven't finished it yet [13:52] maybe today I will get to it [14:06] who wants to make me a cuda-runtime content snap? :-p [14:10] also, the snap admin pages get gateway timeout a LOT [14:11] e.g. https://snapcraft.io/fakecam/listing [14:26] mvo is that ldap bug important? [14:43] * cachio afk [14:44] zyga: a good question, it seems to be given that it blocks these people from using snaps [14:48] mvo: just curious because you've bumped priority to high from usual medium [15:23] PR snapd#10006 opened: [RFC] cmd/snap-bootstrap: refactor handling of ubuntu-save, do not use secboot's implicit fallback === pedronis_ is now known as pedronis [15:37] mborzecki: I did a first quick pass on #10006, some initial comments/questions [15:37] PR #10006: [RFC] cmd/snap-bootstrap: refactor handling of ubuntu-save, do not use secboot's implicit fallback [15:37] Bug #10006: python libglade program crashes on load [15:43] the kids are hijacking my desktop, bbiab [15:47] https://git.ostc-eu.org/OSTC/OHOS/components/staging/xts_acts/-/merge_requests/17/diffs#note_6899 [15:47] very creative use of HOST: [15:47] cachio ^ :) [16:24] zyga, hey [16:24] you can run any command in HOST [16:25] but first time I see someone use that [16:25] cachio I was thinking of using that more formally [16:25] with a host: section [16:25] that's like execute but runs for each task, before the files are sent, to the host [16:25] and captures errors, unlike $(HOST: ) [16:25] I guess it's specific to what we do [16:26] as or images are more embedded than traditional ubuntu [16:26] I wanted to ask for your opinion [16:26] and spread could warn the user that host commands exist [16:26] I think we don't use it [16:26] needing something like --classic [16:26] oh we use it, in spread.yaml [16:27] I wasn't even aware it is supported at the level of task.yaml [16:27] but it should be really usefull to skip tests based on values of variables [16:27] spread --enable-host-commands [16:27] (a bit too long but something of the sort) [16:27] and we don't need to run that in the target machine [16:27] that would then do test selection [16:27] and run host: commands in sub-directory of each test [16:27] e.g. we're using it to mkfs some images [16:27] that the target device mounts [16:28] but has no tools to create [16:28] I'll probably write something like that next week as we're using spread more and more now [16:28] hehehe [16:29] it would be nice to be able to build stuff and send it just to the instance which will run the test [16:29] I need to think possible use cases [16:29] in our case it's a bit weird [16:29] but I think i could be really usefull [16:29] and I agree spread doesn't fully match that [16:29] because the build happens elsewhere [16:29] on another machine [16:29] and we just get the image it produces [16:29] so the host running spread doesn't have bitbake or any related tooling [16:30] so it cannot compile all tests, for example [16:30] but that's fine, I think this is still a good way to use spread and extend it a little to this special-case) [16:30] yes, agree wiht that [16:48] mvo: a draft of the fix - https://github.com/snapcore/snapd/pull/10007 [16:48] PR #10007: o/configstate, o/snapshotstate: fix handling of nil snap config on snapshot restore [16:48] PR snapd#9974 closed: cmd/snap-bootstrap/initramfs-mounts: move time forward using ref files <β›” Blocked> [16:48] PR snapd#10007 opened: o/configstate, o/snapshotstate: fix handling of nil snap config on snapshot restore [17:28] is 2.5GB too big to upload to the store? [17:28] I'm receiving: `There seems to be a network error: ('Connection aborted.', ConnectionResetError(104, 'Connection reset by peer'))` [17:32] mvo: your last comment in #9914 has probably quoting problems [17:32] PR #9914: image: write resolved-content from snap prepare-image [17:33] mvo: ah, I could fix it (interestingly) [17:35] aah. getting a bit further on the fourth attempt [17:44] failed at the last hurdle - 99% then a 504 gateway timeout error [17:46] related. I've noticed a LOT of gateway timeouts when doing snap maintenance via snapcraft.io publisher's pages [17:54] posted a thread about timeouts https://forum.snapcraft.io/t/many-504-gateway-timeout-errors/23152 [18:00] hey diddledan :) [18:01] o/ [18:48] pedthe the last commit is the gadget.DefaultConstraints, maybe the one before? [21:08] PR snapcraft#3427 closed: extensions: make GNOME 3.38 stable [22:05] PR snapd#9987 closed: tests: improve tests documentation - part 1