/srv/irclogs.ubuntu.com/2018/03/15/#snappy.txt

mborzeckimorning06:00
mwhudson(answer: snapd in the core snap is newer than snapd in bioinic today)06:44
zyga-ubuntugood morning07:08
zyga-ubuntumwhudson: can you give me the denial please07:09
zyga-ubuntumwhudson: grep for DENIED in dmesg07:09
mborzeckizyga-ubuntu: mornings07:09
mwhudsonzyga-ubuntu: i think it's the more or less known thing about apparmor and overlayfs not being friends07:09
zyga-ubuntumwhudson: ah, so it's still the version witohut overrlay support?07:10
zyga-ubuntumwhudson: can you pastebin /var/lib/snapd/system-key07:10
mwhudsonzyga-ubuntu: i'm going to wait for 2.32 until i get bothersome about it07:10
mwhudsonzyga-ubuntu: don't have a vm up know07:10
zyga-ubuntuthat's ok07:10
zyga-ubuntuI thought that patch was out already07:10
mwhudsonzyga-ubuntu: i think xenial is on 2.23.1 or something07:11
mwhudsonhm that's what xenial-proposed has anyway07:12
mwhudsonso does the stable core snap have snapd from xenial-proposed in it?07:12
mwhudsonthat seems surprising07:12
* zyga-ubuntu doesn't know07:12
zyga-ubuntuI was a little detached yesterday07:12
mupPR snapd#4844 opened: overlord/snapstate: allow core defaults configuration via 'system' key <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/4844>07:30
=== pstolowski|afk is now known as pstolowski
pstolowskimornings07:36
mborzeckipstolowski: hey07:37
mborzeckipstolowski: can you take a look at #4826?07:38
mupPR #4826: wrappers: services which are socket or timer activated should not be started during boot <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/4826>07:38
pstolowskimborzecki: yep07:53
kalikianamoin moin07:59
=== _cpaelzer is now known as cpaelzer
mborzeckipstolowski: thanks for the review08:15
pstolowskinp08:16
mupPR snapd#4826 closed: wrappers: services which are socket or timer activated should not be started during boot <Created by bboozzoo> <Merged by bboozzoo> <https://github.com/snapcore/snapd/pull/4826>08:18
mupPR snapd#4845 opened: snap, store: store version numbers in the commands database <Created by mvo5> <https://github.com/snapcore/snapd/pull/4845>08:37
mvomborzecki: could you please create a 2.32 version of 4826 (if there isn't one already)?08:38
mborzeckimvo: coming up08:39
mvota08:39
mupPR snapd#4846 opened: [2.32] wrappers: services which are socket or timer activated should not be started during boot <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/4846>08:49
mborzeckimvo: ^^08:50
mvomborzecki: ta08:53
Chipaca*yawn*08:53
Chipacajust five more minutes08:53
pedronishello08:58
Chipacapedronis: hi08:59
pedronisChipaca: hi,  I need to update a PR after let me know when you want to chat about puritan08:59
Chipacapedronis: knee-deep in the hash cache mash atm09:00
pedronisChipaca: I saw you discussing that,    did you notice that some of those helpers are used when there's no state09:00
pedronisStateCache need to be optional09:01
Chipacapedronis: yes I did09:01
pedronisI mean snapasserts exist to hold stuff at the intersection of  snap files and assertions (but not needing state)09:01
pedronisor at least not requiring state09:02
* Chipaca nods09:02
pedronisChipaca: are you looking  also into the download case? I though the idea was to fix firstboot first09:04
pedronisstore has its own ways to keep state at distance09:04
Chipacapedronis: firstboot first, but with my eye on download to make the followup easy (or trivial)09:04
pedroniseasier sounds fair, trivial unlikely09:05
Chipacait's all a bit messy though09:05
Chipacapedronis: did you see the thing about the extra extra hashing during download delta?09:05
pedronisyes, I was aware of that09:05
pedroniswe also check the hash of the delta itself09:05
Chipacai guess i'd forgotten :-)09:06
Chipacathat's fine09:06
pedronisseems a bit orthogonal09:06
pedronisexcept that we should have picked a different hash for those09:06
Chipacaanyhoo, that's  what i'm in09:06
pedronisno sense being super expensive09:06
pedronisgiven that we need to recheck the whole thing anyhow09:06
pedronisbut it's as it is09:06
Chipacapedronis: we can fix that though :-)09:07
pedronisyes, it's fixable09:07
Chipacanot today09:07
Chipacaalso, store is a mess, and daemon is a mess09:07
Chipaca¯\_(ツ)_/¯09:07
pedronisstore was worse09:07
Chipacaoh, totally09:07
Chipacababy steps09:07
pedronisit's improving (slowly)09:07
pedronisdaemon, no, I don't think we rearchitected much of it yet09:08
pedronislet me know if I can help, also happy to review09:08
* pedronis back to his high prio stuff09:09
mupPR snapd#4847 opened: osutil: add symlinkat(2) <Created by zyga> <https://github.com/snapcore/snapd/pull/4847>09:09
pedronisgrumble, the PR that had a consistently failing spread test now passed once I added a some debug stanza :/ I'm quite sure there is something fragile after the change but who knows now09:20
Chipacapedronis: i'm feeling rather dumb here, but I can't figure out where the second hashing in firstboot is happening09:23
Chipacapedronis: derive side info does one, but the second one...?09:24
mborzeckiit'd be so nice if i didn't have to fire up a vm with fedora/suse just to check what `rpm -E %configure` expands to09:24
pedronisChipaca: verify-snap09:24
Chipacapedronis: that's not run for firstboot09:24
pedronis?09:24
Chipacapedronis: firstboot does InstallPath09:24
Chipacapedronis: which means the snap is local, so gets no validate-snap task09:24
pedronisreally09:25
pedronisI'm confused09:25
Chipacathat's how i read it, but see: dumb09:25
pedronisI thought we always did that09:25
pedronisif we don't there is nothing to fix09:25
pedronisbut might be problematic for other reasons09:25
* Chipaca takes the rest of the day off09:25
Chipaca:-)09:25
pedronisthat's a recent chnage09:26
Chipacapedronis: 201609:27
pedronisnothing to do afaict09:27
pedronisnow I'll discover it's by me09:28
mupPR snapd#4846 closed: [2.32] wrappers: services which are socket or timer activated should not be started during boot <Created by bboozzoo> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/4846>09:28
Chipacapedronis: you'd only discover that if you went looking09:29
Chipacapedronis: I say don't09:30
pedronisit's by me09:30
pedronisso we never did double hashing09:30
Chipacaso the symlink fix should make all the difference we can make09:30
pedronisI mean at firstboot09:31
* Chipaca too09:31
pedronismmh09:32
pedronisyes, avoiding the copy is as good as it gets09:32
pedronisunless we go back to the cheating script09:33
pedronissame also for core btw09:33
Chipacapedronis: well, core links09:33
Chipacapedronis: the symlink only happens if the link fails09:33
pedronisyea, there's not win to be had on core09:33
Chipacaah. yeah.09:33
Chipacabut09:34
Chipacai do feel that if we had a central place to do hashing this would've not taken so long to figure out09:34
Chipacabut, not work for today09:34
pedronisnot sure how we can achieve that09:35
pedronisunless you mean one codeline, not conceptually09:35
Chipacamagic ヽ(`Д´)⊃━☆゚. * ・ 。゚,09:35
Chipacawishful thinking mostly09:36
pedroniswe would need unify DeriveSideInfo and doValidateSnap, seems worthwhile but not sure how to attack that09:36
pedronisit's probably possible, bit of a code pretzel though09:37
* Chipaca nods09:37
Chipacameanwhile I'll do the cheap thing and skip the extra hash in download after successful applyDelta09:37
Chipacathen that'll stop bugging me09:37
Chipacapedronis: can we talk about puritan in ~2h09:39
pedronisyes09:40
zyga-ubuntumborzecki: can you please look at 4847 again09:46
zyga-ubuntuI added one more syscall09:46
mvomborzecki: go vet is fully happy now again on 1.10, right?09:56
mborzeckimvo: yes, it's passing09:57
mborzeckimvo: cachio's bionic PR failed in InstallDate() unit test, probably outdated mksquashfs with the bug that you fixed09:57
ackksergiusens, mvo I see that https://github.com/snapcore/snapcraft/commit/10509d590658f1c417b91d66a356700483997d75 has landed now, is there any plan to rename base-18 to core18 soon?10:00
mvomborzecki: yeah, the issue here is that squashfs has not transitioned to bionic yet iirc the autopkgtest for lxd failed10:08
mvoackk: yes, we want to rename it soon, right now a snapcraft issue prevents us from building, this will get fixed this week, then we will do the rename (once we can build again)10:08
ackkmvo, ah, cool, thanks10:09
pedronispstolowski: hi, I think I still owe you a bunch of reviews, I will try to have a reviews day tomorrow10:10
pstolowskipedronis: hi! no worries, and thanks in advance! I think you can focus on #4358 for now and ignore the rest10:12
mupPR #4358: interfaces: interface hooks implementation <Created by stolowski> <https://github.com/snapcore/snapd/pull/4358>10:12
pstolowskias they are stacked on top of 435810:12
mupPR snapd#4848 opened: many: cherry-pick relevent `go vet` 1.10 fixes to 2.32 <Created by mvo5> <https://github.com/snapcore/snapd/pull/4848>10:15
Chipacamvo: you'll also want to cherry pick 19a1dc929b89bf8dd5d6ad22bb36942b5a2508c410:18
mupPR snapcraft#1994 closed: docker: add the architecture <bug> <Created by sergiusens> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/1994>10:19
Chipacamvo: for bubonic i mean10:19
Chipacabah, for bubonic to pass10:19
Chipacabionic*10:19
mvoChipaca: thank you10:20
Chipacathere's a go 1.10's behaviour change that breaks our tests (explained in that commit)10:20
mborzeckiChipaca: bubonic ;)10:20
mvoChipaca: its not in master yet, is it?10:21
Chipacamvo: no10:21
mborzeckihope it's not about the plague10:21
mvoChipaca, mborzecki lol10:21
Chipacamvo: it's pushed to #483510:21
mupPR #4835: tests: add bionic system to google backend <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/4835>10:21
Chipacabut that fails to be green because the google archive mirror doesn't have the new bionic squashfstools10:22
mvoChipaca: we need to enable bionic-proposed there10:22
mvoChipaca: but I can cherry-pick into my 2.32 pr10:22
* Chipaca nods10:22
Chipacathis is why i mention it :-)10:22
mvota10:22
mborzeckiChipaca: can you take a look at #4841?10:24
mupPR #4841: snap/pack, cmd/snap: add `snap pack --check-skeleton` <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/4841>10:24
mvohey stgraber ! the autopkgtests for squashfs-tools fail in the lxd testing right now (http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#squashfs-tools), is there a know issue with autopkgtest and lxd? the failures do not look related to the squashfs change10:25
Chipacamborzecki: I can do 4831, and 4861, but not 4841 sorry10:25
* Chipaca lies10:26
mborzeckiat least 4861 gives the nice tatooine-ish 404 :P10:27
mupPR snapcraft#1996 closed: tests: add SNAPCRAFT_KEEP_DATA to debug <Created by elopio> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/1996>10:28
cachiomvo, the problem of enabling bionic-proposed is that I need to doit suring the prepare, is it ok?10:28
pedronis#4829 and #4849 also needs reviews10:29
mupPR #4829: store: Sections and WriteCatalogs need to strictly send device auth only if the device has a custom store <Created by pedronis> <https://github.com/snapcore/snapd/pull/4829>10:29
mupPR #4849: many: propagate contexts enough to be able to mark store operations done from the Ensure loop <Created by pedronis> <https://github.com/snapcore/snapd/pull/4849>10:29
mupPR snapd#4849 opened: many: propagate contexts enough to be able to mark store operations done from the Ensure loop <Created by pedronis> <https://github.com/snapcore/snapd/pull/4849>10:29
cachiomvo, it will be temporal until is it enabled by default10:30
mvocachio: yeah, I think thats ok10:32
Chipacamvo: how would you feel about sliding 4834 into .32?10:34
Chipaca#483410:34
mupPR #4834: snap/squashfs: when installing from seed, try symlink before cp <Created by chipaca> <https://github.com/snapcore/snapd/pull/4834>10:34
mupPR snapd#4834 closed: snap/squashfs: when installing from seed, try symlink before cp <Created by chipaca> <Merged by chipaca> <https://github.com/snapcore/snapd/pull/4834>10:35
mvoChipaca: let me look10:36
ondrazyga-ubuntu ping10:36
mvoChipaca: absolutely10:36
Chipacamvo: cd7a41b921446bff4ad02ceacf1811c1a6319cc7 fwiw10:36
mvoChipaca: I cherry-pick10:36
zyga-ubuntuHey ondra10:37
ondrazyga-ubuntu hey, I have asked this before, but when using layouts, what was the process to read original file?10:37
mvoChipaca: ta10:38
zyga-ubuntuondra: you can attempt to use hostfs10:41
ondrazyga-ubuntu any how to do that?10:43
pedronisChipaca: having early lunch, we can chat in ~40 ?10:48
Chipacapedronis: sure10:49
zyga-ubuntuondra: re, sorry, I was afk10:50
zyga-ubuntuondra: so, you can look at the file in /var/lib/snapd/hostfs/$F10:50
zyga-ubuntuondra: but you will need an interface for t hat10:50
mupPR snapd#4850 opened: many: fix shellcheck warnings in bionic <Created by mvo5> <https://github.com/snapcore/snapd/pull/4850>10:50
ondrazyga-ubuntu which interface is that?10:51
zyga-ubuntunone exists now10:51
Chipacamvo: the spellcheck check is also broken in xenial, fwiw, we just don't run it10:51
zyga-ubuntuit would depend on $F for sure10:51
ondrazyga-ubuntu :)10:51
zyga-ubuntuas otherwise it would let  you read any file10:51
ondrazyga-ubuntu right10:51
mvoChipaca: spellcheck or shellcheck? I don't mind so much about the spellcheck, we might as well disable it and only run it via a nightly job10:52
Chipacashellcheck10:52
Chipacaah10:52
Chipacasorry10:52
Chipaca:-)10:52
mvooh, ok10:52
zyga-ubuntusheepcheck10:52
* Chipaca shellchecks his spellchecker10:52
mvoshellshock10:52
ondrazyga-ubuntu wouldn't be easier to allow hook to run before bind mount, and then we can rely on existing permissions?10:52
Chipacaah wait, yes, shellcheck, we're talking of the same thing10:52
zyga-ubuntuondra: no, it's not easy in any way10:52
ondrazyga-ubuntu right10:53
zyga-ubuntuondra: and it would still need an interface10:53
Chipacamvo: shellcheck does not run as part of tests; it's not installed on the images10:53
zyga-ubuntuondra: as this way you could read abritrary files10:53
zyga-ubuntuondra: our current design assumes that applications cannot observe pre-layout filesystem at any stage10:53
zyga-ubuntuso no partial state is expsed10:53
ondrazyga-ubuntu ok, so hostfs it is then10:53
zyga-ubuntuas our apparmor profile assumes the layout is in place10:53
zyga-ubuntuand grants permissions to the places affected by the layout10:53
ondrazyga-ubuntu ah, OK that makes sense10:53
mborzeckizyga-ubuntu: regarding #4571 we could move configure.ac/autogen.sh to the top of snapd tree10:54
mupPR #4571: data, cmd, packaging: use autotools to generate artifacts under data <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/4571>10:54
zyga-ubuntuondra: my advice is to open a thread to request an interface for reading hostfs file (specific file) so that we can grant this10:54
zyga-ubuntumvo: what do you think about mborzecki's proposal?10:54
zyga-ubuntuI'm okay but we had a discussion with that and this is how we ended up with "autotools is hidden in cmd/"10:54
ondrazyga-ubuntu OK will do10:55
cachiozyga-ubuntu, that should be fixed? https://travis-ci.org/snapcore/snapd/builds/353519499#L524711:00
cachiozyga-ubuntu, or it is still in progress11:00
zyga-ubuntucachio: no, not yet. I'm working on that now11:00
cachiozyga-ubuntu, ah, ok, thanks11:01
mvozyga-ubuntu: I think to think but to me autotools is just something I dislike whereever it lifes11:04
mvozyga-ubuntu: I mean "I need to think"11:04
zyga-ubuntumvo: any ideas as to what to do then?11:04
zyga-ubuntushould we move away from autotools11:04
zyga-ubuntuor just use it consistently11:04
mvozyga-ubuntu: sorry, I know my comment was not helpful. but yeah, either consistently or switch but switching must be worth it, mesons seems to be popular but I'm not sure its sufficiently better11:06
mvo(to justify the cost)11:07
mborzeckimvo: xenial version of meson is outdated, and afaik it's not available in trusty at all11:08
ondrazyga-ubuntu mvo any idea what could be causing "run hook "post-refresh": execv failed: No such file or directory"11:11
zyga-ubuntuhmmm,11:11
zyga-ubuntuondra: what does the hook look like?11:12
ondrazyga-ubuntu https://pastebin.ubuntu.com/p/w22S3q9Y2D/11:12
ondrazyga-ubuntu :)11:12
ondrazyga-ubuntu I trimmed it down, as I can't figure out what is the problem11:13
zyga-ubuntuso you refresh a snap and the hook fails to run?11:13
zyga-ubuntuis it reproducible?11:13
ondrazyga-ubuntu I have install hook which runs just fine I did sym link as I usually do and it failed to run11:14
ondrazyga-ubuntu install works11:14
zyga-ubuntusymlink?11:14
ondrazyga-ubuntu happening all the time11:14
ondrazyga-ubuntu that was before11:14
zyga-ubuntupstolowski: ^ wanna look?11:14
ondrazyga-ubuntu so I replaced sym link with file, and still same11:14
pstolowskiondra: can you share that snap?11:16
ondrapstolowski yeah preparing to share it11:16
ondrapstolowski zyga-ubuntu damn, I did clean build and now it works, and I did same before11:22
zyga-ubuntudo you have the old snap?11:22
ondraso can't reproduce it now11:22
zyga-ubuntumaybe look inside11:22
ondrazyga-ubuntu so I was using snap try11:23
ondrazyga-ubuntu and without rebuild I was modifying prime/meta/hook11:23
mupPR snapd#4848 closed: many: cherry-pick relevent `go vet` 1.10 fixes to 2.32 <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/4848>11:25
=== bashfulrobot_ is now known as bashfulrobot
=== Kamilion|ZNC is now known as Kamilion
=== diddledan_ is now known as diddledan
=== mborzeck1 is now known as mborzecki
=== wiking_ is now known as wiking
pedronisChipaca: I'm back11:30
Chipacapedronis: wb :)11:31
Chipacapedronis: so, if I understand your point of view, using puritan for everything stringish isn't a sustainable practice11:31
ondrazyga-ubuntu pstolowski http://people.canonical.com/~okubik/git_2.7.4_amd64.snap11:31
ondrazyga-ubuntu so I'm using snap try, so unsquash it first11:32
pedronisChipaca: indeed11:32
pstolowskiondra: could this be a missing -x on the hook script?11:32
ondrazyga-ubuntu pstolowski so now I have different problem, it will install, but if I try to run I get execv failed: No such file or directory11:32
Chipacapedronis: OTOH my point of view is that unless we do something for every stringish thinig, we're going to eventually miss one we shouldn't11:32
ondrazyga-ubuntu pstolowski do $ snap try <>; it will run, call $ snap try <> on same directory and it will break11:33
Chipacapedronis: would you be happier with using a lot more types, for example?11:33
pedronisChipaca: no in general11:33
pedronisChipaca: we need  tooling and a way to mark things11:34
pedronisChipaca: I find needing a special type for snap-id very suspect11:34
pedronisit feels very cargo cultish11:34
Chipacapedronis: when you say tooling, do you mean a static checker, or do you mean a json decoder replacement?11:34
pedroniswhatever works11:34
pstolowskiondra: what core are you running with?11:34
pedronisChipaca: atm we are just making a bit of code uglier without clear path forward11:35
ondrapstolowski 16-2.31.2+git610.7a79b84 (4243)11:35
Chipacapedronis: what would you do?11:36
pedronisChipaca: also whatevedr is problematic with the store is likely problematic with snap.yaml11:36
pedronisas well11:36
pedronisChipaca: I don't know, I'm not even sure I agree with your premise11:36
pedronisthat we really need to worry about everything11:36
pedronisbut if we do need to worry about everything the current approach alone doesn't cut it11:37
Chipacapedronis: because of the lack of a static checker?11:38
pstolowskiondra: ok, same core here. I un-suqashed it, did snap try twice, it worked. can you do 'snap changes' to find changes correspondin to your snap-try commands, and then 'snap change <ID of the change>' for both to see more info about the failure?11:38
pedronisChipaca: it seems we need to mark all structs with json or yaml tags as either risky or not and then decide what to do with each11:38
mborzeckizyga-ubuntu: mvo: tried having just cmd/configure.ac and doing AC_CONFIG_FILES([../data/Makefile ..]) but that doesn't work, the resulting makefiles do some silly thing and try to cd one level above snapd checkout11:39
pedronisthough sometimes we use map[string]interface{} directly, maybe not on input11:39
pedronisnot sure11:39
zyga-ubuntumborzecki: thank you for confirming that11:40
mborzeckizyga-ubuntu: mvo: just moving configure.ac and autogen.sh to the top level dir (plus adjusting paths) is enough, it will clutter the directory once you autoreconf but at least both cmd and data are built using autohell11:41
zyga-ubuntumborzecki: yeah,11:41
zyga-ubuntuyou have my +1 but convince gustavo as he was opposing it before11:41
Chipacapedronis: that's a mountain of work, but it does seem the logical conclusion11:42
mborzeckizyga-ubuntu: we could easily say with the hack that's right now in the PR :P works too, and does not clutter the directory11:42
pedronisChipaca: well, the non logical solution is say we need to care about everything but then leaving it up to reviewers11:42
mborzeckiChipaca: could we do a silly hack with reflection and field tags perhaps?11:43
ondrapstolowski https://paste.ubuntu.com/p/7J8yPTrmBG/11:44
* cachio afk11:44
mborzeckiChipaca: then have an unmarshaller that wraps json and goes to inspect all the strings to clean them up, unless there's a tag that says to leave the string as it is11:45
mborzeckipedronis: ^^11:45
pedronisthere are probably a few possible approaches11:45
pedronisthere are also concerns about runtime speed11:46
pedronisalso personally don't think we should write a full new json decoder11:46
mborzeckiagreed, i'm not propsing to write a json decoder, just sanitize the structs when they come out of the decoder somehow, in a separate call perhaps11:48
ondrapstolowski here you have whole test https://paste.ubuntu.com/p/2q7PH8cqk4/11:48
ondrapstolowski from snap remove11:48
pedronisChipaca: now we also need to understand what everything means,  I suppose you mean that for example store generated error messages are also a concern?11:49
ondrapstolowski exactly same error I was getting before about configure hook11:49
pedronisChipaca: I mean is our attacker a user of the store, or the store?11:49
ondrapstolowski need to run for lunch, but will be available later11:49
pedronis(there are blurry lines there but it still make a difference where to spend our energy)11:50
Chipacapedronis: if it's the store itself i think things fall apart11:50
Chipacapedronis: but, the problem is bugs11:51
pedronisI understand11:51
pedronisbut there are all sorts of bugs11:51
Chipacapedronis: I mean, #1750527 is the bug11:51
mupBug #1750527: dashboard does not validate text fields <review-tools:Triaged by jdstrand> <Snapcraft:New> <snapd:In Progress by chipaca> <Snap Store:Fix Released by matiasb> <https://launchpad.net/bugs/1750527>11:51
Chipacapedronis: even with that change, it's not clear to me everything textish from the store is validated11:52
pedronisChipaca: I'm not arguing for doing nothing, but I'm also not happy to do something cargo cultish and unbounded11:52
Chipacapedronis: I understand, but if the alternative to cargo culting something is having to make a decision about every single field, cargo culting starts to look good11:53
pedronisChipaca: you are saying we should use the store data without knowing what it is / what it is about11:53
Chipacapedronis: "is this something that can be edited by third parties, and is it going to be shown to the user" seemed to be the question11:54
Chipacathe first half we can probably answer easily11:54
pedronisChipaca: and snap-id is dubious?11:55
pedronisanyway  at this point as I said even if we continue to use string for some things11:55
pedronisas I said we need to worry about all the json and all the yaml11:55
ChipacaI don't think snap-id is dubious, no11:55
pedronisbut you made a puritan.SimpleString11:55
Chipacabut if you make everything not be a string, you can write a really silly static checker11:56
Chipacathe alternative is tagging, which isn't hard (but I hadn't thought of it in this context)11:56
pedronisI'm skeptical of that11:56
pedronis(the silly part)11:57
Chipacapedronis: it'd be only a little more work than the check in daemon for commands11:58
pedronis?11:58
pedroniswe define local types sometimes to parse json11:58
Chipacaok11:59
Chipacapedronis: so what do we do11:59
pedronisit seems like we need to introduce safejson and safeyaml,   and not use json and yaml, as thin wrappers and go from there12:00
pedroniswith a silly check that we don't use the other diretly in non-tests12:01
Chipacapedronis: what are safejson and safeyaml?12:01
pedronisChipaca: packages with a subset of what is offered by json and yaml12:01
pedroniswe can probably then make them have different behavior at test time vs runtime12:02
pedronisand at test time they could check the rules that we make for target types12:02
=== tyhicks` is now known as tyhicks
=== tyhicks is now known as Guest65850
pedronisChipaca: it seems the only approach to make sure we cover all the ground  (I'm a bit worried about the messiness of dealing with our various uses of json statically)12:05
pedronisthough yaml is probably worse, all of it comes from the user12:05
pedronisby definition12:05
pedronisif we don't trust snapcraft12:06
pedronisotoh we have validation there12:06
pedronisChipaca: are you saying that we should do validation for snap.yaml but not trust any string from the store?12:06
pedronisit seems asymmetric, but maybe there's a good reason12:07
Chipacapedronis: aborting a 'snap find' because one of the results had a bogus entry seemed a poor choice12:07
Chipacapedronis: aborting a 'snap install' because of the same seems fine12:07
pedronisyea, but validation doesn't check all the fields at the moment12:08
pedronisdoes it?12:08
Chipacait does not12:08
pedroniswe might print a non-validated field12:08
pedronis(for reasons)12:08
Chipacayes12:08
Chipacabut it'd be fairly straightforward to fix that12:08
pedronisChipaca: I fear you opened a can of worms12:08
Chipacapedronis: it was already open :-) i might've kicked it a little12:09
pedronisChipaca: anyway  you mighe decide to go validation only for snap.yaml (but we have also other yaml files, like gadget yaml)12:10
pedronisbut we still need a scalable solution for all the json from the store12:10
=== alan_g_ is now known as alan_g
Chipacapedronis: (just to keep things interesting, what should it do if the snap yaml ini the json fromo the store is invalid? :) )12:11
pedronisare we not validating it?12:12
Chipacapedronis: the one in details? probably not12:12
pedronisanyway it's a corner case that shows cargo culting with naive types is not great12:12
pedronisfalse security effect12:12
pedronisanyway I think we validate it12:13
pedronisand if it's invalid we ignore it12:13
pedronisor maybe not12:13
pedronislet me check12:13
pstolowskiondra, ah wait, the execv error comes from running the app, it's not hooks12:14
pedronisChipaca: no, it's not validated atm12:15
pedronisjust parsed12:15
pedroniswe ignore it on "parse" errors but not validation (that we don't do)12:15
pstolowskiondra: but ok, i can reproduce what you pasted, investigating12:16
pedronisChipaca: so what I would do is have a way to enforce needing to tag all json fields as either  "user" or something else, all user fields need one of the special dedicated types12:18
pedronis(for values of all)12:19
pedronisChipaca: still would need  a plan about how to make sure we validate all snap.yaml fields12:21
Chipacapedronis: would something like puritan still be useful in this context?12:22
pedronisChipaca: yes,   as I said we would String and Paragrah12:22
pedronisfor some of the user fields12:22
Chipacapedronis: and in particular, if I just used puritan for the known-problematic fields today would that be a reasonable zeroth step12:22
pedronisChipaca: yes,  starting with just a few fields  would an accetable first step12:23
pedroniswe probably don't need or shouldn't need SimpleString though12:23
pedronisfor that step12:23
pedronisunless I'm confused12:23
Chipacaok, I'll prune puritan back to just those, and nuke everthing but paragraph and string12:23
Chipaca(they can easily be brought back -- i'll leave the flags in the underlying code)12:23
pedronisChipaca: I'm also not sure puritan will not offende somebody as a name12:24
* Chipaca grins12:24
Chipacait's a silly name, but I don't think there are puritans left12:24
Chipacai might be wrong though12:24
Chipacapedronis: i could call it 'safejson', and then also use it to house the tag checker12:28
pedronisseems reasonable (to me)12:28
Chipacaalthough this is a particular brand of safe (but then, safe always is)12:28
Chipacasafe-against-global-thermonuclear-war12:29
Chipacatermite-safe vs thermite-safe, etc12:29
Chipaca(also, does termite-safe mean termites can eat it, or won't eat it?)12:29
* Chipaca needs lunch12:30
pedronismvo: Chipaca: do we have a fix now with test layout and /etc?  do I just need ot merge master12:30
Chipacapedronis: AFAIK the layout test is still a flake12:30
pedronisfun not :/12:30
pstolowskiondra: I installed your snap normally, then uninstalled, then snap try works. something is fishy here...12:31
Chipacapstolowski: what's going on?12:31
pedronisChipaca: contact(_url) is intersteting btw, it seems we need a type that validates urls or blanks them12:32
Chipacaungh12:32
Chipacapedronis: have you seen the data in contact12:33
pedronisit's random?12:33
pedronisI thought it was supposed to be a http: or mailto: url12:33
mborzeckihm there's a govalidator package that can do some of this magic12:33
mborzeckiyou basically set validate tags in struct fields and then call ValidateStruct()12:34
mborzeckiChipaca: pedronis: https://godoc.org/github.com/asaskevich/govalidator12:34
pedronisinteresting but seems not what we want (speedwise)12:34
mborzeckiwe've used it in mender for some of the APIs12:34
pedronisif I understood Chipaca's worries12:35
pedroniswe need more of a metavalidator than a validator12:35
mborzeckispeedwise is subjective, my guess would be the i/o part of working with store will be longer than the validation :)12:35
pedronisthat's not what I gathered from John at the sprint12:36
pedronishe was worried about double decoding utf8 basically12:36
mborzeckithe github page has some nice examples https://github.com/asaskevich/govalidator12:36
pedronisanyway our current problem is not so much validation (we have the code), is make sure all the fields12:36
pedronisare setup properly for it12:36
mborzeckipedronis: yes, that's what i recall to, but looks like we're moving towards verifying the contents/structure of respective fields12:37
Chipacapedronis: mborzecki: well... i wasn't worried about the double utf8 decode, per se12:37
Chipacapedronis: mborzecki: but i needed to do most of the work anyway12:37
pedronisit might be underasting for snap.yaml12:37
Chipacathat's why it ended up doing it directly12:38
pedronisheh12:38
pedronisI meant "interesting"12:38
pedronisotoh unless is perfect not sure we want one more dep12:38
pedronismborzecki: for  store json we have more of cleaning up problem, than a validation one12:39
pedronisif I understand12:39
zyga-ubuntumvo: I have the first and harder half of the layouts fix12:39
zyga-ubuntushall I push it to 4847 so that it can be squashed12:39
zyga-ubuntuor would you like to see separate commits12:39
Chipacapedronis: mborzecki: we can also decide to drop invalid json on the floor12:39
zyga-ubuntuI haven't pushed the fix there yet, just the prerequisite helpers12:39
Chipacapedronis: mborzecki i'd be fine with taht if we can do it at the snap level12:39
Chipacathat is, in a search result, drop individual results12:40
Chipacabut then... a typo in a description would stop a snap refresh12:40
Chipacanot sure we want that12:40
Chipaca(granted you'd really need to work hard to get a typo now the store is fixed)12:40
pedronisChipaca: doesn't that apply to snap.yaml too though?12:41
pedronisif the description  comes from the snap.yaml then we clean from the store, but fail when we install anyway?12:41
Chipacapedronis: indeed. and even more vocally.12:41
* Chipaca turns up the 'everything is terrible' dial another notch, and goes to get some tea12:42
zyga-ubuntuChipaca: hey, sorry for being late with that patch; could you look at 4847, this adds the symlinkat and realinkat functions12:42
zyga-ubuntuand some testing helpers12:42
zyga-ubuntuit's used in upcoming fix12:42
Chipacazyga-ubuntu: realinkat?12:43
pedroniszyga-ubuntu: it's "cannot update snap namespace: cannot create writable mimic over "/etc": no such file or directory" fixed or are you working on that still?12:43
Chipacabut yes, after tea is brewed12:43
* pedronis has lost track12:43
zyga-ubuntuI meant to say readlinkat12:43
zyga-ubuntuThank you!12:43
Chipacapedronis: that's the fix he's talking about12:44
Chipacaright now :-)12:44
pstolowskiondra: ah, ignore my earlier comment, second snap try breaks it12:46
zyga-ubuntupedronis: that's what I fixed just now, it will be a PR in a moment12:47
zyga-ubuntupedronis: just trying to coordinate that with mvo for release (one PR, many PRs, squash or not, etc)12:47
mupPR snapd#4836 closed: tests: force profile re-generation via system-key <Created by mvo5> <Merged by niemeyer> <https://github.com/snapcore/snapd/pull/4836>12:48
pedroniszyga-ubuntu: that's fine, just trying to understand whether I needed to re-run the tests or merge master first12:48
zyga-ubunture run now12:49
mupPR snapd#4838 closed: snapstate: put layout feature behind feature flag <Created by mvo5> <Merged by niemeyer> <https://github.com/snapcore/snapd/pull/4838>12:51
mupPR snapd#4851 opened: cmd/snap-update-ns: fix creation of layout symlinks <Created by zyga> <https://github.com/snapcore/snapd/pull/4851>12:51
zyga-ubuntumvo: I've opened https://github.com/snapcore/snapd/pull/4851 to get a feel of the fix in the wild12:51
mupPR #4851: cmd/snap-update-ns: fix creation of layout symlinks <Created by zyga> <https://github.com/snapcore/snapd/pull/4851>12:51
zyga-ubuntuafter standup I need to go to the doctor again but the 2nd fix for layouts is easier so I will push the PR after returning12:52
pstolowskizyga-ubuntu: can you remind me/brief me on how do I inspect namespaces of a snap?12:56
mupPR snapd#4809 closed: cmd/snap: tweak and polish help strings <Created by chipaca> <Merged by chipaca> <https://github.com/snapcore/snapd/pull/4809>12:56
zyga-ubuntupstolowski: use nsenter12:56
zyga-ubuntunsenter -m/run/snapd/ns/foo.mnt12:56
mupPR snapd#4852 opened: snapstate: put layout feature behind feature flag <Created by mvo5> <https://github.com/snapcore/snapd/pull/4852>13:01
pstolowskiniemeyer: having network issues, will join in a few moments13:02
soee_hey are there any plans to fix the ugly looking snap apps their icons in launchers etc?13:27
zyga-ubuntupstolowski: can you please pastebin the meta/snap.yaml13:28
zyga-ubuntupstolowski: I have a suspicion I know what's going on13:28
pstolowskizyga-ubuntu: https://pastebin.ubuntu.com/p/8tCdGtRTcp/13:28
zyga-ubuntupstolowski: aha, that's curious13:29
zyga-ubuntuthat's not what I assumed13:29
zyga-ubuntucan you paste the URL of the snap pelase13:29
zyga-ubuntu*please13:29
zyga-ubuntuI'll pull and explore13:29
pstolowskizyga-ubuntu: http://people.canonical.com/~okubik/git_2.7.4_amd64.snap13:30
pstolowskizyga-ubuntu: unsquash and snap try twice13:30
zyga-ubuntuthanks13:31
pstolowskizyga-ubuntu: ty! let me know what's the outcome13:41
zyga-ubuntuI will only check after my doctor appointment though13:42
pstolowskisure13:45
=== Guest65850 is now known as tyhicks
=== tyhicks is now known as Guest1006
mborzeckiChipaca: are you fixing snap info output?13:56
Chipacamborzecki: yes13:56
mborzeckiChipaca: idk why, but even `fmt.Fprint(w, formatDescr(both.Description, termWidth))` tries to expand %13:57
Chipacamborzecki: it's not formatDescr13:57
Chipacamborzecki: it's strutil.WordWrap13:57
Chipacamborzecki: which is the same one munging the indents13:57
Chipacamborzecki: so guess who's throwing it away13:57
Chipaca<- this guy13:58
Chipaca:-)13:58
mborzeckiChipaca:13:59
ondrapstolowski hey14:00
mborzeckiChipaca: https://paste.ubuntu.com/p/qXH3Bk4Zkt/ pff poor man's fix, but if it's WordWrap breaking it then strutil is probably better place to fix it14:00
ondrapstolowski back now, I saw you can reproduce it now14:00
ondrapstolowski anything else I can assist with?14:00
pstolowskiondra: yeah, I got to the point where I can point my finger at what breaks and handed it over to zyga as it's his domain, he will look at it14:02
zyga-ubuntuI'm going to see a doc now, I'll check it out after that ondra14:02
zyga-ubuntudefinitely feels like my type of problem14:02
ondrazyga-ubuntu yeah no time pressure from me, it's not blocking me personally, just found it as very interesting problem, so happy to help if there need14:04
zyga-ubuntuI know what to look at, I'll let you know when I understand the problem14:04
Chipacamborzecki: yeah, by the time formatDescr gets it it's already happened14:06
mborzeckiChipaca: http://paste.ubuntu.com/p/F3y8NcpYQZ/14:07
ondrazyga-ubuntu thanks bunch :)14:07
Chipacamborzecki: pretty much yes, but as I said on the list, the indent munging needs to die14:07
mborzeckiChipaca: death by 1000 tabs14:08
Chipaca:-)14:08
pedronisniemeyer: #4825 is the PR that needs a 2nd look14:09
mupPR #4825: overlord/snapstate:  implement policy of holding refreshes for 2h since seeding on classic <Critical> <Created by pedronis> <https://github.com/snapcore/snapd/pull/4825>14:09
zyga-ubuntuondra: I know what the problem is, something for me to fix in do-undo logic for mounts14:10
zyga-ubuntuthanks for bringing this to my attention, I will focus on it ASAP14:10
ondrazyga-ubuntu happy to help :)14:11
mborzeckioff to pick up the kids14:20
mupPR snapd#4825 closed: overlord/snapstate:  hold refreshes for 2h after seeding on classic <Critical> <Created by pedronis> <Merged by niemeyer> <https://github.com/snapcore/snapd/pull/4825>14:28
MincePiesQuestion: After installing spotify snap in Elementary OS - How Do I Start It ?14:47
kyrofaMincePies, if they don't pick up the desktop file, check in /snap/bin14:53
kyrofaThere should be an executable in there you can run14:53
ChipacaMincePies: if you just installed snapd, you might need to log out before it has the paths set up right, but you should be able to do 'snap run spotify' (or /snap/bin/spotify if elementary ships it as /snap)14:54
Chipacabrb, rebooting14:54
mupPR snapd#4853 opened: overlord/snapstate: hold refreshes for 2h after seeding on classic <Critical> <Created by pedronis> <https://github.com/snapcore/snapd/pull/4853>15:41
pedronismvo: ^  I made the backport for that bit15:41
jjohansenzyga-ubuntu: I'm building test kernels, is there one you would like in particular15:41
cachioniemeyer, hey15:51
cachioremember the spread issue that I told you during the standup?15:52
niemeyercachio: Hey, sure15:52
cachioniemeyer, well, the real problem was different15:52
niemeyercachio: Not surprised ;)15:52
cachiodebian is killing the networking before the ssh sessions15:53
cachioit is a known issue15:53
niemeyercachio: What does that mean in more detail?15:53
cachiowhen we reboot15:55
cachiosystemd is stopping the network services15:56
cachioin this debian15:56
cachioit is stopping first the network connection and then the ssh sessions15:56
niemeyerHow's that an issue?15:57
cachioin that case spread is not getting that the session is closed15:58
cachioso then when it tries to connect to detect the machine is rebooted15:58
cachioit is to late15:58
cachiothe machine is up again15:58
cachiobebian is taking between 7 and 8 seconds to start15:59
cachioubuntu is taking + than 1215:59
niemeyerAh, I see.. the connection is silently dropped15:59
cachioyes15:59
niemeyerOkay, that makes more sense16:00
cachioI created a service to force to stop the ssh sessions before the network16:00
cachiowhen we reboot16:00
cachioand the problem is gone16:00
niemeyerI'd prefer to workaround it in a way that makes spread more resilient16:00
niemeyerHmm16:00
cachiootherwise I could add a keepalive in spread when we reboot16:01
cachioto detect if the ssh session is gone16:01
=== mborzeck1 is now known as mborzecki
niemeyercachio: Won't work.. too short a time16:01
niemeyercachio: I suggest the following: let's drop all the waits, and make spread look at the actual uptime16:02
cachioniemeyer, ok16:02
niemeyercachio: Instead of waiting for the disconnection, it disconnects by itself automatically when asking for the reboot16:02
niemeyercachio: And then immediately tries to reconnect and check the uptime16:02
niemeyercachio: Repeat until timeout16:03
cachioniemeyer, ok, makes sense16:03
cachioI'll try that16:03
niemeyercachio: WE need to make this logic resilient as we'll often see errors mid-routine16:03
cachiowhich errors?16:04
cachioyou mean the failed attempts?16:04
cachioniemeyer,16:05
cachioI'll try that and push it16:05
cachioafter lunch :)16:05
cachioniemeyer, thanks16:06
niemeyercachio: np, thanks for figuring it out16:07
niemeyercachio: I suggest using this to figure the latest boot time:16:12
niemeyerdate -u --iso-8601=seconds -d "`cut -f1 -d. /proc/uptime` seconds ago"16:12
niemeyercachio: There are backticks in that message, which hopefully your IRC client did not interpret16:12
niemeyercachio: Ah, even better:16:13
niemeyer date -u --iso-8601=seconds -d "$(cut -f1 -d' ' /proc/uptime) seconds ago"16:13
niemeyercachio: Then, we need to tolerate a delta of up to, say, 3 seconds, since there will be a difference between the time we read the uptime from the time date makes the syscall to pick up the time16:15
Chipacaniemeyer: cachio: or, you know, 'uptime -s'16:15
Chipaca:)16:15
Chipacai'm going to go offline for a while, will bbl16:17
niemeyerChipaca: Does it use utmp or proc?16:17
* niemeyer checks16:17
niemeyer(we want proc)16:17
Chipacashould still be able to push the fix for snap info tonight16:17
niemeyerApparently proc, so that's nicer indeed, thanks!16:19
Chipacaniemeyer: proc; utmp for who's logged in16:19
* Chipaca vanishes in a cloud of []rune16:19
niemeyerExcept cut and date come from coreutils, and uptime comes from procps16:20
niemeyerProbably good enough16:20
MincePieswell that worked - only just! https://paste.ubuntu.com/p/Dj5nxS7t8g/16:25
MincePiesWhere can I find a list of snaps to test ?16:26
cachioniemeyer, ok, so I'll use 'uptime -s'16:37
niemeyercachio: Sounds good, thanks16:37
MincePiesWhere can I find a list of snaps to test ?16:40
MincePiesI have a 1 teraByte SSD16:40
pedronisI'm getting again  Job for snapd.service canceled.  on 14.0416:44
pedronisdid we find what was it about?16:45
cachiopedronis, do you have a log?16:45
cachioto see where is it failing16:45
pedroniscachio:  https://travis-ci.org/snapcore/snapd/builds/353848109?utm_source=github_status&utm_medium=notification  3 prepares on 14.04 are failing with that16:46
cachiopedronis, it was giving that error when we tried to stop it and it was not in running state16:46
cachiopedronis, it is failig in another place now16:48
cachiopedronis, a solution is to encapsulate the stop into a function and there check before the status and then stop the service16:49
pedronisit's failing like this on a couple of my branches16:50
pedronisthat have very different changes16:50
cachiopedronis, so, perhaps it is something new16:52
pedronismaster is also red16:52
pedronistrying to see which way16:52
cachiosame error on master16:53
cachiosomething changed16:53
pedronisyes16:53
cachiopedronis, I'll take a look16:53
cachioright now16:53
cachiothanks for the headsup16:54
=== pstolowski is now known as pstolowski|afk
mupPR snapd#4854 opened: devicestate: introduce DeviceManager.Registered returning a channel closed when the device is known to be registered <Created by pedronis> <https://github.com/snapcore/snapd/pull/4854>17:01
zyga-ubunture17:01
* zyga-ubuntu needs more examinations 17:01
zyga-ubuntuaww, pushed go fmt fixes17:08
MincePiesquestion, Where can I find a list of snaps for testing, please ?17:16
mcphailhttps://snapcraft.io/store ?17:26
mcphailhttps://uappexplorer.com/snaps17:27
MincePiesmcphail: how do I get this to go? https://uappexplorer.com/snap/ubuntu/software-boutique17:29
mcphailMincePies: I've never used that snap. I think it is fairly specific for Ubuntu Mate. flexiondotorg may be able to clarify for you17:31
MincePiesWho is he ?17:32
zyga-ubuntuMincePies: he's affiliated with Ubuntu Mate17:32
mcphailHe's the creator of that snap17:32
MincePiesLets see if he shows-up, then (?)17:32
mcphailGenerally, if you have a snap installed, "snap info name_of_snap" will tell you which commands can be run17:33
MincePiesBrilliant & Its my first snap install! https://imgur.com/CHByC6U17:36
ogra_ oh zyga-ubuntu ....17:39
ogra_zyga-ubuntu, will you take pictures of the crowd with pitchforks in fromt of your house ?17:39
ogra_"Because flatpak is not the future ..."17:39
zyga-ubuntuogra_: in poland? they will be lost at the train station17:40
ogra_lol17:40
zyga-ubuntu"track 6 at platform 4 in sector 8"17:40
zyga-ubuntuall said in gibberish polish with poor speakers17:40
zyga-ubuntuand once they come here they will become infected17:40
zyga-ubuntuand then half of them will oppose the other half17:41
zyga-ubuntuand they will discuss a substitute topic instead17:41
zyga-ubuntuwanna do a code review?17:41
MincePieszyga-ubuntu: > wanna do a code review? Answer: Yeah.18:09
zyga-ubuntuMincePies: hey18:09
zyga-ubuntuI have two related PRs18:10
zyga-ubuntuhttps://github.com/snapcore/snapd/pull/484718:10
mupPR #4847: osutil,testutil: add symlinkat(2) and readlinkat(2) <Created by zyga> <https://github.com/snapcore/snapd/pull/4847>18:10
zyga-ubuntuand https://github.com/snapcore/snapd/pull/485118:10
mupPR #4851: cmd/snap-update-ns: fix creation of layout symlinks <Created by zyga> <https://github.com/snapcore/snapd/pull/4851>18:10
zyga-ubuntuI will happily take feedback18:11
MincePieszyga-ubuntu: I don't Like this: https://paste.ubuntu.com/p/H944SV4kc3/18:12
zyga-ubuntucan you be more specific?18:12
MincePiesWill it work on debian ?18:13
zyga-ubuntuyes, why would you worry about that?18:13
zyga-ubuntuthis is an unit test for a testing helper18:13
zyga-ubuntuit will work on any system18:13
MincePieszyga-ubuntu:  > it will work on any system | That's abit 'headed' there.18:14
zyga-ubuntu?18:14
MincePiesHave you tried Rosa ?18:14
zyga-ubuntuit will work on windows and macos and plan918:14
zyga-ubuntubecause it's totally unrelated to the system18:15
zyga-ubuntubecause it's a mocking helper for testing other parts of the code18:15
MincePiesWhat is a mocking helper, then, when its at home?18:15
zyga-ubuntusorry, I'm looking for people who can review my code18:15
MincePieshe doesn't know.18:16
zyga-ubuntuinternet is a funny place18:16
zyga-ubuntujjohansen: hey, do you have a patch I could pull and try out?18:25
mupPR snapd#4839 closed: errtracker: respect the /etc/whoopsie configuration <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/4839>18:37
mupPR snapd#4853 closed: overlord/snapstate: hold refreshes for 2h after seeding on classic (2.32) <Critical> <Created by pedronis> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/4853>18:37
mupPR snapd#4285 closed: tests, spread: add Arch Linux to CI systems <Created by bboozzoo> <Closed by niemeyer> <https://github.com/snapcore/snapd/pull/4285>18:39
mupPR snapd#4855 opened: Translate polkit strings <Created by gunnarhj> <https://github.com/snapcore/snapd/pull/4855>19:17
mupPR snapd#4852 closed: snapstate: put layout feature behind feature flag (2.32) <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/4852>19:49
oSoMoNsergiusens, is https://forum.snapcraft.io/t/custom-environment-variables-for-parts/1639/9 being planned / worked on yet?19:56
oSoMoN(I might be able to take a stab at it if not)19:57
zyga-ubuntuhmmm20:04
zyga-ubuntuI'm getting consistent failures20:04
* zyga-ubuntu wonders what changed20:04
zyga-ubuntu+ systemctl stop snapd.service snapd.socket20:06
zyga-ubuntuJob for snapd.service canceled.20:06
cachiozyga-ubuntu, I have fixed that20:06
zyga-ubuntumvo: if you are around, do you have any idea what may have changed?20:06
zyga-ubuntuoh20:06
zyga-ubuntucachio: shall I pull master?20:06
* zyga-ubuntu hugs cachio :-)20:07
cachiono yet20:07
zyga-ubuntuwhat do I need?20:07
cachioI was testing that20:07
cachioI'll push in 5 minutes20:07
zyga-ubuntuexcellent, thank you20:07
zyga-ubuntuI will send kids to bed in the meantime20:07
sergiusensoSoMoN: no, not on the roadmap; we could plan for it in Berlin.20:08
mvozyga-ubuntu: hey20:09
mvozyga-ubuntu: I am around, what is the question20:09
oSoMoNsergiusens, please do :) I won't be in Berlin but I'll be tracking it20:11
mupPR snapd#4856 opened: release: 2.32~pre2 changelogs <Created by mvo5> <https://github.com/snapcore/snapd/pull/4856>20:13
sergiusensoSoMoN: if you want to implement I would not be against that either ;-)20:17
mwhudsonzyga-ubuntu: morning20:17
mwhudsonzyga-ubuntu: "We can check that we are on an overlayfs, look at the upperdir and check if it is a tmpfs." <- does this mean parsing /proc/mounts or something else?20:18
mwhudsonif so, does snapd already have code for this?20:18
cachiozyga-ubuntu, #485720:19
mupPR #4857: tests: adding checks before stop snapd service to avoid job canceled on ubuntu 14.04 <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/4857>20:19
mupPR snapd#4857 opened: tests: adding checks before stop snapd service to avoid job canceled on ubuntu 14.04 <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/4857>20:19
cachiois not a super elegant solution but should work20:19
cachioWe already used that in the past to fix the same problem in the reset20:20
mwhudsonmmm osutil/mountinfo.go looks like a good start ;)20:20
mupPR snapd#4855 closed: data: translate polkit strings (2.32) <Created by gunnarhj> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/4855>20:20
zyga-ubunture20:24
zyga-ubuntuhey good morning20:24
zyga-ubuntumwhudson: we have code for this already20:24
zyga-ubuntumwhudson: please look at ... (one sec)20:24
zyga-ubuntuhttps://github.com/snapcore/snapd/blob/master/osutil/overlay.go#L4420:25
zyga-ubuntuI believe this can be modified to return both upper and lower dir20:25
zyga-ubuntuand then we can inspect the upper dir path to find the fstype20:25
mwhudsonoh heh that code looks installer relevant20:26
zyga-ubuntuit is referenced from ..20:26
zyga-ubuntuhttps://github.com/snapcore/snapd/blob/master/interfaces/apparmor/backend.go#L114 and https://github.com/snapcore/snapd/blob/master/interfaces/apparmor/backend.go#L44120:27
zyga-ubuntuwhich means it ends up in both snap-confine and per-snap profiles20:27
zyga-ubuntuer20:27
oSoMoNsergiusens, I haven't looked into implementation details yet, but it looks like it shouldn't be too much work20:27
zyga-ubuntuper app snap profiles20:27
mwhudsonyeah that makes sense20:27
zyga-ubuntuwe could use it as a starting point20:27
zyga-ubuntuI think rather than doing elaborate mountinfo analysis just find upperdir and then fstatfs it20:27
mwhudsoni guess we should change code around here: https://github.com/snapcore/snapd/blob/master/overlord/snapstate/autorefresh.go#L13420:28
mwhudson(which seems very fresh, hi pedronis)20:28
zyga-ubuntumwhudson: not sure, ask pedronis via the forum20:36
mwhudsonzyga-ubuntu: ack20:36
mvocachio: we might have a new 2.32~pre for amd64/i386 soon in beta20:49
mvocachio: arm seems to be a bit slow to build though20:49
cachiomvo, perfect20:49
cachiotomorrow afternoon I'll be off20:49
mvocachio: no worries20:49
cachiomvo, but I can make the tests run20:49
mvocachio: getting it into beta and bionic is the key here, all else is bonus :)20:49
cachioso should not be a problem20:50
mvocachio: thank you! that is great20:50
cachionp20:52
zyga-ubuntucachio: so, what can I do to unblock PRs?20:53
cachiozyga-ubuntu, we need to merge #4857  first20:54
mupPR #4857: tests: adding checks before stopping snapd service to avoid job canceled on ubuntu 14.04 <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/4857>20:54
cachioit is the first part of the solution20:54
zyga-ubuntuok, reading20:54
zyga-ubuntuwhat's next?20:54
cachiothen I'll apply that to the other tests and scripts20:55
cachiozyga-ubuntu, I just applied that for those tests that were failing20:55
cachiobasically it fails in tests with script which are stopping snapd in the first line20:55
cachioin the prepare20:56
cachioit happens because in the prepare-each the last line is starting the snapd.service and socket20:56
cachioand for some reason now the start is taking more time than before20:56
zyga-ubuntucachio: can we use systemctl is-active?20:57
cachiowell, the problem is that the status "activating" makes the mess20:57
cachiois-active returns true20:57
cachiobut it is not fully ready20:58
cachioit is just happening in 14.0420:58
cachioperhaps we could try to make a change in systemd to prevent that20:58
cachioand/or see why the systemd service is taking more time to be active (running)20:59
zyga-ubuntuhmm20:59
zyga-ubuntuI mean20:59
zyga-ubuntuit prints "active"20:59
zyga-ubuntuI mainly ask because it looks cleaer than doing status and grepping20:59
zyga-ubuntu*cleaner21:00
cachiozyga-ubuntu, is-active is not enough21:01
cachiozyga-ubuntu, that's the problem21:02
cachiozyga-ubuntu, perhaps I am not getting you well, please add a comment in the PR21:03
zyga-ubuntunah, that's ok21:03
cachiothis solution is temporal21:03
zyga-ubuntuI'm fine with good is better than perfect if it ships21:03
cachioI think we need to figure out why it is happening now, and not before21:03
cachiobut I did that to unblock all the other PRs21:04
cachiozyga-ubuntu, let's see if all the tests pass21:06
cachiozyga-ubuntu, I just tested completion21:06
cachiowith repeat 5021:06
oSoMoNI'm not finding any documentation on build-snaps. how does snapcraft expose the contents of the build-snaps once they are installed?21:07
mvocachio: i386 is in beta now21:09
mvocachio: looks like you need to shepherd amd64/arm* into beta, it takes a long time today :/21:10
mvocachio: or will do the rest in my morning, need to sleep now. cu21:12
oSoMoNsergiusens, ^21:12
cachiozyga-ubuntu, well, no errors for 14.0421:16
cachiostill missing to finish one test21:16
zyga-ubuntuok21:16
cachiozyga-ubuntu, in green21:21
Chipacaniemeyer: ping22:12
niemeyerChipaca: pong but on a call22:12
Chipacaniemeyer: ah, give me a shout when you get off, i'll prepare some examples meanwhile22:13
zyga-ubuntuChipaca: wow, you're working late22:22
zyga-ubuntucnk22:23
zyga-ubuntucachio: is it merged?22:23
Chipacazyga-ubuntu: i don't work tomorrow, and i want to fix this snap info description thing22:23
cachiozyga-ubuntu, let me check22:23
zyga-ubuntuChipaca: I understand the feeling22:24
zyga-ubuntuplus22:24
zyga-ubuntuI had coffee22:24
zyga-ubuntuthat wasn't a smart thing22:24
cachiozyga-ubuntu, no reviews yet22:24
zyga-ubuntubut it was leftover after some cake we made22:24
zyga-ubuntuand now I'm here and looking at a bug22:24
cachioChipaca, zyga-ubuntu #485722:27
mupPR #4857: tests: adding checks before stopping snapd service to avoid job canceled on ubuntu 14.04 <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/4857>22:27
cachioplease take a look before merging it22:27
Chipacazyga-ubuntu: oooh, i have cake too22:36
Chipacabut … it's downstairs22:36
zyga-ubuntuChipaca: let's review 485722:39
zyga-ubuntuit shoud fix master22:39
Chipacai'm looking at it22:39
Chipacaand scritching my head22:39
Chipacais systemd really this broken22:39
zyga-ubuntuwhy22:39
zyga-ubuntuheh22:39
zyga-ubuntuthat's a good question22:40
zyga-ubuntuI'm inclined to slap a TODO on it and merge it because it's green22:40
zyga-ubuntuand red sucks22:40
zyga-ubuntuactually22:40
zyga-ubuntumaybe we are just silly22:40
zyga-ubuntumaybe the "cancelled" error just means22:40
zyga-ubuntuyeah, it's off22:40
Chipacazyga-ubuntu: ?22:40
zyga-ubuntubut returns an error22:40
Chipacaah, no22:41
Chipacazyga-ubuntu: cancelled means 'i couldn't queue that job you asked me to do'22:41
zyga-ubuntuah22:41
zyga-ubuntuhmmm22:41
Chipacawhere 'that job' is stopping the thing22:41
zyga-ubuntudid we report it upstream?22:41
Chipacazyga-ubuntu: AIUI it's fixed in a new enough systemd22:41
zyga-ubuntubut not in 18.0422:42
Chipacaalso if we describe what we're doing to systemd in trusty i suspect pottering will weep22:42
Chipacazyga-ubuntu: isn't this 14.04 fix?22:42
zyga-ubuntubut this was affecting 16.04 and others22:42
zyga-ubuntuhmm22:42
zyga-ubuntuone sec22:42
cachioit is affecting just 14.0422:42
Chipacaif we can catch it on a new enough  one, yes please let's report it22:42
Chipacai thought it was always trusty22:43
zyga-ubuntuah22:43
zyga-ubuntuyes, just 14.0422:43
zyga-ubuntuso...22:43
zyga-ubuntumeh but yes22:43
zyga-ubuntuI wonder why now it became so apparent22:43
zyga-ubuntudid something change22:43
zyga-ubuntuor is it just google cloud being "better"22:43
Chipacaraces are racy22:44
zyga-ubuntuI have a feeling we are "winning" more often now22:44
Chipacaniemeyer: depending on how busy your call is, if you want, take a look at http://people.canonical.com/~john/wrappers.txt22:44
Chipacaniemeyer: bottom line the current formatDescr is very buggy, so  i rewrote it, but before pushing i thought i'd compare it with formatDescr and with go/doc's ToText22:45
Chipacaniemeyer: in my book, i win22:45
Chipacaniemeyer: but i thought i'd check with you22:46
* zyga-ubuntu -> Zzz22:46
niemeyerChipaca: Which one is yours? Top?22:47
Chipacaniemeyer: the one labeled 'wordwrap'22:47
Chipacayes, top22:47
mupPR snapd#4857 closed: tests: adding checks before stopping snapd service to avoid job canceled on ubuntu 14.04 <Created by sergiocazzolato> <Merged by zyga> <https://github.com/snapcore/snapd/pull/4857>22:47
niemeyerChipaca: A bit strange on acestreamplayer22:47
Chipacaniemeyer: that's the 'respecting existing \n' thing22:48
niemeyerChipaca: Even worse on autopilot-qt22:49
niemeyerChipaca: I wonder if we should fold22:49
niemeyerChipaca: and respect empty lines instead22:49
Chipacaniemeyer: knowing when to fold is hard22:49
niemeyerChipaca: Empty lines?22:49
Chipacaniemeyer: look at firefox for an example of folding22:49
zyga-ubuntujust buy 100 nvidia GPUs and have them AI the problem away22:49
Chipacazyga-ubuntu: Zzz22:50
niemeyerChipaca: I see..22:50
Chipacazyga-ubuntu: (in reading this i saw there's a gpu-enabled terminal, and i wondered why a terminal would use the gpu for the terminal and not for ai)22:50
niemeyerChipaca: Empty lines and non letters at start, maybe..22:50
niemeyerChipaca: I think it's going into a good direction.. and the exercise you're doing is great22:50
niemeyerChipaca: Thanks for that!22:51
niemeyerChipaca: Let's see if we can do some conservative folding, starting on the cases we're pretty sure is fine.. that might be better than to figure when *not* to fold22:51
Chipacaniemeyer: if knowing when to fold were easy there wouldn't be a Common Mark :-)22:51
niemeyerAnyway22:52
Chipacabut, sure22:52
niemeyerI need to run22:52
Chipacaniemeyer: aw22:52
Chipacayou're no fun any more :-)22:52
Chipacaniemeyer: I'll push this, as it's an improvement over formatDescr, and we can loop back next week22:52
Chipacai'm not here tomorrow :-)22:52
niemeyerThank you!22:52
niemeyerMe neither22:52
niemeyer:)22:52
niemeyerOr maybe not anyway ;)22:52
zyga-ubuntuhaha22:52
niemeyer... nothing to see here ... o/22:52
zyga-ubuntuso "see you all tomorrow"22:52
zyga-ubuntuthis team is so predictibly terrible at not working22:53
* zyga-ubuntu goes to sleep22:53
Chipacaniemeyer: btw in that .txt the "has \n\n" and "has \r" is to help figure out folding heuristics, if they exist22:57
cachiozyga-ubuntu, good night22:57
Chipacathe "has \t" is because i refuse to care if it looks bad because somebody put tabs in there22:57
mwhudsonhow long should booting ubuntu core on a dragonboard take?23:17
mwhudsoni haven't booted this one in a long time so it's possible the hardware has died23:18
mwhudsonbut it's hanging at "failed to load macaddress file, using random one instead"23:18
mwhudsonor it's possible i hadn't inserted the sd card fully23:20
zyga-ubuntumwhudson: hmm, it should boot pretty quickly23:27
zyga-ubuntumwhudson: I had to reflash my SD card after loooong inactivty, not sure why23:27
zyga-ubuntumaybe that other card just failed23:27
mwhudsonzyga-ubuntu: nah i just hadn't pushed the card i was booting off in fully :)23:27
zyga-ubuntuah :)23:28
* zyga-ubuntu cannot sleep after that coffee23:28
mwhudsonok now time to try to remember how to make an ubuntu core image23:29
zyga-ubuntuctrl-r ubuntu-image ;-)23:29
zyga-ubuntuyou need a model assertion23:29
zyga-ubuntuthe rest is easy-ish23:29
mwhudsonyes exactly :)23:29
mwhudsonuh i also need to download an arm64 core snap23:31
mupPR snapd#4858 opened: strutil, cmd/snap: drop strutil.WordWrap, first pass at replacement <Created by chipaca> <https://github.com/snapcore/snapd/pull/4858>23:32
Chipacazyga-ubuntu: ^ special rune-wrangling pr for curing insomnia23:32
mwhudsonuhh my board rebooted and snapd paniced with "sync: unlock of unlocked mutex"23:33
zyga-ubuntuuh23:33
zyga-ubuntunot fun23:33
zyga-ubuntuwhat did it do before23:33
zyga-ubuntuI recall we had some issues when error cases would panic23:33
zyga-ubuntus/cases/paths/23:33
zyga-ubuntubut not deliberatly, more by accident really23:33
mwhudsonhttps://www.dropbox.com/s/y2svocouxp7o1h2/IMG_20180316_123326990.jpg?dl=023:34
mwhudsonhm not extremely readable23:35
zyga-ubuntuno, not much23:35
zyga-ubuntucan you focus on the screen and send another one23:35
zyga-ubuntuoh23:35
zyga-ubuntuinvalid memory address or nil pointer dereference23:36
zyga-ubuntulooks like pedronis-land23:36
zyga-ubuntuI don't know that code much23:36
zyga-ubuntubut please drop this in the forum23:36
zyga-ubuntulooks like something to fix for the release23:36
mwhudsonhttps://forum.snapcraft.io/t/panic-on-dragonboard/449023:40
zyga-ubuntuChipaca: replied23:41
zyga-ubuntuThank you mwhudson23:41
zyga-ubuntuyou can drop the image into the forum23:41
zyga-ubuntuit is more long-lived than a dropbox URL23:41
zyga-ubuntujust drag the image over to the edit field23:41
zyga-ubuntuand wow23:41
zyga-ubuntuyou have a big office :D23:41
mwhudsonhaha i can't work at home any more23:42
zyga-ubuntuwhy not?23:42
zyga-ubuntuChipaca: https://travis-ci.org/snapcore/snapd/builds/354083470?utm_source=github_status&utm_medium=notification23:42
zyga-ubuntuthis build is done but still "running" on travis23:43
zyga-ubuntuit will fail on timeout any moment now23:43
zyga-ubuntuok23:44
zyga-ubuntuI will now exercise "can I keep my eyes closed" game23:45
Chipacaok, i'm out of here23:49
Chipacasee you all when i see you all23:49

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