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

mborzeckimorning05:18
zygaHey Hey05:37
mborzeckiso we have 2.32.105:38
zygaIndeed we do05:38
zygaThe urgent fire should be out now05:39
mborzeckigot a review on 4908 from jdstrand last night, think he got confused with all the arrays getting passed to sc_mkdir_and_mount_and_glob_files()05:39
zyga2.32.2 could add your nvidia support05:40
mborzeckilanding this, with a test, would be nice05:41
zygaYes. Your test yesterday was a good start05:41
mborzeckithat thing on 14.04 was a bit worrying, idk why you'd get permission denied when trying to mount tmpfs inside <root>/var/lib/snapd/lib/vulkan05:43
mborzeckizyga: per your comment, the same flags to configure for all ubuntu variants right?05:54
zygare06:57
* zyga is done with kids & dog06:57
=== mborzeck1 is now known as mborzecki
* zyga notices new systemd release in artful08:01
mborzeckibtw. i've bumped aur package to 2.32.108:22
zygamborzecki: thank you!08:24
zygaI will review the update to the othe PR soon08:24
mborzeckii'll be switching to ubuntu in a couple of mins to double check that things still work fine08:24
Guest90825hello08:32
Guest90825nick08:32
zygahey Guest9082508:32
* zyga updated https://github.com/snapcore/snapd/releases/tag/2.32.108:32
zygamborzecki: thanks08:32
CN_vichellp08:34
CN_vic?08:34
zygaCN_vic: how can we help you?08:34
CN_vic哈哈08:34
CN_vicno08:35
CN_vic thanks08:35
CN_vicbye08:35
pedronispstolowski: I did another pass over interface hooks,  as I noted we are not very consistent with returning xxxRef types wrt pointer or not, not here, but a follow up should clean that up I think08:40
pstolowskipedronis: thank you, yes i just saw your comments. will address in a followup, thanks again08:41
zygahmm08:47
zygadid anyone see08:47
zyga2018-03-27 08:21:40 Cannot allocate google:ubuntu-14.04-64: cannot perform Google request: Get https://www.googleapis.com//compute/v1/projects/computeengine/zones: oauth2: cannot fetch token: Post https://accounts.google.com/o/oauth2/token: net/http: TLS handshake timeout08:47
mborzecki-ubuntuzyga: retry?08:48
zygagreyback: can you please merge master into 454508:50
greybackzyga: ack, on it08:51
zygagreyback: and please run go fmt08:51
zygax11.go is off08:51
zygagreyback: you also have small comment on 493208:53
greybackyep, saw that08:54
zygahttps://github.com/snapcore/snapd/pull/4920 needs a 2nd review08:58
mupPR #4920: timeutil: in Human, count days with fingers <Created by chipaca> <https://github.com/snapcore/snapd/pull/4920>08:58
zygaperhaps mborzecki-ubuntu or pstolowski08:58
om26erpopey: ping08:58
zygapstolowski: what's the plan on https://github.com/snapcore/snapd/pull/4917 ?08:58
mupPR #4917: repo: added repo ConnectionsInfo method (for the new snap connections API) <Created by stolowski> <https://github.com/snapcore/snapd/pull/4917>08:58
popeyom26er: pong!09:00
om26erpopey: new Android Studio is out, could you please merge this PR https://github.com/snapcrafters/android-studio/pull/1709:00
mupPR snapcrafters/android-studio#17: Release version 3.1.0.16 <Created by om26er> <https://github.com/snapcrafters/android-studio/pull/17>09:00
popeyom26er: on it!09:01
om26eralso kindly provide input on https://github.com/snapcrafters/sublime-text/pull/809:01
mupPR snapcrafters/sublime-text#8: Remove '3' from snap name <Created by om26er> <https://github.com/snapcrafters/sublime-text/pull/8>09:01
mborzecki-ubuntuheh, I already viewed 4920 but didn't click 'submit review'09:02
om26erpopey: ^09:02
mborzecki-ubuntuit'd be useful if github had a notification or sth that you have unfinished reviews09:02
popeyhehe, that one again. okay!09:02
om26erpopey: I have added my input on that one, I consulted the upstream as well.09:03
popeyok, will take a look.09:03
pedronis#4931 needs a second review09:03
mupPR #4931: configcore: give a chance to immediately recompute the next refresh time when schedules are set <Created by pedronis> <https://github.com/snapcore/snapd/pull/4931>09:03
pstolowskizyga: i'll address your comments soon, not sure about PlugInfo/SlotInfo vs refs suggestion09:03
zygasure, it was just a suggestion09:04
pedronismborzecki-ubuntu:   #4571 needs to be closed?09:07
mupPR #4571: data, cmd, packaging: use autotools to generate artifacts under data <Blocked> <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/4571>09:07
mborzecki-ubuntupedronis: i'll close it09:07
pedroniszyga: seems we have quite a few interface PRs in need changes since a while09:08
zygapedronis: yeah, I'm looking at PRs now09:08
zygaI hope to garden somse09:08
mupPR snapd#4571 closed: data, cmd, packaging: use autotools to generate artifacts under data <Blocked> <Created by bboozzoo> <Closed by bboozzoo> <https://github.com/snapcore/snapd/pull/4571>09:08
zygaWe hit some timeouts on pulling snaps from the store09:11
mborzecki-ubuntuFetching pc-kernel ...  <kill-timeout reached>09:11
greybackzyga: 4545 has master merged, gofmt was happy wiht x11.go for me? 4932 has comment addressed09:14
mborzecki-ubuntuif 4908 fails again i should probably use this as an occasion to merge master :/09:14
zygathank you, it's looking good09:15
mupPR snapd#4940 opened: RFC: added UDevMonitor for future hotplug support <Created by stolowski> <https://github.com/snapcore/snapd/pull/4940>09:18
mupPR snapd#4941 opened: vendor: update gopkg.in/yaml.v2 to the latest version <Created by zyga> <https://github.com/snapcore/snapd/pull/4941>09:50
zygapstolowski: reviewed 494009:57
pstolowskizyga: thanks!09:59
pstolowskizyga: 4923 needs de-conflicting10:02
zygapstolowski: it needs investigation what to do, it was just a test PR10:02
zygaI will close it for now10:03
pstolowskiack10:03
mupPR snapd#4923 closed: spread.yaml: look for signs of //deleted mounts <Created by zyga> <Closed by zyga> <https://github.com/snapcore/snapd/pull/4923>10:03
mborzecki-ubuntuzyga: pushed a fix for autogen in 490810:04
zygamborzecki-ubuntu: can you do the master dance with https://github.com/snapcore/snapd/pull/4875 please10:09
mupPR #4875: cmd/snap-confine: fix ptrace rule with snap-confine peer <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/4875>10:09
zygait should be green now10:09
mborzecki-ubuntuzyga: it can be closed now, 2.32 was merged back to  master, and this change was part of 2.32 already10:23
mupPR snapd#4875 closed: cmd/snap-confine: fix ptrace rule with snap-confine peer <Created by bboozzoo> <Closed by bboozzoo> <https://github.com/snapcore/snapd/pull/4875>10:26
zygamborzecki: sorry, I'm slow todat11:12
mborzeckizyga: hm?11:12
zygacan you please walk me through 484411:12
zygahttps://www.irccloud.com/pastebin/okBoncVR/11:15
zygapedronis: is the store experiencing any issues?11:15
pedronisnot particularly at this moment11:16
pedronisthere were some issues with downloads, not sure if they were fully resolved11:16
pedroniszyga: I also need to review 484411:17
zygamborzecki: you have feedback from jdstrand on https://github.com/snapcore/snapd/pull/450911:20
mupPR #4509: interfaces/builtin: add support for software-watchdog interface <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/4509>11:20
zygaikey: hey11:21
zygaikey: long time no talk (or see)11:21
zygaI'm going through various PRs and I noticed there's some feedback on https://github.com/snapcore/snapd/pull/4538 (steam support)11:21
mupPR #4538: interfaces/builtin: Add new steam-support interface <Created by ikeydoherty> <https://github.com/snapcore/snapd/pull/4538>11:21
zygais this waiting on updates from you?11:22
ikeyzyga, yes, just not a good time at the moment sorry11:24
zygagreyback: I added one more idea to your x11 PR11:26
zygagreyback: have a look and tell me if I'm nuts11:26
zygaikey: that's all right, I just wanted to catch up11:26
zygaikey: how are you doing?11:26
ikeynot good, hence not good time. sorry. you?11:26
=== pstolowski is now known as pstolowski|lunch
zygaikey: I would say never better but that's not true11:28
zygaikey: but it's been worse too so that's a charm :)11:28
ikeyhandy when you've an upside :]11:29
zygapedronis: more core download issues11:41
zygapedronis: I restarted the affected tests11:41
pedroniszyga: yea, I think there are still download issues11:42
zyga+ tar -C/ -xf /home/gopath/src/github.com/snapcore/snapd/snapd-state.tar.gz11:43
zygatar: /home/gopath/src/github.com/snapcore/snapd/snapd-state.tar.gz: Cannot open: No such file or directory11:43
zygaI wonder what could cause the spotify snap on opensuse not to support high-dpi while the same snap works on ubuntu 17.1011:47
zygamaybe distro patches missing somewhere?11:47
zygabut unlikely since all of opensuse works ok11:47
mupPR snapd#4942 opened: cmd/snap: user session application autostart v3 <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/4942>11:49
mborzeckioff to pick up my daughter from school, bb for standup11:55
zygaCaelum: I updated my review of your package updates11:56
jdstrandmborzecki (cc zyga): I did get confused initially, but then mentioned in 'Update:' what you could do. however, the refactor is good enough for me12:24
zygaI’m afk for now12:28
mborzeckijdstrand: thanks for the review :)12:40
mupPR snapd#4871 closed: cmd/snap-confine: fix Archlinux compatibility <Created by Erick555> <Merged by zyga> <https://github.com/snapcore/snapd/pull/4871>12:49
jdstrandmborzecki: np, thanks for working on it!12:53
mupPR snapd#4943 opened: tests: adding debian sid to google backend <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/4943>12:55
=== pstolowski|lunch is now known as pstolowski
zygastandup time13:01
* kalikiana going for half a lunch break13:08
zygaerror: cannot install "core": cannot query the store for updates: got13:14
zyga       unexpected HTTP status code 404 via POST to13:14
zyga       "https://api.snapcraft.io/v2/snaps/refresh"13:14
zygapedronis: ^ that's unexpected, right?13:14
pedroniszyga: where?13:14
pedronisthat's my PR, yes it's expected until I rerun the tests13:14
zygahttps://travis-ci.org/snapcore/snapd/builds/356519762?utm_source=github_status&utm_medium=notification13:15
zygayeah13:15
zygaok13:15
zygajdstrand: I think https://github.com/snapcore/snapd/pull/4932 is ready now and your feedback is applied13:21
mupPR #4932: interfaces/content: add rule so slot can access writable files at plug's mountpoint <Created by gerboland> <https://github.com/snapcore/snapd/pull/4932>13:21
pedronisniemeyer: I labeled all those branches critical13:26
zygahttps://github.com/snapcore/snapd/pull/4844 made me realise we have overloaded the term system key13:27
mupPR #4844: overlord/snapstate: allow core defaults configuration via 'system' key <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/4844>13:27
mborzeckizyga: yeah, it's a 'nickname'13:27
mborzeckizyga: as agreed during the sprint ;), '$core' was another candidate13:28
mborzeckizyga: master already has some bits for making `snap set system foo.bar=baz` and `snap get system` work13:29
jdstrandmborzecki: I was thinking about code clarity and added https://github.com/snapcore/snapd/pull/4908/files#r177422132 (not a blocker)13:30
mupPR #4908: [RFC] cmd/snap-confine: attempt to detect if multiarch host uses arch triplets <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/4908>13:30
zygahey jdstrand, how are you doing? :-)13:31
zygamborzecki: yeah, that's fine, I just found it funny13:31
mborzeckijdstrand: thanks, i can push it in a while, this part is tricky so comments are obviously helpful13:32
vidal72[m]zyga: jdstrand should I make PR with patch proposed in https://forum.snapcraft.io/t/apparmor-issues-with-default-install-dir/4568/213:32
jdstrandzyga: hey, pretty good. how are you?13:32
jdstrandmborzecki: thanks13:32
jdstrandzyga: re 4932> done13:34
jdstrandvidal72[m]: oh, I thought you were in the process of that. if you are so inclined, sure, if not, I can.13:36
zygajdstrand: thank you (for both); I'm feeling a bit uneasy with my back lately but long walks with the dog make it go away13:36
jdstrandvidal72[m]: also, I liked '@{INSTALL_DIR}="{/snap,/var/lib/snapd/snap}"' cause I felt it was slightly clearer in this case, but both yours and mine are equivalent policy-wise13:37
pedroniszyga: I recheck that error will go away if I rerun the tests, but that branch  needs  a merge from master and I would prefer to wait a bit for feedback on the prereqs13:37
jdstrandzyga: if you don't already, you might consider a standing desk13:37
jdstrandI found it helped me a lot. bonus points if you add an under-the-desk treadmill13:38
zygajdstrand: oh, I have, it's planned already13:38
jdstrandnice13:38
zygajdstrand: once we save some money we plan to transform a tarrace into my office, make it habitable all year and put a standing desk there13:38
zygathat will also move me out of the living room :)13:39
jdstrandheh, nice13:39
zygathat's for spring next year though13:39
zygafor now, it's the walks :)13:39
jdstrandzyga: it's really just about not sitting for long periods all day, so yeah, a dog walk works for that perfectly :)13:40
zygayeah, I agree13:41
zygaplus, he's very happy not to be in a shelter anymore :)13:41
jdstrand:)13:48
mupPR snapd#4944 opened: interfaces: add /var/lib/snapd/snap to @{INSTALL_DIR} <Created by Erick555> <https://github.com/snapcore/snapd/pull/4944>13:55
mupPR snapcraft#2036 opened: errors: remove stack data when sending to sentry <Created by sergiusens> <https://github.com/snapcore/snapcraft/pull/2036>14:27
niemeyerkalikiana: https://forum.snapcraft.io/t/support-for-passthrough-into-snap-yaml/469814:32
mupIssue snapcraft#2037 opened: core refresh in container build breaks build <bug> <Created by sergiusens> <https://github.com/snapcore/snapcraft/issue/2037>14:33
zygacachio: I reviewed https://github.com/snapcore/snapd/pull/4721#pullrequestreview-107307595 and have one suggestion but let's please do it in a follow-up14:35
mupPR #4721: tests: update interface tests to remove extra checks and normalize tests <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/4721>14:35
kalikiananiemeyer: Awesome +114:37
zygapstolowski: did you see the ping on the forum?14:38
pstolowskizyga: yes. looking into the code and where it comes from14:38
zygait's an un-handled ErrNoState14:38
petanhello, I am getting Built, failed to release14:40
petanis there any way to debug why?14:40
petanthere are no errors in logs14:40
zygapetan: can you please provide some more information/14:40
petanhttps://build.snapcraft.io/user/huggle/huggle3-qt-lx/17672414:40
petanthat's the build log14:40
petanit doesn't say anything else than Build failed to release14:41
petanbtw I managed to build the .snap file using snapcraft on my own PC without any issues14:42
pstolowskizyga: yes i see that14:42
zygakalikiana: ^14:42
zygakalikiana: is that when the store for whatever reason fails to release a snap to a channel?14:43
zygapetan: it feels like a store side fluke14:43
zygapetan: but please talk to kalikiana about it14:43
zygapstolowski: I think we want to check the state from evan14:43
petanhmm so solution is to wait and try to click rebuild later?14:43
zygapstolowski: to see if this is broken state14:44
zygapetan: as I said, I don't know fully, please wait for a response from kalikiana or sergiusens who know this part better14:44
petanok14:44
zygapstolowski: or correct state and broken code14:44
zygapstolowski: unless you find some obviously broken piece of code somewhere14:44
pstolowskizyga: yes, i was going to suggest that. note, this error is actually not fatal, just logged, i'm not sure what's the reasoning behind that logic14:45
kalikianazyga: petan Hmmm the build seems fine indeed.14:48
sergiusenszyga: that looks more like a store issue, roadmr ^14:48
zygapstolowski: dunno, but it looks fundamental and we need to get to the bottom of it14:49
roadmrsergiusens, zyga : yes, we're looking at intermittent upload/download issues14:49
pstolowskizyga: sure14:49
zygapstolowski: if you see ev, can you ask him about state.json please14:49
pstolowskizyga: I did via the forum14:49
* zyga -> dinner14:49
niemeyerpedronis: #4931 reviewed.. I suggested a simpler and more general approach there14:50
mupPR #4931: configcore: give a chance to immediately recompute the next refresh time when schedules are set <Critical> <Created by pedronis> <https://github.com/snapcore/snapd/pull/4931>14:50
niemeyerpedronis: LGTM if you're happy with that as well14:50
jdstrandpstolowski: hi! fyi, my comments in https://forum.snapcraft.io/t/please-help-testing-2-32-in-beta/4696/714:52
pstolowskijdstrand: yep, saw that, thanks! did you ever have dotnet-sdk installed?14:53
jdstrandpstolowski: yes (I just updated my comment to say that)14:53
jdstrandI don't recall when though...14:53
pstolowskijdstrand: can you send me your state?.json?14:54
jdstrandsure14:54
jdstrandpstolowski: should I stop snapd before sending it?14:54
pstolowskijdstrand: yes14:54
mupBug #1759294 opened: Please display confinement level information in 'snap info' command output <Snappy:New> <https://launchpad.net/bugs/1759294>14:58
jdstrandpstolowski: emailed15:00
cachiozyga, sure I'll take a look now15:01
pedronisniemeyer: so doing it even on errors?15:02
pedronisfor any config change15:02
niemeyerpedronis: Yeah15:13
pedronisok15:13
niemeyerpedronis: Shouldn't be a problem, and it's a pretty rare and manual event.. much easier for us to reason about15:14
zygacachio: thank you for doing that PR, it's pretty big!15:16
zygawoah15:18
zygajdstrand: do you see the dotnet-sdk snap in snap interfaces anywhere?15:18
jdstrandzyga: no15:19
zygathis is very interesting and odd15:19
zygapstolowski: let me know what you find out15:19
mupPR snapcraft#2038 opened: Add an option for setting npm flags option <Created by guilhem> <https://github.com/snapcore/snapcraft/pull/2038>15:21
nessitapetan, hey, were you asking about the huggle snap?15:23
petanyes, it builds but doesn't release now, it always worked15:23
petanhttps://build.snapcraft.io/user/huggle/huggle3-qt-lx/17672415:23
nessitapetan, we are having some issues with our snap storage access that is being worked on, and that caused the review of your revision 640 to be stuck. I unstucked it and now the rest of the revisions are being processed, see https://dashboard.snapcraft.io/snaps/huggle/15:23
petanok thanks15:24
nessitapetan, you may need to go to dashboard and release the revisions manually15:24
zygathank you nessita !15:25
nessitazyga, \o/15:25
pstolowskizyga: ok, so the problem is we have 4 stray connections for a removed snap in the state; these were auto-connections from the snap to core, so we consider  that snap affected by core upgrade. now i need to find out why we didn't remove these connections when snap was removed15:32
pstolowskiniemeyer: ^15:32
zygapstolowski: that's nice15:33
zygaI wonder if those were super old and were always there (but nobody noticed the error or the error did not surface) or it this is something we recently broke15:34
mupBug #1759294 changed: Please display confinement level information in 'snap info' command output <Snappy:Invalid> <https://launchpad.net/bugs/1759294>15:37
pedronisniemeyer: this made me think something,  we should really call EnsureBefore after we have committed the transaction, which is outside this package15:40
cachiozyga, it is a big change the add -i interface in all the "snap interfaces"15:48
cachiozyga, is it ok if I do it in another PR15:48
cachioI also agree it is more robust15:48
cachiozyga, but I need to update 90 different places15:49
om26erwhen does snapd 2.31.2  leave -proposed on stable Ubuntu releases ?15:52
ackkmvo, zyga, hi, WRT 'nobody' user for snaps, was the idea we discussed at the sprint agreed upon?15:59
niemeyerpedronis: +116:01
zygacachio: Yes, lets do it in a new PR16:02
zygaAckk, I forgot what the agreement was, was it to ship a user with snapd or do something else?16:03
ackkzyga, yeah I think it was that snapd would create a "snaps-nobody" user that is used to remap the nobody user16:09
ackkzyga, (or whatever username is decided)16:09
ackkzyga, we really just need a non-root user16:09
zygaAckk remap how?16:11
zygaRemember16:11
zygaRemember that etc passwd is from the host today, right?16:12
pstolowskizyga: see my latest answer to the stray connections bug16:15
pstolowskiin the forum16:16
zygapstolowski: looking16:16
ackkzyga, doesn't snapd remap uids?16:17
zygaAckk, no we don’t do that16:18
zygapstolowski: is there anything we can add to snapd to fix people with broken state16:18
ackkzyga, ah I see. anyway, that doesn't really matter, I just seemed to remember you talked about user mapping16:19
ackkzyga, you guys, not you specifically :)16:19
zygaSorry, my memory is rusty. I need to review the notes from that week16:19
zygaYam16:20
pstolowskizyga: yes, I think we need to remove these stray connections in InterfaceManager::initialize16:20
pstolowskizyga: does that sound sensible?16:21
niemeyerOkay! Let's do some more reviews..16:21
zygaHmmm, I think so but what is a stray connection? One without one or the other snap?16:22
pstolowskizyga: yes16:23
pstolowskizyga: ok, I think i know why we didn't see that before16:30
pstolowskiadding one more comment16:30
zygapstolowski: I think there's a deeper bug in refresh code in interfaces16:30
cachiomborzecki, when you have some time coiuld you please take a look to #472116:30
mupPR #4721: tests: update interface tests to remove extra checks and normalize tests <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/4721>16:30
zygaoh16:31
* zyga waits for your new comment16:31
zygapstolowski: some code should not reach the state where it got ErrNoState16:31
zygapstolowski: probably our reconnect code is buggy tyhere16:31
* kalikiana wrapping up for the day16:34
pstolowskizyga: commented16:39
zygaright16:40
zygathanks, I'm looking forward to the PR16:40
pstolowskizyga: yep, working on it, besides fixing reloadConnection I'll also add this cleanup on startup, wdyt?16:40
zygapstolowski: skip the cleanup for now16:41
pstolowskizyga: ok16:41
zygapstolowski: let me think about that some more16:41
zygaor propose it separatel16:41
zygay16:41
pstolowskizyga: the cleanup could actually happen in reloadConnection, almost for free - Connect fails only if either plug or slot is missing16:45
zygalet's be conservative for now, this can be cherry picked into the release16:45
zygawe can always clean it up later16:45
pstolowskiok16:45
zygapedronis, niemeyer: can you please ack 494117:07
vidal72[m]I wrote a post in forum. This raises my eyebrows https://forum.snapcraft.io/t/bogus-apps-in-store/470317:17
niemeyer#494117:17
mupPR #4941: vendor: update gopkg.in/yaml.v2 to the latest version <Created by zyga> <https://github.com/snapcore/snapd/pull/4941>17:17
zygaThank you!17:17
niemeyerzyga: Tests pass, previously discussed in the meeting, and not much to review.. I've just merged17:19
zygathanks, I just wanted to ack this17:19
niemeyerzyga: Thanks for doing so17:19
mupPR snapd#4941 closed: vendor: update gopkg.in/yaml.v2 to the latest version <Created by zyga> <Merged by niemeyer> <https://github.com/snapcore/snapd/pull/4941>17:20
niemeyerpedronis: I'm getting to the end of #4900 btw17:20
mupPR #4900: many: use the new install/refresh API by switching snapstate to use store.InstallRefresh <Critical> <Created by pedronis> <https://github.com/snapcore/snapd/pull/4900>17:20
niemeyervidal72[m]: You got a response there17:20
naccniemeyer: well, for part of the post17:21
naccprobably the less important part, though :)17:21
zygahmmm, I get this on a clean tree17:23
zygahttps://www.irccloud.com/pastebin/WAMjnnmK/17:23
vidal72[m]so if I publish with invalid license it can stay this way forever? Nobody verify, nobody care?17:23
zygais my govendor foo not great or is there a real problem?17:23
niemeyernacc: Yes, there are about 10 questions on that post.. :) I've answered a few more of them17:24
mupPR snapd#4945 opened: vendor: update gopkg.in/yaml.v2 to the latest version <Created by zyga> <https://github.com/snapcore/snapd/pull/4945>17:24
naccniemeyer: heh17:24
niemeyervidal72[m]: Please ask any other questions there so we can have a single conversation17:25
niemeyernacc: Feel free to participate as well17:25
niemeyernacc: Assuming you have points other than "heh", of course17:25
naccniemeyer: sure17:26
vidal72[m]niemeyer: ok17:26
mupPR snapd#4946 opened: Ignore bad connections in reloadConnections, don't surface them outsi… <Created by stolowski> <https://github.com/snapcore/snapd/pull/4946>17:27
pstolowskizyga: ^17:27
pedronisniemeyer: fwiw, that one contains everything, it has prereqs17:29
niemeyerpstolowski: That PR title looks quite broken17:29
niemeyerpedronis: Too late :)17:30
pstolowskiniemeyer: ah, sorry, fixed17:30
niemeyerpedronis: For the best I suppose, in this case17:30
pedronisit's quite large (though more than half is tests)17:32
jdstrandroadmr: hi! not at all urgent, but can you pull in r1016 of CRT? (just another override)17:33
zygapstolowski: reviewed17:35
zygasmall change requested17:35
zygalet me know if you think this is okay or if it turns out bigger than small17:35
pedroniszyga: notice that reconnect on refresh doesn't exist in master,  it's a new thing in the interace hooks branch17:42
* cachio afk17:42
zygapedronis: hmmm, but we do reload connections on upgrade17:45
zygaotherwise people on beta would not hit this case, no?17:45
pedroniszyga: reloading connections,  and reconnect are two different things17:45
pedroniswe always been reloading connections17:45
pedronisafaik17:45
pstolowskizyga: Connect() can fail only if either: plug or slot is missing, or interfaces on them don't match. we need to ignore both these cases and not add to affectedSnaps. the error message that people reported will not be visible anymore, we will only log to the logger17:48
pstolowskizyga: changing error reporting in Connect will affect ifacestate and api tests, so not exactly a small change17:50
zygano, the error on interface mismatch is one thing17:51
zygabut when something is just *gone* that's the error we don't want to show17:51
niemeyerpedronis: Review is out17:51
pedronisniemeyer: thanks, this was the big one so you covered also the prereqs.  (4896, 4772 and 4771)17:58
pedronisniemeyer: #4873 is for delaying registration17:59
mupPR #4873: many: delay classic registration until first store interaction <Critical> <Squash-merge> <Created by pedronis> <https://github.com/snapcore/snapd/pull/4873>17:59
mborzeckiquit18:00
niemeyerpedronis: Looking18:00
pstolowskizyga: how about this: https://pastebin.ubuntu.com/p/YyrYQY8FBw/ ?18:19
niemeyerpedronis: Okay, I think I can grasp it18:19
niemeyerpedronis: Do you have some time for a short call?18:19
niemeyerpedronis: About the PR18:19
pedronisniemeyer: yes18:20
niemeyerpedronis: Okay, let's hop onto snappy-devel18:25
pedronisniemeyer: I'm there18:26
kyrofaniemeyer, do you have any time today to meet about architectures?18:49
pstolowskizyga: i've pushed the above change to the PR, eod18:51
=== pstolowski is now known as pstolowski|afk
roadmrjdstrand: sure, 1016 going in the queue \o/18:55
jdstrandthanks! :)18:55
niemeyerkyrofa: In a call for the last hour.. tomorrow might be easier if it works for you19:19
kyrofaniemeyer, sergiusens will be on vacation after today, but I can be there19:20
mupPR snapcraft#2036 closed: errors: remove stack data when sending to sentry <Created by sergiusens> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/2036>19:32
jdstrandstokachu: did you update lxd to work around the environment scrubbing issue (ie, the not being able to find liblxc.so.1)?19:32
jdstrandstokachu: nm19:32
jdstrandstgraber: hey, did you update lxd to work around the environment scrubbing issue (ie, the not being able to find liblxc.so.1)?19:33
jdstrandstgraber: I'm trying to reproduce. I thought all I needed was an upstream kernel with apparmor enabled, but maybe I am misremembering19:35
stgraberjdstrand: we might have accidentally worked around it19:46
stgraberjdstrand: let me check19:46
stgraberjdstrand: yeah, we did, we had to set LD_LIBRARY_PATH for zfs to be happy in some cases, so that's effectively masking the bug you're looking at19:46
stgraberjdstrand: "snap run --shell lxd" and then running "aa-exec -p unconfined" should let you reproduce it though19:47
jdstrandstgraber: that would explain it19:51
jdstrandI'm wondering how important this is to fix in snapd then19:52
jdstrandI filed the apparmomr bug so we'll get a fix eventually19:52
stgraberthat'd still break all classic snaps though wouldn't it?19:52
stgraberclassic snaps on distros with similarly lacking apparmor support that is19:53
stgraberas the same profile as LXD would be used and LD_LIBRARY_PATH would get stripped as a result19:53
stgraberwhether that'd break such a snap is another matter though, a lot of them may be fine not using any of the core snap's libs?19:54
jdstrandstgraber: classic snaps have all kinds of weirdness with their libs and don't set LD_LIBRARY_PATH19:54
jdstrandwe've also not seen any reports against them19:55
stgraberok, anyway, yes, for LXD this isn't a problem anymore because we always consider whatever snap-confine sets to be bad and override it ourselves in our wrappers19:57
jdstrandstgraber: so, what I was thinking was that I'd have a lxd-support specific fix in snapd while we wait for the kernel to be fixed19:57
jdstrandbut if you don't care any more...19:57
stgraberwe can probably wait for the kernel fix, we're only likely to run into this again if we add a new command and forget about it, which is somewhat likely but also a pretty quick workaround to put in place on our side once someone reports it19:59
jdstrandstgraber: I don't mind looking at an lxd-support fix for at least a little bit, but trying to find the correct aa-exec -p unconfined -- ??? invocation to demonstrate the issue20:01
stgraberI "think" the reproducer on Sergio's system was:20:02
stgrabersnap exec --shell lxd20:02
stgraber  export LD_LIBRARY_PATH=foo20:02
stgraber  aa-exec -p unconfined bash20:02
stgraber    echo ${LD_LIBRARY_PATH}20:02
stgraberwhich would then show up empty rather than containing "foo"20:02
jdstrandstgraber: sure, I know about that part (that is in the bug I filed and have all the reproducer's etc)20:03
jdstrandstgraber: but I'm looking for the liblxc issue specifically20:03
stgraberok, the liblxc issue is because prior to us always setting LD_LIBRARY_PATH ourselves, we'd rely on snap-confine doing that for us, so it looked like 1) user runs "lxd init" 2) calls snap-confine which sets LD_LIBRARY_PATH 3) The wrappers/commands/lxd is execed 4) Script re-execs itself through aa-exec -p unconfined loosing its LD_LIBRARY_PATH 5) Script exec bin/lxd which is linked against liblxc, causing20:05
stgraberloader error due to missing library20:05
jdstrandfyi, snap-confine doesn't do anything with LD_LIBRARY_PATH20:07
jdstrandalright, I'll keep playing with it20:07
stgraberoh, then whatever sets it :) the snap binary itself I guess?20:08
jdstrandit's a weird call stack, but it is snapenv.go that keep sit from getting stripped when going through setuid snap-confine20:09
jdstrandanyhoo, I'll look at this a bit, but may end up moving to something else20:09
jdstrandoh, I could install an affected revision20:11
jdstrandstgraber: was the change in lxd-pkg-snap.git or lxd.git?20:12
stgraberjdstrand: it was in lxd-pkg-snap, when we started including multiple zfs versions20:12
jdstranddb21175920:13
jdstrandok, cool20:13
stgraberjdstrand: http://paste.ubuntu.com/p/s4gMQvB9dx/20:13
stgraberjdstrand: applying that and then building the snap should give you a build that'll have the issue when running "lxd init"20:13
jdstrandright20:14
jdstrandcool, thanks!20:14
zygaHmmm20:22
zygaOn a phone20:22
zygaLd library path is reset because of at secure20:23
jdstrandstgraber: fyi, the 2.0 channel is still affected:20:23
jdstrand$ sudo /snap/bin/lxd init20:23
jdstrandlxd: error while loading shared libraries: liblxc.so.1: cannot open shared object file: No such file or directory20:23
zygaBut we have a system where certain variables are saved and restored as Snappy prefix $varname20:23
jdstrandzyga: that isn't the issue20:23
zygaOh sorry just noticed notification from my phone20:24
stgraberjdstrand: oh, that'd make sense since we haven't done the multi-zfs version trick there yet20:24
stgraberjdstrand: well, that makes it easier to test :)20:24
jdstrandzyga: it is related to at secure of course, but the bug is this: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/175934620:24
mupBug #1759346: ix scrubs environment when it shouldn't <aa-kernel> <apparmor (Ubuntu):New> <https://launchpad.net/bugs/1759346>20:24
jdstrandstgraber: indeed20:25
zygaLooking20:25
jdstrandstgraber: it also means you can workaround it easy enough in the 2.0 packaging20:25
zygaI see20:26
zygaStill we have a system where snap run and snap exec cooperate and can save restore environment20:26
stgraberjdstrand: yeah, got to update a whole bunch of stuff in 2.0, haven't done too much of it given our tiny snap user base for it vs deb20:26
* jdstrand nods20:27
jdstrandzyga: yep20:29
Caelumzyga: I updated my two PRs, will look at package issues later tonight20:31
zygaThank you!20:32
Caelumzyga: I don't know why you saw snap-repair, because I definitely remove those, you may have been looking at an older revision20:32
zygaOh20:33
zygaPerhaps, I will check out and see tomorrow20:33
zygaDid you get Spotify to open browser links20:33
Caelumno let me try that20:33
zygaThat requires the service files20:34
Caelumyeah it doesn't work20:36
Caelumfirefox opened a second spotify and didn't open the track20:37
jdstrandzyga: note that the issue happens after the snap run/snap env business. ie, LD_LIBRARY_PATH is preserved. The act of running aa-exec, which has ix, strips LD_LIBRARY_PATH such that the thing it execs doesn't see it20:40
zygaI see jdstrand20:41
jdstrandzyga: also, this is *only* partial apparmor support which gets the '/** pix,' rule20:41
jdstrandwhich applies to aa-exec20:41
jdstrandanyway. thinking through how to fix it. I have ideas20:41
zygaDo we need a user space workaround20:41
jdstrandI'm thinking about a snapd change to partial policy20:42
zygaOk20:42
jdstrandreally, we need the kernel fixed, and it will be20:42
jdstrandit is possibly a documentation change only20:44
mupPR snapcraft#2039 opened: Release changelog for 2.40.1 <Created by sergiusens> <https://github.com/snapcore/snapcraft/pull/2039>21:12
mupPR snapd#4945 closed: vendor: update gopkg.in/yaml.v2 to the latest version <Created by zyga> <Merged by zyga> <https://github.com/snapcore/snapd/pull/4945>21:13
nacckyrofa: sigh, sergiusens mentioned they had used the git-ubuntu.self-test, but it looks like maybe it's busted again -- (our CI flagged it, it passed on one run that was using 2.39.3+really2.35 (https://jenkins.ubuntu.com/server/job/git-ubuntu-ci/345/consoleFull) and failed one that used 2.40 (https://jenkins.ubuntu.com/server/job/git-ubuntu-ci/349/consoleFull). The former branch had the latter as an23:22
naccancestor, so it implies not a ocding error (and neither touches the gpgv paths)23:22
nacckyrofa: hrm, now i had a job succeed with 2.4023:51
nacc... that's not great either23:51

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