[06:35] <mborzecki> morning
[06:40] <mborzeck2> damn isp
[07:33] <mup> PR snapd#7747 closed: gadget: skip fakeroot if not needed <Simple 😃> <Created by cmatsuoka> <Merged by bboozzoo> <https://github.com/snapcore/snapd/pull/7747>
[07:38] <zyga> hey
[07:38] <mborzecki> zyga: hey
[07:38] <zyga> mborzecki: check out "Sourcetrail"
[07:38] <zyga> it's FOSS just now
[07:38] <zyga> pretty neat IMO
[07:39] <mborzecki> zyga: hmmm 'something went wrong'
[07:39] <zyga> mborzecki: did you finish all of the HR training?
[07:39] <mborzecki> zyga: yup
[07:39] <zyga> https://github.com/CoatiSoftware/Sourcetrail
[07:39] <zyga> did you have any issues?
[07:39] <mborzecki> zyga: with the hr training?
[07:39] <zyga> I had to re-do one from scratch because the in progress version was stuck on last page without ability to "sign" the result
[07:40] <zyga> yes
[07:40] <zyga> I finished everything but more like at 1-2AM
[07:42] <mborzecki> zyga: so sourcetrail is like a better gnu global web mode?
[07:44] <zyga> I have no idea what that is
[07:44] <zyga> hey mvo
[07:44] <zyga> how did you sleep?
[07:50] <mvo> hey zyga ! much better. did stay up longer and had a relatively good sleep
[07:50] <mvo> zyga: and you?
[07:50] <mborzecki> mvo: hey
[07:51] <zyga> mvo: I managed to sleep at 2:30 - 3:00 AM
[07:51] <zyga> better than yesterday for sure
[07:52] <zyga> mvo: I shared this with Maciek earlier: https://github.com/CoatiSoftware/Sourcetrail
[07:52] <zyga> it's neat, I played with it a little
[07:53] <zyga> their website is slashdotted now
[07:53] <zyga> but should recover eventually
[07:53] <mvo> zyga: 2:30am - 3:00 am ? that is still not great :/
[07:53] <mvo> hey mborzecki
[07:53] <mvo> zyga: oh, nice
[08:03] <pstolowski> morning
[08:05] <mvo> hey pstolowski ! good morning
[08:06] <zyga> good morning pawel
[08:07] <mborzecki> pstolowski:  hey
[08:32] <zyga> mvo: I think I should take a swap day today
[08:32] <zyga> mvo: yesterday was okay to "burn" the day on HR and some random reviews
[08:32] <zyga> but today I feel so tired and sleepy, in the morning, that I really think I need to just take it easy and sleep/rest all day
[08:32] <zyga> and not pretend to work effectively
[08:33] <mvo> zyga: sure, thats fine
[09:16] <Mirv> if there's someone who is not really badly sleep deprived and has access to openSUSE Tumbleweed, please update to 20191116 and check if you can reproduce what I have bug #1853110
[09:16] <mup> Bug #1853110: On up-to-date openSUSE Tumbleweed all snaps show "broken" <snapd:New> <https://launchpad.net/bugs/1853110>
[09:16] <zyga> j,,
[09:16] <zyga> hmm
[09:17] <pstolowski> Mirv: hey! yes i'm actually looking at it right now
[09:18] <zyga> pstolowski: thank you
[09:18] <pstolowski> (it's my bug triaging day today)
[09:18] <Mirv> zyga: you are not counted into that someone according to log above :D take care.
[09:18] <Mirv> pstolowski: ok, thanks!
[09:18] <zyga> thank you so much guys
[09:18]  * zyga returns to cleaning the office 
[09:21] <Mirv> apparmor was updated but not sure what was changed https://lists.opensuse.org/opensuse-factory/2019-11/msg00264.html - that said, disabling apparmor does not seem to help me
[09:21] <pstolowski> Mirv: i'm installing tumbleweed atm as i don't have it handy
[09:22] <zyga> pstolowski: it eats gobs of space
[09:22] <zyga> pstolowski: using btrfs and snapshots
[09:22] <zyga> not very vm friendly
[09:22] <zyga> you may want to disable snapper (snapshot thing)
[09:23] <Mirv> ..or just select ext4 for everything in advanced setup instead of btrfs
[09:33] <pstolowski> zyga, Mirv good to know, thanks, yeah, too late to change fs, will look at disabling later
[09:49] <mvo> a second review for 7745 would be great
[09:50] <mvo> should be simple and will unblock 7746
[09:50] <zyga> mvo: let me do it
[09:52] <Mirv> pstolowski: so for example I've rocketchat-desktop installed, and with sudo mount /var/lib/snapd/snaps/rocketchat-desktop_97.snap /mnt I get: mount: /mnt: mount failed: Operation not permitted.
[09:52] <Mirv> I wish there was something meaningful in some log, but I can't find any
[09:54] <zyga> Mirv: look at audit log
[09:54] <zyga> Mirv: /var/log/audit/audit.log
[09:56] <Mirv> I tried, but I did not find other than "ype=AVC msg=audit(1574157270.914:590): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap.signal-desktop.signal-desktop" pid=7789 comm="apparmor_parser"" type of messages
[09:58] <zyga> that's odd
[09:59] <pstolowski> Mirv, zyga: i cannot reproduce the exact mount issue, but something is definately broken. all snaps get mounted, also after reboots. but i can get a snap to run only after i install it, and until reboot. after reboot i get "cannot change profile for the next exec call: No such file or directory
[09:59] <pstolowski> snap-update-ns failed with code 1: File exists" for all snaps
[09:59] <zyga> pstolowski: did you enable snapd.apparmor.service?
[09:59] <pstolowski> profiles seem to be in place, snaps mounted
[09:59] <zyga> it's part of the install docs
[10:00] <pstolowski> ah, i missed that
[10:00] <zyga> mvo: https://github.com/snapcore/snapd/pull/7745#pullrequestreview-318910411 + 1
[10:00] <mup> PR #7745: snap-bootstrap: add go-flags cmdline parsing and tests <Created by mvo5> <https://github.com/snapcore/snapd/pull/7745>
[10:01] <mup> PR snapd#7745 closed: snap-bootstrap: add go-flags cmdline parsing and tests <Created by mvo5> <Merged by zyga> <https://github.com/snapcore/snapd/pull/7745>
[10:02] <mvo> zyga: thank you!
[10:04] <pstolowski> zyga: right that was it
[10:05] <mvo> also 7712 needs a second review (a bit more work but really important to move forward with uc20)
[10:06] <pstolowski> Mirv: ok, cannot reproduce on fresh install, wonder what when wrong on your box. do you have everything updated, no held dependencies etc?
[10:06] <Mirv> I do see "missing file /snap/.../meta/snap.yaml" type of messages but that's obvious since nothing is mounted, it's just annoying that regarding the "Operation not permitted" I'm not finding anything, and sudo systemctl stop apparmor + sudo systemctl stop snapd.apparmor do not help so it does not seem to be apparmor that's denying the permission (also as nothing is in audit.log)
[10:07] <pstolowski> Mirv: the fact you cannot even mount .snap manually is a key, that's pretty weird
[10:07] <Mirv> pstolowski: :( everything is updated, nothing seems to be held
[10:08] <Mirv> pstolowski: yes it is
[10:08] <Mirv> squashfs is installed, that's one thing that I thought about
[10:08] <pstolowski> Mirv: that's not even a snapd issue but something more fundamental
[10:08] <pstolowski> Mirv: is it a standard suse kernel?
[10:09] <Mirv> pstolowski: standard yes. but I have another TW laptop at 20191112, I'll update that one too and see if it gets broken or not
[10:10] <pstolowski> Mirv: also, can you try mount -v /var/lib/snapd/snaps/rocketchat-desktop_97.snap /mnt (-v for verbose)
[10:11] <Mirv> pstolowski: not anymore verbose with that
[10:12] <Mirv> pstolowski: ah, it's loop devices broken, somehow.. I can't mount an iso either
[10:13] <Mirv> but yes this is not snapd anymore
[10:13] <mup> Bug #1853122 opened: Facing requires classic confinement error <Snappy:New> <https://launchpad.net/bugs/1853122>
[10:13] <zyga> Mirv: losetup -a?
[10:13] <zyga> maybe you ran out of loopback devices
[10:14] <Mirv> zyga: empty
[10:14] <zyga> can you try:
[10:15] <zyga> Mirv: losetup -f /path/to/a/squashfs/file/
[10:15] <zyga> (as root)
[10:15] <zyga> perhaps also with -r for --read-only
[10:15] <Mirv> hmm, losetup: cannot find an unused loop device
[10:15] <zyga> so that's the problem
[10:16] <zyga> can you strace it?
[10:17] <Mirv> yep, and from there I can see that there's nothing ls /dev/loop*
[10:17] <zyga> do you have loop-control?
[10:17] <Mirv> not even that
[10:17] <zyga> I don't know what makes it
[10:17] <zyga> on my system that is 10:237
[10:23] <pstolowski> Mirv: thanks for updating the bug report!
[10:24] <Mirv> pstolowski: sorry for taking your time :( it very effectively seemed like "snapd broken" for a long time..
[10:25] <Mirv> so currently I've filed openSUSE bug report, but then again my other laptop did not break. mknod /dev/loop-control c 10 237 helps. I'll follow up on the more relevant channels, maybe of course snapd current report a bit more if loop devices are broken.
[10:25] <mup> Bug #1853122 changed: Facing requires classic confinement error <snapd:New> <https://launchpad.net/bugs/1853122>
[10:25] <zyga> pstolowski: consider adding a check that /dev/loop-control exits and has major/mior
[10:26] <zyga> sanity check, that is
[10:26] <pstolowski> zyga: exactly
[10:26] <pstolowski> Mirv: no worries. we do some sanity checks, and i think this problem highlights one other potential problem that we may want to check
[10:39] <xnox> Chipaca:  mvo: https://raw.githubusercontent.com/snapcore/pc-amd64-gadget/20/grub.cfg-recovery  note improvements 1) variables select the default entry by id 2) all recovery systems are enumerated 3) entries are created per-mode / per-system 4) no idea what duplicate hotkeys will do 5) added menuentry to go back to UEFI setup, as my VM is too quick
[10:39] <xnox> it's kind of evolution of previous globgging, with type entries.
[10:40] <xnox> and the cmdline is now correct.
[10:41] <xnox> i was thinking that load_env --file /systems/$snapd_recovery/grubenv could e.g. declare the modes that are supported, and then generate entries for modes that a given recovery system can do?
[10:41] <Chipaca> xnox: I too was thinking of an env per system
[10:41] <mvo> xnox: sounds good! should we handle this stuff via PRs or do you prefer to commit directly to master?
[10:42] <xnox> it was a rewrite, thus i just pushed it to master
[10:42] <Chipaca> xnox: i'm not sure the logic for default= is sane there though
[10:43] <Chipaca> xnox: shouldn't that be set after the loop?
[10:43] <xnox> Chipaca:  mvo: we were meant to have design for the boot menu right....? because it matters what order things are shown, what the text / hotkeys are, what they do, how they are grouped.
[10:44] <xnox> Chipaca:  it is set if there is a default provided in the global env (i.e. boot that next); otherwise it is set each time a new better system is found.
[10:45] <xnox> mvo:  Chipaca: and we need to like search for ubuntu-boot and add entry to chainload "normal mode" grub right?
[10:46]  * xnox also dislikes run/recover. I would prefer "normal/recover/install" such that hotkeys are unique: n r i
[10:47] <mvo> xnox: I pushed https://github.com/snapcore/core20/pull/13 with a very first draft of the separation of writable-path from initramfs. its the old code almost untouched. I will look to add tests and then we can start refactoring I think
[10:47] <mup> PR core20#13: handle-writable-paths: extract the writable-path handling <Created by mvo5> <https://github.com/snapcore/core20/pull/13>
[10:47] <mvo> xnox: but its what you had in mind, rightß
[10:47] <mvo> ?
[10:48] <mvo> niemeyer: it would be great if https://github.com/snapcore/core20/ pull requests could be added to mup
[10:48]  * mvo needs to step out for ~10min
[10:48] <niemeyer> mvo: Heya
[10:48] <niemeyer> mvo: Sure, will do
[10:50] <xnox> mvo:  yes, that is the right approach, and a good starting point. It shouldn't live in /etc though, and can always iterate that once we create it as an entry point.
[11:05] <pstolowski> Chipaca: hey, why was this assigned to some other team? https://bugs.launchpad.net/snapd/+bug/1851480
[11:05] <mup> Bug #1851480: Hooks are not included in slot/plug label expressions <snapd:Confirmed for glancr> <https://launchpad.net/bugs/1851480>
[11:08] <zyga> pstolowski: community
[11:11] <pstolowski> zyga: someone specific is going to fix it?
[11:11] <mvo> xnox: yeah, do you prefer /usr/lib/something/handle-writable-path?
[11:12] <Chipaca> pstolowski: that's dot-tobias
[11:12] <pstolowski> Chipaca: ah, ok
[11:12] <xnox> mvo:  /usr/lib/core/handle-writable-paths yeah
[11:13] <Chipaca> pstolowski: they said on 2019-11-07 they'd get to it "next week", and that they'd report progress
[11:13] <Chipaca> pstolowski: so maybe it's time to jiggle the plug
[11:14] <mvo> xnox: cool, will move it over
[11:16] <zyga> pstolowski: yes, though please reassign if you want to fix it sooner
[12:09] <mup> PR snapd#7749 opened: tests: restart the snapd service in the snapd-failover test <Created by mvo5> <https://github.com/snapcore/snapd/pull/7749>
[12:13] <cachio>  mvo hey
[12:14] <cachio> #7749 is to fix the issue I raised about that test on pi3?
[12:14] <mup> PR #7749: tests: restart the snapd service in the snapd-failover test <Created by mvo5> <https://github.com/snapcore/snapd/pull/7749>
[12:16] <mvo> cachio: it *could* be related but it was the outcome of a discussion with mborzecki about the snapd failover robustness and we wanted to make sure our tests are complete (i.e. testing that we didn't just restart into the right snapd but also ensuring that its stable accross the restart)
[12:16] <mvo> cachio: you need to remind me about this pi3 issue, I don't recall :/
[12:17] <cachio> mvo, sure
[12:17] <cachio> I see this error https://paste.ubuntu.com/p/xBhPYrjfVf/
[12:18] <mup> PR snapd#7750 opened: sanity: check /dev/loop-control device as part of sanity checks <Created by stolowski> <https://github.com/snapcore/snapd/pull/7750>
[12:18] <cachio> mvo, It happens after we install the broken snapd
[12:20] <mup> PR snapd#7712 closed: seed: support in Core 20 seeds local unasserted snaps for model snaps <Priority 🏇> <Created by pedronis> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/7712>
[12:21] <mvo> cachio: thanks, thats interessting. is this happening all the time or just sometimes?
[12:21] <cachio> mvo, all the time
[12:23] <mvo> cachio: do you know when this started to happen?
[12:24] <mvo> cachio: or is it happening since forever?
[12:24] <mvo> cachio: also I assume this happens on all the Pis, not just pi3, pi2 as well?
[12:25] <cachio> mvo, checking logs
[12:26] <mvo> cachio: thank you, no rush, I get lunch now but that is interessting, I wonder if there is a race with that path
[12:28] <cachio> mvo, 2.42 execution
[12:28] <cachio> first time I saw that
[12:28] <cachio> I raised the issue at that moment
[12:29] <cachio> and then I did a manual execution to get more info
[12:29] <cachio> last week
[12:30] <cachio> mvo, I mostly reproduced that on pi3
[12:31] <cachio> on pi2 not sure
[12:32] <cachio> just once on pi2, it was during 2.42.1
[12:37] <cachio> mvo, it is not happening all the time on pi3
[12:37] <cachio> mvo, this is an execution during last week https://trello-attachments.s3.amazonaws.com/5da8bc830df86851446e9d4e/5dcf78cb5984618fb21cd5d7/1a9b05bfb0491c8faad045fc9f6143d3/snapd_2.42.1%2Bgit1140.g9173632_(5459)_pi3-refresh-18_arm32.log
[12:38] <cachio> this is all stable + snapd from edge
[12:38] <cachio> and it works well
[12:50] <pstolowski> cachio: is this still the case https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1852635 ?
[12:50] <mup> Bug #1852635: mount-ns test failing with latest bionic updates <snapd (Ubuntu):New> <https://launchpad.net/bugs/1852635>
[12:52] <cachio> pstolowski, yes
[12:52] <cachio> pstolowski, this is the last log https://travis-ci.org/snapcore/spread-cron/builds/613333438
[12:53] <cachio> from yesterday
[12:53] <pstolowski> cachio: ok, thanks, will investigate
[12:53] <cachio> pstolowski, thanks
[13:48] <mvo> cachio: thank you! interessting find, I wonder what is going on there, our code did not change in a while, maybe systemd did change somehow
[14:09] <mborzecki> pstolowski: https://devfest.withgoogle.com/#devfest-map try poland
[14:09] <pstolowski> mborzecki: thanks
[14:22] <mup> PR snapd#7748 closed: overlord: fix the get command help message <Simple 😃> <Created by cmatsuoka> <Closed by cmatsuoka> <https://github.com/snapcore/snapd/pull/7748>
[14:24] <pstolowski> cachio: fwtw i run spread -debug google:ubuntu-18.04-64:tests/main/mount-ns and it didn't fail
[14:31] <mborzecki> cachio: pstolowski: do you have the log?
[14:33] <pstolowski> mborzecki: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1852635
[14:33] <mup> Bug #1852635: mount-ns test failing with latest bionic updates <snapd (Ubuntu):Confirmed> <https://launchpad.net/bugs/1852635>
[14:37] <mup> PR snapd#7751 opened: cmd: fix the get command help message <Simple 😃> <Created by cmatsuoka> <https://github.com/snapcore/snapd/pull/7751>
[14:37] <cmatsuoka> mborzecki: did it over in the right message: https://github.com/snapcore/snapd/pull/7751
[14:37] <mup> PR #7751: cmd: fix the get command help message <Simple 😃> <Created by cmatsuoka> <https://github.com/snapcore/snapd/pull/7751>
[14:38] <cachio> pstolowski, are yo uusing the image test-bionic-1 ?=
[14:40] <cachio> mborzecki, this is the last error https://travis-ci.org/snapcore/spread-cron/builds/613333438#L1850
[14:41] <mborzecki> cmatsuoka: thanks, will take a look
[14:42] <pstolowski> cachio: no, how do you mean?
[14:43] <cmatsuoka> mborzecki: thanks for noticing that, I grepped for the faulty message and I think I didn't expect more than one instance
[14:45] <pstolowski> cachio: ah, you mentioned it in the beginning of output in the bug report
[14:46] <pstolowski> cachio: how do i get it?
[14:48] <ijohnson> mborzecki: regarding epochs on #7431, I don't think we should do anything for that, AFAICT it should just work with epochs, my gut feeling is that if there is something special that should happen with disabled services and epochs the "transitioning" snap between epochs should take care of that in post-refresh, pre-refresh hooks IMHO
[14:48] <mup> PR #7431: overlord/snapstate: don't re-enable and start disabled services on refresh, etc <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/7431>
[14:48] <ijohnson> anyways do you think I'm ok to land that PR now since it's green? (CC mvo)
[14:49] <ijohnson> mvo: also should we get a +1 from jdstrand on #7731 before merging?
[14:49] <mup> PR #7731: usersession/userd: add "apt" to the white list of URL schemes handled by xdg-open (LP: #1776873) <Created by oSoMoN> <https://github.com/snapcore/snapd/pull/7731>
[14:50] <mvo> ijohnson: yeah, a review for 7731 from jdstrand would be great, should be fine but best to double check with him
[14:50] <ijohnson> ack
[14:51] <mvo> ijohnson: let's merge 7431, it got two +1 and conceptually samuele had looked at it so AFAIK we should not block on him
[14:52] <cachio> pstolowski, I created it by updating and upgrading bionic and then rebooting it
[14:52] <ijohnson> \o/ I'm on it
[14:52] <mvo> ijohnson: great, thanks for this one!
[14:53] <mup> PR snapd#7431 closed: overlord/snapstate: don't re-enable and start disabled services on refresh, etc <Created by anonymouse64> <Merged by anonymouse64> <https://github.com/snapcore/snapd/pull/7431>
[14:53]  * ijohnson can't wait for pstolowski to rewrite all of that code for preseeding and review it all again
[14:53] <mup> PR snapcraft#2809 opened: project-loader: address errors from mypy uprev <Created by cjp256> <https://github.com/snapcore/snapcraft/pull/2809>
[14:54] <pstolowski> ijohnson: yay
[15:14] <ijohnson> pstolowski: I'm not quite done going through my backlog of forum/email/github notifications, did you submit a PR adding 'k' to the serial-port apparmor rules? If not I can do that
[15:14] <ijohnson> looks like jdstrand gave a +1 to adding 'k' to the rule
[15:14] <ijohnson> https://forum.snapcraft.io/t/not-able-to-start-configure-custom-built-ubuntu-core/14142/23?u=ijohnson
[15:16] <pstolowski> ijohnson: he did, but he also said he was going to do it afaiu
[15:17] <ijohnson> ah I see his other comment now, nvm :)
[15:18]  * cachio lunch
[15:19] <mup> PR snapd#7752 opened: tests: enable degraded test on arch linux after latest image updates <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/7752>
[15:19] <mborzecki> ijohnson: yeah, i was wondering about the snap service naming, it's totally up to whoever builds the snap, so you can have a service named A, then the user disables it, the publisher renames A to B, the user proceeds to disable B, then A returns as something completely new and gets disabled because we carry the history of the disabled service names, but it a corner case so meh ;)
[15:21] <ijohnson> well the question I would have is when you say "A returns as something completely new", how do you qualify something completely new? :-) it has the same name, so the publisher probably intended some kind of connection between the first service and it's reincarnation
[15:21] <ijohnson> but yes that is a corner case
[16:35] <mup> PR snapcraft#2810 opened: build-providers: address errors from mypy uprev <Created by cjp256> <https://github.com/snapcore/snapcraft/pull/2810>
[16:40] <ijohnson> Chipaca: I think the snapd REST API wiki docs need an update, see https://forum.snapcraft.io/t/facing-requires-classic-confinement-error/14163
[16:40] <Chipaca> hmm
[16:40]  * Chipaca looks
[16:41] <Chipaca> ijohnson: oh, doc seems to be wrong, not outdated
[16:42] <ijohnson> wrong == outdated ?
[16:44] <Chipaca> ijohnson: /v2/snaps never took options
[16:44] <ijohnson> right got it
[16:44] <Chipaca> so all those options descriptions should be on /v2/snaps/<snap>
[17:14] <Chipaca> augh
[17:14]  * Chipaca takes a break
[17:21] <ijohnson> degville, when you get a chance can you take a look at making the docs changes for https://bugs.launchpad.net/snapd/+bug/1612440 ?
[17:21] <mup> Bug #1612440: Full systemd socket activation support <lxd> <Snapcraft:New> <snapd:Fix Released> <https://launchpad.net/bugs/1612440>
[17:23] <degville> ijohnson: will do, thanks for letting me know.
[17:29] <ijohnson> thanks!
[17:41] <jk0ne> Hello!  I am beginning an upgrade of the snapcraft forums.  The forum will be in read-only mode until this is completed.  ETA: less than one hour.
[17:53] <Chipaca> EOD for me it is
[17:53] <Chipaca> 👋
[18:32] <jk0ne> forum.snapcraft.io has been upgraded. Maintenance is complete.
[18:32] <mup> PR snapcraft#2811 opened: extractors: address errors from mypy uprev <Created by cjp256> <https://github.com/snapcore/snapcraft/pull/2811>
[18:39] <degville> thanks jk0ne!
[18:46] <ogra> hmm
[18:46] <ogra> jk0ne, not sure if that was your intent ... https://imgur.com/a/es4hRK9
[18:47] <ogra> (has anyone else lost all CSS from the forum ?)
[18:48] <ogra> bah ... ok, now it is back but i'm hard logged out ...
[18:48] <ec0> looks OK here
[18:48] <ogra> (and cant remember my credentials since the silly forum doesnt use SSO)
[19:03] <jk0ne> ogra: I think you might have hit it during the actual reload.  Let me know if you are seeing issues still.
[19:15] <ogra> jk0ne, nope, seems ok now
[19:17] <jk0ne> glad to hear
[23:24] <mup> PR snapcraft#2812 opened: store: address errors from mypy uprev <Created by cjp256> <https://github.com/snapcore/snapcraft/pull/2812>
[23:39] <mup> PR snapcraft#2813 opened: pluginhandler: address errors from mypy uprev <Created by cjp256> <https://github.com/snapcore/snapcraft/pull/2813>