/srv/irclogs.ubuntu.com/2020/08/04/#snappy.txt

mborzeckimorning05:37
mborzeckimvo: hey06:48
mvogood morning mborzecki06:51
mborzeckimvo: i've pushed an update to arch, and working on updates for fedora06:53
mvomborzecki: nice, thank you06:55
pstolowskimorning07:05
mborzeckipstolowski: hey07:07
jameshmvo: it looks like the edge channel for the core snap hasn't published for a while, and doesn't seem to reflect master.  Is that a known problem?07:32
mvojamesh: we need jdstrand to unblock publication, the review tools flaged edge incorrectly07:37
mvojamesh: or some other store reviewer for that matter07:37
mupPR snapd#8917 closed: osutil/disks: add mock disk and tests for happy path of mock disks <Squash-merge> <UC20> <⛔ Blocked> <Created by anonymouse64> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/8917>07:42
zygagood morning08:36
zygamvo I'm filing the paperwork now08:36
mupPR snapd#9088 opened: cmd/snap-preseed: use snapd from the deb if newer than from seeds <Preseeding 🍞> <Created by stolowski> <https://github.com/snapcore/snapd/pull/9088>08:37
zygapedronis thank you! :)08:39
pedronismvo: I approved that core revision09:22
mvopedronis: thank you09:22
mvopedronis: there might be more to approve https://dashboard.snapcraft.io/snaps/core/revisions/9810/09:31
pedronisthere's a lot of them09:33
pedronislet' see09:33
mvopedronis: yeah, I think you will have to approve 5 or so and then it should have recovered (one approval for each arch)09:34
=== Haxxa is now known as Guest846
pedronismvo: I think now I approved all archs once, let's see09:47
mvopedronis: thank you! fwiw, I'm working on 8982 right now, it needs some tweaks for not leaking FDs in the error case now that the export is split09:50
ijohnsonmorning folks09:53
mvogood morning ijohnson09:54
ijohnsonhey mvo09:54
ijohnsonmvo: thanks for merging 8917, but I don't suppose you saw the squash merge label for that PR ?09:55
ijohnsonit's not a big deal, just a little messy now IMHO09:55
pedronismvo: the subsequent revisions are getting green on their own now09:57
* pedronis lunch09:57
mvoijohnson: oh no, sorry for that09:58
mvopedronis: great, thank you09:58
ijohnsonmvo: no worries, just my OCD wanting to have a clean git history without all my silly "merge feature X into feature Y" and "merge master into feature Y" commits10:00
pstolowskihey ijohnson !10:04
ijohnsonhey pstolowski10:04
ijohnsondid you try out the ubuntu-bartender thing at all? no worries if you didn't, happy to show you how I debugged things with that in a little bit10:04
pstolowskiijohnson: no, not yet, since you mentioned you needed manual hacks i assumed it makes sense to wait for you10:14
ijohnsonpstolowski: sure, do you wanna join the SU HO in 45 minutes ?10:15
pstolowskiijohnson: yes, sure10:15
ijohnsonsounds good10:15
jameshThe access check attributes on snapFileCmd ("/v2/snaps/{name}/file") don't really make sense.  From what I can see, the polkit action it specifies will never be used10:20
pstolowskiijohnson: i've a small interruption here, may need 15 or so, can i ping you when ready for HO?10:55
ijohnsonsure no worries10:55
zygao/10:57
ijohnsonhey zyga how are you feeling ?10:57
zygaI'm in the office, training my legs to stand and ... just do that10:57
zygamuch better, stronger by the day10:57
ijohnsonnice that's really great to hear10:58
zygastill pathetically weak but making progress :)10:58
zygastarting Wednesday I should be able to sit for more than half an hour, or so the doctors tell me10:58
zygahow have you guys been?10:58
ijohnsonthings are going well I think, not too many fires10:58
zygathat's great10:59
zygahow are tests?10:59
zygais everything working okay?10:59
zygaI rebooted our instance after boot loader patches went out10:59
ijohnsonnot too bad actually, not that much "actions missing in action" kinda thing10:59
ijohnsonstill some red from uc20 prepare and store 408s randomly11:00
ijohnsonbut the tests seem to be syncing up properly which is good11:00
zygaok11:01
zygathat's great to hear11:01
zygamy goal for today is to sent some docs to mvo11:01
zyga(done)11:01
zygaand to exercise (in progress)11:01
ijohnsonnice11:01
zygaand to see a bit more about my branches (bonus)11:01
zygaI'll try to address the feedback you gave me11:01
zygaI'm off until Thursday11:01
zygabut I'll try to help a little11:01
pstolowskihey zyga, glad to hear your condition is improving11:06
zygayeah, :-)11:06
zygamy daughter told me that I move like my father (who is old and moves slowly :)11:07
pstolowskiouch11:08
* zyga break 11:27
zygatired o/11:27
pstolowskiijohnson: sorry, it took a bit longer; can we talk now?11:41
ijohnsonpstolowski: sure, give me 5 minutes I want to start flashing my SD card, it takes a bit to finish11:41
pstolowskiijohnson: sure11:41
ijohnsonpstolowski: ok ready joining the HO now11:46
pstolowskiijohnson: ok11:46
mborzeckipedronis: 13 files changed, 315 insertions(+), 51 deletions(-) just the writer & bits in gadget/install, devicestate install and stubs in boot12:01
mborzeckipedronis: not great, but not horrible either12:01
mborzeckithe tests inflate the diff a bit12:02
pedronismborzecki: sounds ok12:02
* pstolowski lunch12:09
mupPR snapd#9089 opened: many: introduce content write observer, install mode glue, intial seal stubs <UC20> <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/9089>12:33
mborzeck1pff chrome died at the end of standup13:34
=== mborzeck1 is now known as mborzecki
mupPR core20#79 closed: Add secureboot-db package, try #2 <Created by xnox> <Merged by xnox> <https://github.com/snapcore/core20/pull/79>13:47
=== mborzeck1 is now known as mborzecki
jdstrandmvo: I'm looking and it looks like Samuele approved core so you are set. you said it was flagged incorrectly, but it dropped a file. I think the review-tools dtrt?14:00
mvojdstrand: yeah, all good, thanks!14:00
mvojdstrand: (in a meeting, will get back to you)14:04
jdstrandmvo: no worries, just wanted to make sure everything was ok. thanks!14:06
mvojdstrand: yeah, I think the issue was that edge go a (much older) core and then we got the new version. this lead to the review-tools flagging I think14:08
jdstrandmvo: yes, that can definitely happen as the review-tools (and the store at the point that the tools are run) have no concept of 'edge' or 'stable'14:09
jdstrandmvo: we now have a role rotation for store manual reviews, so we should in theory be more proactive, but you can always reach out :)14:10
mborzeck1hmm 2020-08-04T13:37:42.0599670Z Failed for "gopkg.in/yaml.v2" (failed to clone repo): exit status 12814:19
mborzeck12020-08-04T13:28:36.1975163Z fatal: unable to access 'https://github.com/snapcore/go-gettext/': transfer closed with outstanding read data remaining14:21
mborzeck1is github going down again?14:21
pedronispstolowski: I added a question to #9087, we can chat tomorrow if it needs discussion14:28
mupPR #9087: o/snapstate: check available disk space before downloading a snap on install (4/N) <Disk space awareness> <Needs Samuele review> <Created by stolowski> <https://github.com/snapcore/snapd/pull/9087>14:28
pstolowskipedronis: ok14:28
pstolowskipedronis: hmm i didn't think of multi snap install, i think you're right14:30
pedronispstolowski: well also refreshes, this code is used by refreshes too14:30
pedronisthere's some questions there as well14:31
pedronispstolowski: we we should have a chat14:31
pedronistomorrow or when it makes sense for you14:31
pedronispstolowski: I mean, if you are busy with other things, this can probably wait a bit14:32
mupIssue core20#80 opened: networking does not persist in a reboot loop on arm64 pi4 <Created by anonymouse64> <https://github.com/snapcore/core20/issues/80>14:32
pstolowskipedronis: sure, let's see how it foes with xenial+squashfs problem on preseeding14:33
pedronispstolowski: about seeeding error, one option could also be to look at in Error changes, when we do the in flight check in ensureSeeded15:06
pedronisbut is not optimal15:07
pstolowskipedronis: indeed, that would work. but yes15:08
pedronispstolowski: though maybe it's just enough to go over the changes in the api code15:12
pstolowskipedronis: we exit on task errors when preseeding. snap-preseed could inspect state by itself if exit status != 015:13
pstolowskipedronis: it was commit 24d77f474dc53846a16289d19721292d16832cd815:13
pedronispstolowski: this is not about preseed, it's about finishing the seeding15:13
pstolowskipedronis: ah you're right15:13
pedronisyea, I think the option I prefer is just going over the changes in getSeedingInfo if seeded is false15:15
pedronisit's very self contained and less risky15:16
pstolowskipedronis: yes that's ok15:17
ijohnsonpedronis: given the email from CPC, should we adjust `snap debug seeding` output to be more "yaml", I see for example right now if we can't calculate a time and output "-", that makes it invalid yaml15:27
* cachio lunch15:27
ijohnsonpedronis: because otherwise it's all valid yaml15:28
ijohnsonbut maybe there are other edge cases I don't see that are not valid yaml15:29
mupPR snapd#8998 closed: tests/cmd/snap-bootstrap/initramfs-mounts: add test case for empty recovery_mode <Simple 😃> <UC20> <Created by anonymouse64> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/8998>15:33
pedronisijohnson: sorry, I forgot, we have special support in the unicodeMixin to emit things that are valid yaml for out patterns15:54
ijohnsonmmmm, so the current code is buggy then15:54
pedronisijohnson: look at .dash in cmd_info.go for example15:55
ijohnsonah so if we use "–" instead of "-" then yaml is happy15:55
ijohnsonyeah I see it now15:55
pedroniswell, it's a bit more complicated than that, but yes, there are helpers to pick things15:56
ijohnsonpedronis: ok, given this is it okay if I respond to CPC's email with instructions on how to use snap debug seeding with the caveat that we found a bug just now where it's not always valid yaml ?15:56
pedroniswell, we need to add error too15:57
ijohnsonsure, but that won't change the formatting will it?15:58
ijohnsonI was assuming if seeding error'd then we would just exit with non-zero exit code and add something else to the yaml output15:58
pedronisyes, but I would prefer to send one email with all the bits15:58
pedronisinstead of many15:58
ijohnsonok, that's fine15:58
ijohnsonI can file a PR to fix the unicode yaml issue then15:59
pedronisbasically I we should first get closer to what we want in .415:59
pedronisand then mail them15:59
ijohnsonyes makes sense I will not email them16:00
mupPR snapd#9090 opened: cmd/snap/debug/seeding: use unicode for proper yaml <Preseeding 🍞> <Simple 😃> <⚠ Critical> <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/9090>16:14
ijohnsonpedronis: pstolowski: I opened ^ which fixes the yaml issue for snap debug seeding16:14
pedronisijohnson: thx, pstolowski:  I'm looking into adding seed-error16:15
ijohnsonnice16:15
pstolowskipedronis, ijohnson thanks!16:15
mupPR snapcraft#3238 opened: db: introduce generalized datastore <Created by cjp256> <https://github.com/snapcore/snapcraft/pull/3238>16:44
ijohnsonjdstrand: regarding https://bugs.launchpad.net/snapd/+bug/1889695, do you anticipate you will have a fix ready in the next few days ? we would like to include that in the next point release of snapd 2.45.416:57
mupBug #1889695: [k8s-support] permission denied error when calling readlink on /proc/1/ns/pid <snapd:New> <https://launchpad.net/bugs/1889695>16:57
jdstrandijohnson: I could fix that, but they need the other things I'm doing for microk8s. I won't have that done for 2.45.4 and was planning 2.46. if it goes fast, *maybe*, but I doubt it will go fast17:00
pedronisijohnson: I have code, I will post a PR after dinner17:04
ijohnsonjdstrand mmm I see, so the issue is that I assume a new version of various $CONTAINER_TECHNOLOGIES is what is causing the problems?17:19
ijohnsonjdstrand also I don't know how critical the k8s thing is for field, I would recommend asking Tony about the priority of that17:20
pedronisijohnson: I proposed #909117:28
mupPR #9091: cmd/snap: display the error in snap debug seeding if seeding is in error <Created by pedronis> <https://github.com/snapcore/snapd/pull/9091>17:28
ijohnsonpedronis ack I will take a look17:28
mupPR snapd#9091 opened: cmd/snap: display the error in snap debug seeding if seeding is in error <Created by pedronis> <https://github.com/snapcore/snapd/pull/9091>17:29
cachioijohnson, hey17:59
cachioI see the cgroup test failing in debia18:00
cachiohttps://paste.ubuntu.com/p/9rk24R2265/18:00
cachioI tried and it is easy to reproduce18:00
cachiodo you know something about that? what could be the route cause?18:01
ijohnsonLet me look18:01
ijohnsoncachio: no I don't know what that issue is18:03
cachioit is failing in debian sid18:04
cachionot sure if it is because an update on a dependency18:04
jdstrandijohnson: well there are a number of things. new workloads aren't working right and I need to investigate the best fix for that, then there are various access issues, and then there is the different behavior depending on the kernel version18:08
ijohnsonjdstrand ack makes sense18:10
zygaI've released 2.45.3.1 to openSUSE18:10
* zyga gets out of office18:10
ijohnsoncachio: yeah I kinda suspect an upstream change in Debian here18:10
cachioijohnson, yes, I don't see any change in our side which could be affecting that18:11
* cachio afk19:38

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!