/srv/irclogs.ubuntu.com/2018/06/13/#snappy.txt

mwhudsonhi00:14
mwhudsonis anyone around?00:14
mwhudsonseeding the snaps on the latest bionic live-server daily is taking an extraordinary amount of time00:15
mwhudsonlike 4 minutes00:15
mwhudsondoes anyone know anything about this?00:15
niemeyermwhudson: I haven't heard anything about it, and certainly not expected02:32
mwhudsonniemeyer: i forumed https://forum.snapcraft.io/t/extremely-slow-seeding/589102:33
niemeyermwhudson: Thanks!02:34
mupPR snapd#5313 opened: tests: enable fedora 28 again <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/5313>03:01
mborzeckimorning04:58
Lin-Buo-Renhttps://forum.snapcraft.io/t/wildcard-syntax-in-organize-keyword/589504:58
mupPR snapd#5221 closed: snap: parse connect instructions in gadget.yaml <Created by pedronis> <Merged by pedronis> <https://github.com/snapcore/snapd/pull/5221>05:12
zygao/05:15
zygagood morning!05:15
mborzeckizyga: is pstolowski still collecting logs from econnreset?05:30
mborzeckipstolowski: https://paste.ubuntu.com/p/8BgX5gJdXj/05:31
zyganot sure05:32
zygagetsockopt: connection refused05:33
zygaeconreset is driving me crazy05:40
mupPR snapd#5304 closed: overlord/ifacestate:  simplify checkConnectConflicts and also connect signature <Created by pedronis> <Merged by pedronis> <https://github.com/snapcore/snapd/pull/5304>05:41
mupPR snapd#5313 closed: tests: enable fedora 28 again <Created by sergiocazzolato> <Merged by zyga> <https://github.com/snapcore/snapd/pull/5313>05:43
mupPR snapd#5292 closed: interfaces/docker-support: update for docker 18.05 <Created by anonymouse64> <Merged by zyga> <https://github.com/snapcore/snapd/pull/5292>05:49
mupPR snapd#5285 closed: tests/main/{snap-repair,ubuntu-core-services}: add debug information <Blocked> <Created by bboozzoo> <Closed by bboozzoo> <https://github.com/snapcore/snapd/pull/5285>05:53
zygahttps://github.com/snapcore/snapd/pull/5230 needs a 2nd review05:54
mupPR #5230: interfaces/udisks2: also implement implicit classic slot <Created by jdstrand> <https://github.com/snapcore/snapd/pull/5230>05:54
* zyga goes out with the dog05:59
zygare06:44
mvoabeato: hey, nice work on the watchdog PR! how urgent is this for you? is 2.34 (~5 weeks away) ok? or do you need it quicker?06:51
mvo5276 needs a second review06:51
mvoplease :)06:51
mupPR snapd#5301 closed: snapstate,ifacestate: remove core-phase-2 handling <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/5301>06:52
abeatomvo, it is fine to have it for 2.34, thanks for asking (we already have a working workaround and do not need this urgently, it is fine to have it in an update)06:53
mborzeckimvo: 5276 needs deconflicting06:53
mvoabeato: great, thank you06:54
abeatoyw06:55
mvomborzecki: indeed, done06:56
pedronismvo: hi, did you see this:  https://forum.snapcraft.io/t/extremely-slow-seeding/589107:03
mvopedronis: not yet, let me check07:08
mvomwhudson: hey, about your forum post about seeding being slow. is this a regression, i.e. was the previous snapd quicker?07:13
pstolowskimorning07:18
pstolowskimborzecki: thanks for the log, i think i have enough logs now07:20
pstolowskii'll look at econnreset again now07:25
mborzeckimvo: +1 on 5276, also restarted the build as it failed with interfaces-calendar-.. (one that's know to randomly fail)07:28
mvomborzecki: thank you07:28
mvomborzecki: and thank you :)07:28
pstolowskipedronis: hey, is there any benefit of doing task.SetStatus(state.DoneStatus) at the very end of task handler? I remember moving it towards the end in the reviews, but now that i look at it i doubt it serves any purpose07:31
pedronispstolowski: it's mostly for consistency,  are you wondering if you need it, we do need it07:34
pedronispstolowski: the reason we need  is that we want to add th tasks/change to state in the same atomic write to state as we set the task to done, otherwise we risk having it done again (and add the tasks again)07:37
pedronisor fail because to add them forever because self-conflicts of some kind07:37
pstolowskipedronis: ok, i see; there are some comments in a few other places that do that but they don't tell whole story, thanks07:38
pedronispstolowski: it's usually related to having the task change the state in a significant non idempotent way07:39
pedronisat which point we want to mark it done in the same atomic write07:39
mwhudsonmvo: yes it's a regression, haven't tried for a couple of weeks though07:39
pstolowskipedronis: understood, thanks07:41
mvomwhudson: thank you, I tried to reproduce but no luck so far (booted it just two times though). any hints what I could be missing? I used the amd64 image in a standard kvm vm with -m 150007:42
mwhudsonmvo: i'm trying your command line and it's hanging for me07:42
mwhudsonmaybe i should reboot my system07:42
mwhudson(as in, my  laptop)07:42
mvomwhudson: what commandline did you use? I can try that one on my box07:43
mwhudsonmvo: kvm -m 1500 -snapshot ~/isos/bionic-live-server-amd64.iso07:43
zygawhat's the URL to the iso07:43
mwhudsonearlier i was using -m 1024 so i was wondering if it was swapping in the system07:44
zygaI can try here for one more sample07:44
mvomwhudson: heh, that looks eerily similar ;)07:44
zygamy network has higher latency than landlines07:44
mvomwhudson: aha, I can try with smaller ram values07:44
mwhudsonmvo: usually i use -cdrom $ISO -hda target.img07:44
mvomwhudson: I was thinking if .au makes a difference07:44
mwhudsonif it's hitting the network, i have other complaints :)07:44
mwhudsonthe cd is usually plenty fast here07:45
mwhudson*cdn07:45
mvomwhudson: or .nz - yeah, I shouldn't07:45
* mwhudson downloads a snap at 11MB/s07:46
pedronispstolowski: it's usually:    do things that could error,   change the state,  mark it done07:46
pedronispstolowski: if a task is fully idempotent it can rely on taskrunner marking it done07:46
mwhudsonargh this vm booted after 4 mins but i forgot to pass -redir07:46
mwhudsonpedronis, mvo: http://paste.ubuntu.com/p/BQGMG4pZdM/ <- snap tasks 207:48
* mwhudson reboots the host07:48
mborzeckimwhudson: have you tried using virtio for net and drive btw?07:49
zygaDone    2018-06-13T07:42:47Z  2018-06-13T07:44:35Z  Mount snap "core" (4650)07:51
zygathis is certainly unexpected07:51
zygais this an SD card?07:51
zygaunless this includes some waiting on other tasks07:51
pedroniszyga: you need to look at the ready before, not the spawn07:52
pedronisthe spawn is not when they start running07:52
pedronisis when they are created07:52
zygaI see07:52
zygain that case it's still around a minute of waiting for mount07:52
zygathat is curious07:52
pedronisyes, also the time between the spawn and the first ensure ready is strangely long07:53
pedronis2018-06-13T07:42:47Z  2018-06-13T07:43:49Z07:53
zygaeach mount is slow07:53
zygamborzecki: what is the host storage like? is this a HDD or a SSD? which filesystem are you using07:53
zygaer07:54
zygamwhudson: ^07:54
zyga(bad tab)07:54
mborzeckiheh ;)07:54
mwhudsonbaaaaaah rebooting my laptop fixed it07:56
zygapedronis: question about seeding07:56
zygapedronis: on line 28 we have "mark system seeded"07:56
zygabut then we have more tasks below07:56
zygais that expected07:56
mwhudsonmborzecki: yes, too lazy to remember command line syntax for virtio07:58
mborzeckimwhudson: fwiw it makes a huuge difference here ;)07:59
mupPR snapd#5276 closed: devicestate: support seeding from a base snap instead of core <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/5276>08:00
mwhudsonmborzecki: ok, i'll try to teach it to my bash history :)08:03
Chipacamoin moin08:17
ChipacaI'm en route to the dentist; connection might be flaky08:17
mborzeckizyga: https://www.youtube.com/watch?v=ofeCpN99FU808:18
zygamborzecki: oh, nice, thank you08:19
zygamborzecki: apparmor logo looks a little bit like our flag :)08:19
Chipacazyga: mvo: anything else to note on the conncheck->info pr?08:19
mborzeckizyga: what happened to the the dope penguin with gas mask on?08:20
Chipacaasking because I wouldn't like to trigger a whole spread run for a small change only to then have to do it again :-)08:20
zygamborzecki: whaaat, I didn't know that was the previous logo08:20
mborzeckizyga: https://gitlab.com/apparmor/apparmor this logo08:21
Chipacaooh, 'Add Vulkan abstraction' commit in apparmor08:27
Chipaca(4 weeks ago)08:27
pedroniszyga: not completely, it seems related to how auto-connect works08:32
pedronispstolowski: did you see: http://paste.ubuntu.com/p/BQGMG4pZdM/  the connects at the very end before mark seeded seems a bit wrong08:32
pedroniszyga: pstolowski: ah08:33
pedroniszyga: is the display that is off, they are sorted by id , not really time or sequence08:33
zygaoh drat!08:34
zygaindeed, I didn't see this08:34
zygashould we change that08:34
pedronisI don't know, is definetely more confusing now that we have tasks that add more tasks08:34
pedronisthey will all show up like that at end08:35
Chipacattfn08:38
pstolowskipedronis: oh, do we run things twice? does this auto-connection make sense at all?08:41
pedronispstolowski: it's because is a self autoconnection08:47
pedronispstolowski: we probably can fix that in auto-connect itself08:47
pstolowskipedronis: i didn;t know we have self-autoconnection, what is it for?08:47
pedronispstolowski: tbh it's a bit of a corner case, but is quite important, docker uses it for example08:48
pedronispstolowski: it's usally when the server and the client of something are in the same snap, that's the docker case I think08:48
pstolowskipedronis: ok, what test is this?08:49
pedronispstolowski: test?08:49
pedronisthis is a real image08:49
pstolowskipedronis: ah, allright08:50
pedronispstolowski: anyway, to fix this we would need to keep track of connection already requested in newconns using the connref ID08:51
pedronispstolowski: it's actually a bug btw, not just an opt, because of the hooks (in this case they don't exist, do nothing)08:53
pedronispstolowski: btw do we check in ifacestate.Connect if the connection already exist?08:56
pedronispstolowski: I know at some point doConnect would do nothing if the connection already existed, is that still true? or did we change it08:56
pstolowskipedronis: performance review in a moment, will talk to you afterwards, i need to actually check hits08:57
pstolowski*this08:57
pedronisnp08:58
pstolowskiallright, i'm back09:06
* zyga finished his self review 09:10
pstolowskipedronis: we don't check if connection already exists09:11
pedronispstolowski: I think repo does, but because of the hooks is too late there09:11
pedronispstolowski: we should also add that09:12
pstolowskipedronis: yes09:12
pedronispstolowski: so we need a check in ifacestate.Connect   and a check in doAutoConnect in the 2nd loop to make we don't add the same connection again09:13
mvozyga: I added a mount unit to 528409:22
zyga\o/09:22
zygathank you09:22
pstolowskipedronis: i'll address this later today09:26
pedronisthx09:26
jameshzyga: for https://github.com/snapcore/snapd/pull/5271, I think the only open question was yours about what to do about too-old versions of xdg-desktop-portal.09:30
mupPR #5271: cmd/snap: attempt to start the document portal if running with a session bus <Created by jhenstridge> <https://github.com/snapcore/snapd/pull/5271>09:30
* zyga looks09:30
jameshzyga: I don't have a good answer for that, but the PR doesn't introduce any new problems09:30
jamesh(there's no --version option for any of the daemons, so it'd probably need per-packaging system checks)09:31
zygajamesh: ack09:37
jameshzyga: for snapd delivered via distro packages, we can use a "Conflicts:" header, but that doesn't help when snapd is delivered by the core snap09:38
zygajamesh: I think this is still a problem09:46
zygaAFAIK older portal implementation would not confine non-flatpack apps09:46
zygaso an older version of the portal is essentially a sandbox escape09:46
zyga(well, for files)09:46
mvo5284 needs a second review (should be simple :)09:48
jameshzyga: so, I think the old xdg-desktop-portal  file chooser won't register files with the document portal when it thinks it is talking to unconfined apps (good), but our attempt to bind mount the document portal will fail because the application ID is in a different format (bad)09:52
jameshthe bind mount failing is bad because it will reveal the entire document portal tree, potentially giving access to any files registered to flatpak apps09:53
zygammmm09:57
zygaand if we fail and don't start the app this has other negative side effects09:57
jameshwe explicitly set the document portal mounts to ignore failures so it'd work when the portal code isn't present09:59
zygaI need to jump to a call09:59
jameshokay09:59
zygajamesh: if we ignore the failure, does that ever leave the portal wide open for the app to see?09:59
zygacould we fix that by perhaps bind mounting /var/lib/snapd/void there?10:00
jameshzyga: the apparmor policy lets the app access that mount point, so it is open10:00
jameshlong term, I think it would be better to have a completely private $XDG_RUNTIME_DIR mounted at the usual /run/user/$uid10:01
jameshso if we failed to mount something in, then it just wouldn't be present10:01
Son_Gokuinteresting10:06
Son_Gokuwhat brought this conversation on?10:06
Son_GokuI was just having this convo with the Fedora Workstation guys10:06
jameshSon_Goku: I've been (slowly) working to integrate xdg-desktop-portal with snapd10:06
Son_Gokuyes, I saw the first bits land with snapd 2.3310:07
jameshSon_Goku: it works with xdg-desktop-portal 0.2 (patches have been accepted upstream), but fails open with 0.1.10:07
Son_Gokuwait what10:07
jameshif it failed closed, that would be okay10:07
Son_GokuI need an unreleased version of xdg-desktop-portal now?10:07
Son_Gokuthis is going to be a problem10:07
jamesh0.2 is released10:07
Son_Gokuthis is the latest version: https://github.com/flatpak/xdg-desktop-portal/releases/tag/0.1110:08
jameshgah.  getting versions mixed up10:08
jamesh0.11 is the fixed version10:08
Son_Gokuah10:08
jamesh(not sure where 0.2 came from)10:08
Son_Gokuat the moment, I can't ship snapd 2.33 to Fedora 27, which I'm trying to fix right now10:09
jameshSon_Goku: I suspect it isn't as big a deal for Fedora, where we don't have AppArmor confinement in place10:09
Son_Gokuwell, snapd's confinement is mostly useless anyway, so it's not a big deal in that respect10:10
Son_Gokubut it's still ugly since the document portal moved from flatpak into its own thing10:10
Son_Gokuand that is required for xdg-desktop-portal 0.1110:10
jameshyeah.  Alex moved it so the two services could share the same auth logic10:10
Son_Gokuyep10:15
Son_Gokuwhich means that flatpak in Fedora 27 has to be upgraded to...10:15
Son_Gokuwhich they don't typically do if they don't need to10:15
zygare10:24
mupPR snapd#5314 opened: many: rename snap.Info.Name() to snap.Info.InstanceName(), leave parallel-install TODOs <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/5314>10:32
=== Son_Goku is now known as Conan_Kudo
=== Conan_Kudo is now known as Son_Goku
mborzeckipedronis: just-renames PR ^^10:40
zygamborzecki: I'll co-review11:02
zygamborzecki: I haven't done it all yet but could we perhaps remove Name for a transition period so that no new code lands that uses Name vs InstanceName?11:04
pedronismborzecki: will look11:06
mborzeckizyga: which Name? info.Name() is no more, it's been replaced by InstanceName()11:11
zygaah perfect11:11
zygathat's exactly what I wantee11:12
zyga*wanted11:12
zygato avoid API skew from PRs11:12
zygaI'm at 1/3 of the diff11:12
mborzeckizyga: happy scrolling :) and thanks for going though it11:12
zygapleasure :)11:12
zygaChipaca: ping11:19
Chipacazyga: bonk11:19
zygaChipaca: can you please look at the conversation on https://bugs.launchpad.net/snapd/+bug/177629511:19
mupBug #1776295: `stop` and `disable` should kill all processes regardless of daemon stop-mode <snapd:Incomplete> <https://launchpad.net/bugs/1776295>11:19
zygaI think what is being asked for is not supported by systemd but I want a 2nd opinion11:19
Chipacazyga: we can easily make explicit stop be harder than the systemd one, can't we?11:21
zygadefine explicit stop?11:21
zygais that something other than systemctl stop foo.service?11:21
Chipacazyga: snap stop blah11:21
zygamm11:21
Chipacazyga: or snap remove blah11:21
zygayes, that we can11:21
zygawe can definitely do that11:22
Chipacabehind the scenes we currently do systemctl stop11:22
Chipacawe could easily do killall --user $USER instead11:22
Chipacathat'll learn them to complain11:22
zygapastebin ~/.ssh/id_rsa11:22
zygayeah, it's good that we don't )11:22
zygaanyway, this needs some thinking and discussion11:22
Chipacazyga: forum time?11:23
zygasounds good to me11:23
Chipacabasically it'd mean "stop-mode" is for "internal" stoppage, and perhaps also for "restart", but explicit "snap stop" or "snap remove" would slay the whole namespace or w/e11:23
Chipacazyga: shall you, or should I?11:24
zygaChipaca: I can11:24
zygathank you :)11:24
Chipacazyga: perfect :)11:24
mborzeckididn't we do systemctl kill --kill-who=all on snap stop?11:24
Chipacamborzecki: #177629511:25
mupBug #1776295: `stop` and `disable` should kill all processes regardless of daemon stop-mode <snapd:Incomplete> <https://launchpad.net/bugs/1776295>11:25
Chipacamvo: was your "looks good" on #5312 a +1?11:26
mupPR #5312: store: switch connectivity check to use v2/info <Created by chipaca> <https://github.com/snapcore/snapd/pull/5312>11:26
mborzeckiChipaca: yes, that's i'm referring to, iirc this was discussed a bit while that change was introduced, basically systemctl stop stops all processes in cgroup, now since that no longer works because of stop mode, snap stop <service> was supposed to do the right thing11:29
Chipacamborzecki: that bug says it doesn't (but I haven't confirmed this)11:30
Chipacamborzecki: I also don't know if disable or remove dtrt11:30
mborzeckihmm11:30
zygamaybe I'm wrong11:30
Chipacazyga: never!11:30
zygabut what I see is that there's a desire for different action on "systemctl stop" vs on "snap refresh"11:31
Chipacazyga: yep11:31
zygaChipaca: I need to tell my wife ;)11:31
mborzeckiChipaca: hmmm11:31
Chipacazyga: you're never *locally* wrong11:31
mborzeckiChipaca: so when you do snap stop <...> it ends up in servicestate.Control() which calls systemctl stop ... ?11:31
Chipacamhmm11:32
zygamborzecki: done11:39
mborzeckizyga: as for apparmor & SNAP_NAME, jdstrand suggested introducing another variable in the templates and pick one depending on whether it's outside/inside mount ns11:41
mborzeckianyways, to be ironed out11:42
zygamborzecki ack11:42
zygamborzecki: can you do a simple review for me11:42
zyga531511:42
mupPR snapd#5315 opened: cmd/snap-update-ns: introduce MimicRequiredError, make ReadOnlyFsErro… <Created by zyga> <https://github.com/snapcore/snapd/pull/5315>11:42
zygaI'm trying to shrink my main patch11:42
* cachio afk11:46
niemeyerMorning all11:55
zygahey hey :)11:56
niemeyermborzecki: #5030 needs love11:56
mupPR #5030: packaging/amzn2: initial packaging of 2.32.5 for Amazon Linux 2 <Reviewed> <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/5030>11:56
mborzeckiniemeyer: i think it's ok to close it for now, it'll still be accessible and we can revive it (or build on what Son_Goku proposed) when needed11:57
niemeyermborzecki: But is it not needed?11:57
Son_Gokufor now, no11:57
niemeyermborzecki: I mean, we do want it building fine there as well11:57
Son_Gokuniemeyer, most likely, this will be obsoleted by eventual introduction of snapd into EPEL11:57
niemeyerSon_Goku: Heya11:57
Son_Gokuniemeyer: Hi!11:58
mvoChipaca: woah, that merge was quick, did you click merge right after I clicked "approve"?11:58
mupPR snapd#5312 closed: store: switch connectivity check to use v2/info <Created by chipaca> <Merged by chipaca> <https://github.com/snapcore/snapd/pull/5312>11:58
niemeyerSon_Goku: Sorry for not responding quickly enough yesterday.. it's my understanding that all of our g-s are submitted upstream as well..11:58
Chipacamvo: got a notification of your approve11:58
Chipacamvo: mashed the merge button11:58
Chipacamvo: yes11:58
mvoChipaca: heh11:58
niemeyerSon_Goku: The maintainer was also in a sprint in London with us just a week ago or so11:58
mvoChipaca: impressive11:58
Chipacamvo: thank you for the +111:59
niemeyerSon_Goku: Unfortunately it's a bit tricky to get things flowing when there's so much interest yet a disjoint set of needs11:59
Son_Gokuniemeyer, I'm mainly worried about the g-s plugin rotting to the point I'll be forced to disable it11:59
Son_Gokuthe experience is... not great11:59
mvoChipaca: you did all the hard work!12:00
Son_Gokuniemeyer, the main gaps are snap channels and basic perm management12:02
Son_Gokuthe snap channels one is a biggie, because it leads to a confusing experience in g-s12:02
niemeyerSon_Goku: Yeah12:03
Son_Gokuthe perm management is less important, because snapd confinement doesn't work in Fedora anyway12:03
niemeyerSon_Goku: One idea we've been considering is shipping a snap-only version of it as a snap12:03
mupPR snapd#5081 closed: interfaces/apparmor: add chopTree <Created by zyga> <Closed by zyga> <https://github.com/snapcore/snapd/pull/5081>12:03
Son_Gokuniemeyer, yes, I saw the snap-master branch of g-s12:03
Son_GokuI'm not sure that's a good idea12:03
Son_GokuI think it might be better to create an independent DE-agnostic tool12:04
Son_Gokuwhich would be useful for DEs that don't have a software center12:04
zygathere's an elementary app called Snapper or something similar but I think the experience there is not good at all :/12:04
Son_GokuSnaptastic12:04
niemeyerSon_Goku: Best would be to have a single tool working everywhere with everything12:04
Son_Gokubut yeah, it's kind of weird12:04
zygasnaptastic, thanks12:04
Son_Gokubut it could be an interesting foundation for the concept12:05
niemeyerSon_Goku: But that's taking some time to sort out, and we want to make *something* available that sorts out the GUI side of things while we get the ideal in place12:05
Son_Gokuzyga, one idea would be to use the libyui foundation libraries to build a UI agnostic frontend12:05
Son_Gokulike what I did for DNF with dnfdragora: https://github.com/manatools/dnfdragora12:06
Son_Gokuthat would even give a reasonable experience for people who'd like an aptitude-like interface for snap management12:06
Son_Gokuzyga: screenshots of dnfdragora are in https://blog.mageia.org/en/2017/07/21/dandifying-mageia-part-2/12:07
zygapersonally I don't think aptitude like approach is needed for snaps12:08
zygasimply because you don't have the zoo of weird packages like -common or -bin or whatever12:08
Son_Gokubut you need a way for people to find and manage them12:08
zygagnome software has pretty close idea to a proper app store12:09
Son_Gokuwell, then, get the snap channel support in g-s ;)12:09
popeyWe did some design work on g-s last week.12:11
zygapopey: cool, any mockups? :)12:15
popeyloads of sketches, its over to design now to do that12:15
mupPR snapd#5284 closed: data/systemd/snapd.run-from-snap: ensure snapd tooling is available <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/5284>12:17
zygamvo: do we need to do anything about https://github.com/snapcore/snapd/pull/5284#pullrequestreview-12829317012:18
mupPR #5284: data/systemd/snapd.run-from-snap: ensure snapd tooling is available <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/5284>12:18
mvozyga: you mean libexecdir?12:26
zygayes12:27
mvozyga: I replied iirc, is the reply unclear (or did I forgot to submit it :/12:27
zygaI didn't see a reply12:27
mvozyga: """Thanks for checking. This code only runs on ubuntu-core systems, so we can hardcode the (known) libexecdir here.""" <- maybe github ate it :(12:28
zyga+112:28
zygaI see it now12:28
zygathanks12:28
mvozyga: \o/12:28
mvozyga: thanks for your careful review12:28
Son_Goku:(12:28
mupPR snapd#5316 opened: store, et al: kill dead code that uses the bulk endpoint <Created by chipaca> <https://github.com/snapcore/snapd/pull/5316>12:28
Chipaca^^^^ if anybody enjoys reviewing a +99 -1333 PR, now's your chance!12:28
* Chipaca -> lunch12:29
mborzeckiclient.actionData.Name appears to be unused, anyone recalls what was the purpose of this field?12:52
Son_GokuChipaca, less Go code in the world makes me happier :)12:56
Chipacamborzecki: it was the name of the snap12:57
mborzeckiChipaca: 'was' ?12:57
Chipacamborzecki: git show d01831fda7995cc0f2f207000adab192fb2fbf6d12:58
mvoChipaca, zyga we are still in a meeting, might overrun a litle bit13:00
zygaack13:00
Chipacamborzecki: was removed in 15edad32e3d572a2ddd53df3f5b7a9eab4b2333313:01
Chipacamborzecki: it's ignored server-side, is probably why13:01
Chipacamborzecki: KILL IT WITH FIRE13:01
zygamvo: should we wait?13:02
mborzeckiChipaca: oh i won't do that ;) i plan to use it instead13:02
zygamvo: or shall we get started?13:02
mvozyga: go ahead I would say13:02
niemeyerzyga: Meeting running late here.. we'll be there in a moment13:02
zyganiemeyer: ack13:02
mborzeckiChipaca: actually added Instance to SnapOptions, just to find that Name field a bit later13:02
Chipacamborzecki: ¯\_(ツ)_/¯13:03
Chipacamborzecki: removing it seems the saner thing to do i think13:03
Chipacamborzecki: sorry i didn't see your comment about using it instead13:21
Chipacamborzecki: that works also :-)13:21
Chipacamborzecki: but13:22
Chipacamborzecki: what would you use it for?13:22
mborzeckiChipaca: snap install foo.snap --instance foo_bar13:22
Chipacamborzecki: the reason it's not used is because in doSnapAction, the name is already in the path13:22
Chipacamborzecki: that is, it's a POST to /v2/snaps/<name>13:23
Chipacamborzecki: so saying name in the body of the post is redundant13:23
Chipacaredolent13:23
Chipacarefulgent13:23
mborzeckiChipaca: right, but if you try to install it as an instance than i can either use another form field or reuse this13:24
mborzeckiChipaca: and it's also POST /v2/snaps, so the current name comes from the snap itself13:24
Chipacamborzecki: /v2/snaps is doMultiSnapAction13:25
mborzeckiChipaca: i'm doing the variant which sideloads a snap file, hits the same endpoints but uploads a snap too13:29
Chipacamborzecki: ah! a'ight13:31
* zyga needs to feed the dog, brb13:40
zygare13:51
=== pstolowski is now known as pstolowski|lunch
mborzeckiChipaca: seems to work now https://paste.ubuntu.com/p/3WJZthdSyY/ :P14:21
zygajdstrand: hey14:40
zygajdstrand: do you have a sec?14:40
Chipacapedronis: in #5317 I have increased coverage of details.go while keeping to the spirit of the PR :-D14:47
pedronisChipaca: ah14:57
=== pstolowski|lunch is now known as pstolowski
Chipacapedronis: perhaps not what you were hoping for :)14:57
pedronislet's see what we get when the test have run14:58
Chipacapedronis: locally, coverage of store went from 88.3% (96.8% in details.go) to 87.9% (96.6% in details.go)15:01
Chipacathe same two lines are not uncovered15:01
Chipacaer, not covered*15:01
mupPR snapd#5317 opened: overlord: introduce a gadget-connect task and use it at first boot <Created by pedronis> <https://github.com/snapcore/snapd/pull/5317>15:03
* zyga iret's from real-life interrupt 15:11
pedronispstolowski: I will look at your disconnect hooks PR again in the morning15:16
=== jkridner is now known as jkridner|afk
* cachio lunch15:40
pstolowskipedronis: ty15:42
mupPR snapd#5318 opened: interfaces/builtin: add new cuda-support interface <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/5318>15:45
diddledanpreview of what I'm working on https://usercontent.irccloud-cdn.com/file/h6uU1nG3/image.png15:58
zyga@diddledan I'd love if gog would itself distribute snaps15:59
diddledanyeah, they don't want to though15:59
zygadid we ask?15:59
diddledanlast I saw they're "monitoring packaging systems"16:00
zygadiddledan: I know some people there (or I used to, I need to check)16:00
zygapstolowski, mborzecki: can you guys give me a quick +1 on 531916:00
zygait's a mv from package to package16:00
mupPR snapd#5319 opened: cmd/snap-update-ns,strutil: move PathIterator to strutil, add Depth helper <Created by zyga> <https://github.com/snapcore/snapd/pull/5319>16:00
zygaand a trivial one liner method16:00
zygaI can split those if you'd feel better16:00
pstolowskizyga: done16:03
zygamvo: hey, do you want to have the call about core?16:03
zygapstolowski: thank you!16:03
pstolowskizyga: maybe you will know:16:03
zygayes?16:04
pstolowskizyga: when we run spread tests, do we ever reuse the test user home dir between runs of entire suite?16:04
zygaI think we never clean it16:04
zygayes, we reuse it16:04
zygaI only recall seeing code that makes it16:05
zygabut then that's that16:05
zygadiddledan: gog has many similarities with steam16:05
zygadiddledan: so you may look at the (now closed) steam-support interface16:05
zygaas well as the surrounding discussions16:06
pstolowskizyga: just to be sure: i'm not talking about not cleaning it between individual tests; i mean possibility of having leftovers between executions of entire suite16:06
zygapstolowski: I think it is the same16:06
zygapstolowski: it is only clean before first test :)16:06
zygaafter that, until the machine is recycled, we don't touch that16:06
zygathank you!16:26
* zyga just waits for green then proposes the next PR16:26
zygawell, reopens the next PR16:26
mvozyga: lets do it tomorrow morning (unless you have sometihng urgent)16:27
zygamvo: no, nothing urgent16:27
mvozyga: cool, lets do it around 9ish tomorrow?16:27
zygasounds good16:27
mvocool16:28
om26erpopey: ping16:35
zygaeh, blasted fedora 28 failure16:35
om26erpopey: regarding axel snap, do you think we can enable its auto builds now ?16:36
popeyom26er: heya. it alreay is hooked up. I did it when I closed the bug report.16:39
popeyom26er: but it fails to build https://build.snapcraft.io/user/snapcrafters/axel16:39
popeyCan't exec "aclocal": No such file or directory at /usr/share/autoconf/Autom4te/FileUtils.pm line 326.16:39
popeyhttps://launchpadlibrarian.net/373136884/buildlog_snap_ubuntu_xenial_amd64_1c7edf66b8a27bd4ca35886b0511f15e-xenial_BUILDING.txt.gz16:39
om26erwoa, it fails on all arches16:40
zygamborzecki: shall I change https://github.com/snapcore/snapd/pull/531516:41
mupPR #5315: cmd/snap-update-ns: introduce MimicRequiredError, make ReadOnlyFsErro… <Created by zyga> <https://github.com/snapcore/snapd/pull/5315>16:41
zygamborzecki: I think only you can test this https://github.com/snapcore/snapd/pull/531816:43
mupPR #5318: interfaces/builtin: add new cuda-support interface <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/5318>16:43
cachiomborzecki, hey17:03
cachiomborzecki, I created a new image for arch and when I run the tests I get https://paste.ubuntu.com/p/gWm7dzkKFN/17:03
cachiomborzecki, it is checking for updates17:04
cachiobut there are not new updates17:04
mupPR snapd#5319 closed: cmd/snap-update-ns,strutil: move PathIterator to strutil, add Depth helper <Created by zyga> <Merged by zyga> <https://github.com/snapcore/snapd/pull/5319>17:08
mupPR snapd#5081 opened: interfaces/apparmor: add chopTree <Created by zyga> <https://github.com/snapcore/snapd/pull/5081>17:10
zygamborzecki, jdstrand, Chipaca: I updated https://github.com/snapcore/snapd/pull/5081 and it is ready for another review17:10
mupPR #5081: interfaces/apparmor: add chopTree <Created by zyga> <https://github.com/snapcore/snapd/pull/5081>17:10
mborzeckicachio: let me take a quick look, don't know why it's not showing 'there is nothing to do' message17:17
cachiomborzecki, we should remove the update from the snapd test suite17:18
mborzeckicachio: pacman got updated recently, maybe it's showing different output when there are no updates now17:18
cachioI mean, we don't need to update all the packages for arch17:18
cachiomborzecki, I am updating the images every 3 weeks17:19
cachiomborzecki, what do you think?17:19
mborzeckicachio: well in theory we ought to be17:19
mborzeckicachio: i'll take a quick look, it's probably something trivial17:19
mborzeckicachio: can I use this image somehow, or have you replaced the one that we used before?17:20
cachiomborzecki, I already remove the image17:20
cachioI could create a new one17:21
mborzeckicachio: can you built it and name it differntly than the one we have now? i'll update spread.yaml locally to use it17:22
cachiomborzecki, sure17:22
cachiomborzecki, in progress17:23
cachiomborzecki, arch-linux-64-new-v2018061317:31
cachiothis is the image17:31
mborzeckicachio: thx17:33
zygaI’m going for a bike run17:46
zygaSee you later17:47
mborzeckicachio: right, so the logic in prepare_project for arch is wrong, i'll try to do a quick fix17:53
cachiomborzecki, great, tx17:53
=== pstolowski is now known as pstolowski|afk
mborzeckihmm my shellcheck got updated to 0.5.0 and it's rasing some issues in tests/lib/*.sh18:07
mupPR snapd#5320 opened: tests/lib/prepare-restore: fix upgrade/reboot handling on arch <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/5320>18:11
mborzeckicachio: ^^18:11
cachiomborzecki, tx18:18
mupPR snapd#5030 closed: packaging/amzn2: initial packaging of 2.32.5 for Amazon Linux 2 <Reviewed> <Created by bboozzoo> <Closed by niemeyer> <https://github.com/snapcore/snapd/pull/5030>18:55
zygare19:46
* zyga is safely back from biking19:46
cachiozyga, if you have 5 minutes #532019:57
cachiothanks19:57
mupPR #5320: tests/lib/prepare-restore: fix upgrade/reboot handling on arch <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/5320>19:57
mupPR snapd#5320 closed: tests/lib/prepare-restore: fix upgrade/reboot handling on arch <Created by bboozzoo> <Merged by zyga> <https://github.com/snapcore/snapd/pull/5320>20:01
zygacachio: pleasure :-)20:01
zygajdstrand: hey, around?20:01
jdstrandmeeting20:02
cachiozyga, tx20:02
Lukeguys when I do a ruby build in a build-override, how do I move those files into the stage then?20:19
Chipacambuahaha, got 'snap info' talking to v2/info \o/20:24
Chipacasergiusens: you around?20:25
sergiusensChipaca: yup20:25
Chipacasergiusens: two things20:25
sergiusensLuke: make sure they end up in `$SNAPCRAFT_PART_INSTALL`20:26
sergiusensChipaca: one by one20:26
Chipacasergiusens: one, building a cross-platform snap-pack turned out to be a lot more work than I thought it would be, so it's on my plate as a Thing (as opposed to something I slot in between the cracks)20:26
Chipacasergiusens: two was Luke and you've done that :-)20:26
Chipacasergiusens: as i see it i should be getting to work on it early next week20:27
Chipacabut I don't own my priorities :-)20:27
sergiusensChipaca: oh neat, does that include replacing mksquashfs too or just snap? I wonder, not require 😉20:28
Chipacasergiusens: it does not include  replacing mksquashfs20:29
mupPR snapd#5321 opened: tests: fix interfaces-contacts-service test retrying to remove share dir <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/5321>20:29
Lukesergiusens: thanks. is that var documented somwhere? I couldn't find it in the docs20:29
Chipacasergiusens: it's mostly a lot of careful separation of code into cross-platformy bits, but also a bunch of figuring out how to run a test suite on windows :-)20:29
Chipacasergiusens: I need to be in a special mindset for that last bit20:30
Chipacaor hire somebody :-D20:30
Chipaca(number of times I've gone for "hire somebody" in that situation: 3)20:30
sergiusensLuke uses are describe on https://snapdocs.labix.org/scriptlets/4892 or https://docs.snapcraft.io/build-snaps/scriptlets20:30
sergiusensChipaca: use appveyor, that is what we use20:31
Lukei saw the scriptlets docs before. there's no mention of $SNAPCRAFT_PART_INSTALL besides in passing in an example20:31
Lukei guess I'm looking for an explanation of the best practices/intended use of $SNAPCRAFT_PART_INSTALL etc20:32
Lukethanks btw20:32
Chipacasergiusens: nice, i'll look that up20:32
Chipacasergiusens: what happens every time I start is that I'm an hour into reading and I'm just adding to a stack of things to figure out :-) hence why i need to set aside time for it20:34
Chipacasergiusens: for example, appveyor seems to boil down to "run msbuild for you"20:35
Chipacaso no i need to learn msbuild20:35
Chipacaetc :)20:35
Chipacasergiusens: no worries, but not quick for me20:35
Chipacai'll get to it next week20:35
Chipacahopefully20:35
zygajdstrand: if you still have time today please look at chopTree again20:39
zygaIt now does what you asked for20:39
Chipacazyga: if you've got beans after the bike run, #5316 :-D20:39
mupPR #5316: store, et al: kill dead code that uses the bulk endpoint <Created by chipaca> <https://github.com/snapcore/snapd/pull/5316>20:39
Chipacazyga: also 'bike run' seems like you're doing something wrong :-)20:40
jdstrandzyga: ok, it's on my list. it may be tomorrow20:44
zygaChipaca: that explains the odd stare ;-)20:53
zygaI’ll read it first thing tomorrow20:54
jdstrandniemeyer: hi! can you add this to your queue to give some thought: https://forum.snapcraft.io/t/camera-raw-usb-plugs-auto-connect-for-qtchildid/2917/421:18

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