/srv/irclogs.ubuntu.com/2018/07/17/#snappy.txt

=== pbek_ is now known as pbek
=== pstolowski|afk is now known as pstolowski
mvopstolowski: good morning :)07:18
pedronismvo: hi, I'm going to merge #5502 today07:23
mupPR #5502: many: streamline the generic conflict check mechanisms <Created by pedronis> <https://github.com/snapcore/snapd/pull/5502>07:23
mvopedronis: ok, I look at it now07:28
mvopstolowski: interessting fix in the osutil/udev PR - is this a signed/unsigned issue?07:50
mvos/is/was/07:50
pstolowskimvo: yes07:50
pedronismvo: thx07:51
mvopstolowski: interessting07:51
pstolowskimvo: it wouln't happen if my tests didn't use 0xff's to simulate invalid offset07:51
mvopedronis: thank you, nice improvement, also nice to see how much cleaner it got07:52
mvopstolowski: a, sweet07:52
mvopstolowski: I was wondering how you get such a big offset that its a problem on 32bit07:52
mvopstolowski: nice to know there was a test for it!07:52
pstolowskimvo: i'm not quite sure why it didn't panic on 64bits though.07:52
pstolowskimvo: but i added debug and it clearly showed negative number there07:53
mvopstolowski: I assume its because on 64bit 0xff000000 will not wrap to a neagative number (space in the 64 bit int left). but I have not really looked at the details so I might be wrong07:54
mvoChipaca: good morning07:56
pstolowskimvo: i think you're right. re your earlier question, the test parses crafted garbage data07:56
Chipacamvo: it is! how're you today?07:56
mvofun! the degraded test found that we have a sshgurad.service that is broken in our test images07:56
mvopstolowski: tests ftw! nice job07:56
mvoChipaca: I'm well, thank you! having fun reading code and poking at our boot stuff07:57
pstolowskii made a quickfix in the PR and also proposed it upstream07:57
mvoChipaca: hope you are well too?07:57
mvopstolowski: ta07:57
Chipacatests ftw indeed07:58
mvoChipaca: I'm also loosing hair over the question *why* the snap-run-hook test fails on core1807:58
Chipacamvo: yep! looking forward to the day07:58
Chipacamvo: SCSI Chain overterminated07:58
mvoChipaca: *cough* those were the days07:58
* Chipaca thinks the bofh excuse database needs updating07:59
pstolowskinb, it's interesting Go chose to return int from len()07:59
Chipacapstolowski: uint is a second-class citizen07:59
mvopstolowski: fun, there is even a stack-overflow question about why go is doing that (and the answer even makes some sense)08:00
pstolowskimvo: do you have a link?08:09
mvopstolowski: https://stackoverflow.com/questions/39088945/why-does-len-returned-a-signed-value08:10
pstolowskimvo: thanks, interesting explanations08:12
Chipacapedronis: with 5502 landed, should I work on snapshotstate, or should i wait for a followup?08:14
Chipacapedronis: and what about #547408:14
mupPR #5474: many: finish sharing a single TaskRunner with all the the managers <Created by pedronis> <https://github.com/snapcore/snapd/pull/5474>08:14
pstolowskihmm interesting failure of google:ubuntu-16.04-64:tests/main/interfaces-accounts-service08:18
pstolowskihttps://www.irccloud.com/pastebin/XyMk8wi7/08:18
Chipacaquoth the raven, WAT08:19
mvomeh, I get quota CPUS exceeded08:37
mvoin my latest PR08:37
Chipacamvo: have we alerted people about the sshguard service thing?08:50
mvoChipaca: not yet, might be related to our image08:51
mvoChipaca: I mean to our version of the cloud-image08:51
Chipacamvo: ah, i thought we were using stock08:51
mvoChipaca: I'm not sure, I wanted to check with cachio08:51
mvoChipaca: its slightly strange because sshguard is universe08:51
Chipacaah08:52
popeyhttps://forum.snapcraft.io/t/snap-refresh-fails-no-such-file-or-directory/641308:58
popeyIf someone has a moment to look at that I'd appreciate it08:58
Chipacapopey: https://i.imgur.com/iJoG4Ks.jpg09:02
popeyIKR09:02
popey(I have seen this before, but only now have captured it)09:02
ogra_must be all these airplanes interfering with the cosmic rays at your place09:04
Chipacapopey: the most WAT bit is that after the Error, r319 is active09:04
popeyfun, right?09:04
Chipacai.e the one it just said didn't exist09:04
Chipacawaiiit09:04
popeythis isn't even a manky machine that's been running forever with all kinds of crap on it09:04
Chipacafeck09:05
popeyit's a vm I woke up to test something unrelated09:05
ChipacaI mean, <curses>09:05
Chipacait looks like we're adding the prerequisite N times09:05
Chipacathat can't be good09:05
popeyso this is a snapd bug? :)09:09
Chipaca3 times09:09
Chipacayes09:09
popey\o/09:10
popeyI mean, oh dear.09:10
popeyThanks for looking at it.09:10
Chipacapopey: where's my emoji for person-blowing-a-raspberry09:10
popeycolon thorn09:10
popey09:10
Chipaca>:þ then09:11
Chipacaaka the angry lisping viking09:11
popeyshall I file a bug in snapd?09:11
Chipacapopey: let me dig a little bit more first please09:11
popeyokeydokey09:11
Chipacamy first dumb test of printing the name of the prerequisite when we decide to install it (after checking it wasn't due to be installed) shows that we're installing things that are already due to be installed09:12
Chipacaooooh09:12
Chipacathis is probably because that snap is the default provider for a bunch of stuff09:12
Chipacainnit?09:12
popey¯\_(ツ)_/¯09:13
* Chipaca talks to itself09:15
Chipacapopey: yep, just repro'd it, on  install09:18
popeyyay09:19
Chipacastill digging further09:19
Chipaca(there is a race, which is why you're not seeing it all the time)09:19
Chipacaso, yeah09:21
Chipacawe r dumb09:21
Chipacapopey: I'll work on a fix, but feel free to file a bug09:22
popeykk09:22
popeythanks09:22
Chipacapopey: interestingly the refresh succeeded, also09:35
ChipacaI mean, the change failed, but everything installed09:35
popeyyeah, when I have seen this in the past, I run "snap refresh" and it says it has nothing to do09:35
Chipacayep09:36
popeyalso also, in other news "snap refresh" and "snap install" now take a phenomenally long time to actually do anything09:36
popeyI feel like I'm staring at a broken computer when i run snap refresh or install these days09:36
Chipaca:-(09:36
Chipacapopey: I know, they used to be so zippy! :-(09:36
Chipacainterfaces code is _slow_09:36
popey14 seconds to do nothing09:37
popeyi just refreshed then tried to refresh again, 14 seconds for the second run09:37
Chipacapopey: wait, it takes that long to say 'nothing to do'?09:37
popeyyes09:37
Chipacathat's not what I thought you meant09:37
Chipacalet me try09:37
pedronisChipaca: I will merge trunk in the follow ups, they will need review but you can start working on snapshot, you basically need to use AddAffectedSnapsByAttr09:37
popeyhttps://www.irccloud.com/pastebin/JadUttj8/09:37
Chipacapedronis: and drop the old kludgy conflicts stuff09:37
pedronisyes09:38
popeywtf is it doing for 14 seconds?09:38
Chipacapopey: snap list | wc -l09:38
pedronisChipaca: I alos need to update the wiki, there's quite a few kinds not mentioned there09:38
Chipacapopey: plz09:38
Chipacapedronis: :-( thanks :-)09:38
popey20509:38
Chipacado you have SNAPD_DEBUG enabled?09:39
popeygod i hope not09:39
popeyhow can I tell?09:39
Chipacapopey: nah it shouldn't slow things down, just log more09:39
Chipacapopey: (and we've asked canonicalers to have it enabled (and SNAPD_DEBUG_HTTP=3 at least iirc) so we can figure out one-off errors from the logs)09:40
Chipacapopey: “journalctl -u snapd” would have a lot of DEBUG lines09:40
popeydefine " a lot" :)09:40
Chipacapopey: more than 009:40
popeyi haz 009:40
Chipacaso, not a lot09:41
Chipaca:-)09:41
popeywant another bug?09:41
popeynews to me btw that you've asked canonicalers to have debug enabled09:41
Chipacapopey: if you can (even momentarily) turn on debug, we can see where the bug is09:41
popeyok09:41
Chipacapopey: I can forward you the email :-)09:41
Chipacapopey: subject «suggestion to work with debug enabled in snapd», from a year ago09:42
popeyunread :)09:43
* Chipaca goes to the shed to get a 2x409:43
popeyI have enabled this before (to debug store slow download issues) and having debug switched on made the error go away09:44
popeyI am reluctant to enable these things as it makes my system behave differently than the people I talk to every day09:44
popeynormals don't enable this, and neither to devs09:44
Chipacapopey: the _only_ thing setting these debug flags does, afaik, is change the logging options09:44
popeylies :)09:44
Chipacapopey: but I see your point09:44
pedroniswell, but turning it off and on is worse09:45
pedronisit involves a restart09:45
pedroniswhich is sure to change things09:45
popeyhttps://forum.snapcraft.io/t/extremely-slow-snap-downloads/4668/7?u=popey09:45
pedronisgiven how snapd works09:45
Chipacapopey: snap downloads should be much faster since we switched to fastly09:45
Chipacapopey: but, snap refresh != snap downloads09:46
popeyi have seen user reports of slow downloads09:46
Chipacapopey: 14 seconds for snap refresh, with 200 snaps, is rather unique which is why i'd like to see logs of it to know who's being slow09:46
popeyhttps://askubuntu.com/questions/1056606/from-what-url-snaps-are-downloaded09:46
popeyfor example09:46
popeyI am frustrated though, because the general response seems to be "ah well, can't do anything without debug data"09:46
pedronisChipaca: a review of #5515 would be appreciated09:46
mupPR #5515: daemon: make sure most change generating handlers can produce errors with kinds <Created by pedronis> <https://github.com/snapcore/snapd/pull/5515>09:46
popeyright, just enabled debug, now snap refresh is instant09:47
Chipacapopey: ok09:47
Chipacapopey: keep it enabled for a while and tell us if it gets slow09:47
popeywill do, thanks09:47
Chipacapopey: pretty please09:47
Chipacapopey: (this would be bad news, or good news, because it'd indicate a bug in a part of snapd we're itching to change)09:48
pedronisChipaca: ?   is this a do nothing refresh09:48
Chipacapedronis: yes09:48
pedronisChipaca: do we have plans to change that?09:48
Chipacapedronis: see his pastebin09:48
pedronisdon't think so09:48
Chipacapedronis: if it's snapd getting slow after a while because state in-memory means walking whatever bit of state takes 14+ seconds, then yes it's  us09:49
popeyhahaha, its gone slow again already :D09:49
Chipacapopey: e-e-excellent. gib logs.09:49
popeywhich logs, how?09:49
Chipacapopey: journalctl -u snapd09:49
Chipacapopey: from the latest 'started snapd' line09:50
popeyhttp://paste.ubuntu.com/p/syNYjKjB64/09:50
popeyoh, too late, that's all of it09:50
Chipacapopey: that's not debug logs09:50
popey:(09:50
popeyI typed what you asked09:50
popeymaybe snapd didnt restart09:50
* popey tries again09:51
popeymy bad, line 4709 onwards http://paste.ubuntu.com/p/xKMMN3fSdg/09:52
Chipacapopey: if « journalctl -u snapd | grep DEBUG: » is empty, it didn't work09:52
Chipacaah09:52
Chipacanow yes :-D09:52
popeyhaha, is that 200 stabs of the store api ? :)09:52
Chipacaoh09:52
Chipacafor the asserts refresh09:53
pedronisassertions, it's  1 or 2 api calls per snap09:53
pedroniswe have plans to improve09:53
pedronisthat but not immediate plans09:53
Chipacathe snaps refresh api call itself is super fast: 10:51:29.410762 to 10:51:30.37717509:54
popeygold star for you :)09:54
Chipacabah, 'super fast', less than a second09:54
pedronis:)09:54
popeydirty brown star for the store :)09:54
Chipacait's python, less than a second is it doing its best09:54
mvoas a quick fix, could we do the assertion update only for non-interactive refreshes or something09:54
* Chipaca suddenly finds himself to be evil09:55
pedronisno09:55
pedroniswe can't09:55
pedronisbecause validation09:55
mvoindeed09:55
Chipacapopey: could you file a bug, on snapd *and* snapstore, that having 200 snaps means refreshes take way too long09:55
popeysure thing!09:55
popey on it09:55
Chipacapopey: include these logs (from the last bit on), and the 'time' log09:55
popeyThanks for spending time to help me debug09:55
popeywill do09:55
Chipacataw09:55
Chipacapedronis: dunno if you saw that we add prereqs twice and that breaks things09:56
pedronisChipaca: no09:56
pedronisChipaca: that's mvo actually :)09:56
Chipacapedronis: true, that09:56
Chipacamvo: it's all your fault!09:56
mvoChipaca: meh09:56
Chipacamvo: *all* of it09:56
pedronismaybe09:57
Chipacamvo: even brexit09:57
* mvo crumbles in depair09:57
Chipacai'm telling the bbc09:57
pedronisit depends exactly how it fails09:57
mvoChipaca: do you have a reproducer09:57
Chipacamvo: it's racy, but yes: snap install gnome-system-monitor gnome-calculator09:57
Chipacamvo: if it fails to repro, clean up with: snap remove gnome-system-monitor gnome-calculator gnome-3-26-1604 gtk-common-themes09:57
pedronistheoretically there's only one prereq running at a time09:58
Chipacabasically a snap can have another snap more than once in its prereqs09:58
Chipacaand we don't check for that09:58
pedronisChipaca: a snap, or a pair of snaps?09:58
pedronisah, a snap09:59
Chipacapedronis: just one should be enough09:59
Chipacain fact it shold repro with just one09:59
mvoChipaca: ok, once I finished wrestling with the snap-run-hook failure on core18 I'm on this one09:59
Chipacamvo: already fixing it here09:59
pedronisChipaca: mvo: it's because   they added themes to the gnome lib snap itself09:59
mvoChipaca: \o/ even better09:59
pedronisso now some snaps get to it through the snap and through gnome09:59
pedronisso we have a snap that is a default provider both for a snap and a default provider of that snap10:00
pedronisfun10:00
pedronisshould also be easy to solve10:00
popeyhttps://bugs.launchpad.net/snapstore/+bug/1782112 tada10:00
mupBug #1782112: snap refreh is slow with lots of snaps installed <snapd:New> <Snap Store:New> <https://launchpad.net/bugs/1782112>10:00
Chipacapedronis: wondering whether to solve it at install time, or at work-out-prereqs time10:01
Chipacapedronis: the latter seems saner, the former more foolproof10:01
pedronisChipaca: mmh10:02
pedronisChipaca: in theory it should work already, but the theory is fragile10:02
pedronisapparently10:02
popeyI'm surprised we don't send a blob of data to the store with the list of everything we want rather than 200 separate requests.10:02
popeyseems terribly inefficient10:02
pedronispopey: that is the question10:03
popeyAh okay. Ignore me :)10:03
pedronispopey: everybody has a different list so caching would be defeated10:03
pedronisit needs bit more cleverness, some compromise10:03
mvopedronis: if you could have a look at 5491 again today that would be greatly appreciated10:06
pedronisChipaca: I mean in theory when we install  gnome itself  we should detect that the themes are already being installed, that doesn't seem to work though10:06
popeyI appreciate I'm a bit of an outlier with 200 snaps installed :)10:06
popeyblazing a trail10:06
Chipacapedronis: because we create the task list and only add it to state if the whole thing worked10:06
* mvo hugs pop'trailblazer'ey10:06
pedronisChipaca: yes, but we atomically do that for each snap10:06
pedronisor at least that's the intention10:06
pedronisneeds bit of digging10:07
pedronisChipaca: anyway in one of the plans we would do all of this upfront10:07
Chipacapedronis: I can show you where we're not checking for dupes, if you  want10:08
Chipacamaybe I should check for dupes at both places, for extra extraness10:08
pedronisChipaca: but the dupes are indirect10:08
pedronisin this case no?10:08
pedronisso I'm not sure how there can be a place10:08
pedronis(afair current code)10:09
Chipacapedronis: snapstate's defaultContentPlugProviders already gets the duplicated names10:09
pedronis?10:09
pedronisfrom which snap10:09
pedronisso it's silly bug?  not a deep bug?10:09
ChipacaI forget but give me a moment to undo my fix and di can tell you10:09
Chipacapedronis: it seems to be, yes10:10
pedronisok10:10
pedronisI see we were assuming that a snap will not repeat the default provider10:10
pedronisbut they do10:10
mvo*cough* thats a silly bug indeed. thanks pedronis  and Chipaca10:10
Chipacapedronis: for gnome-system-monitor, defaultContentPlugProviders returns: gtk-common-themes, gtk-common-themes, gtk-common-themes, gnome-3-26-160410:12
pedroniswonderful10:12
pedronisseems 2.34  material even10:12
Chipacapedronis: for gnome-calculator, gtk-common-themes, gtk-common-themes, gnome-3-26-1604, gtk-common-themes10:12
pedronisif that is still possible10:12
Chipacait's surprising that it works some of the time :-)10:12
ChipacaI'll fix defaultContentPlugProviders to not return dupes, and leave the slightly hairy code in handlers alone10:13
mvopedronis: yes, looks like we need a .1 anyway10:13
Chipacait'll fix this issue and not make things harder for us10:13
pedronisChipaca: thx10:14
* Chipaca looks for the unit tests of defautContentPlugProviders, and fails10:14
ogra_jdstrand, i'd appreciate a manual apoproval at https://dashboard.snapcraft.io/snaps/xdmcp-client/revisions/1/  (uses the new mir-kiosk snap with a loopback x11 plug for Xwayland, source is at https://github.com/ogra1/xdmcp-client/ )10:20
popeyoooh10:20
ogra_i plan to extend that with a few other clients and turn it into a thin-client appliance ;) (vnc, rdp ... )10:21
popeygreat idea.10:21
popeyI had no success getting an app working with mir-kiosk, so will look at yours for inspiration10:22
ogra_it sadly needs layouts to make Xephyr happy (hardcodes paths to binaries in the code) ... for normal apps it shoudl be a lot easier though10:23
pstolowskii keep getting  cannot allocate new Google server for ubuntu-18.04-64: quota 'CPUS' exceeded. Limit: 600.0 in region us-east1 from travis10:26
mvopstolowski: I saw this as well and asked zyga to ask Gustavo about it. Hopefully he or cachio can help10:28
pstolowskimvo: ack, thanks10:28
ppisatiogra_: i'm debugging the snapcraft.yaml build issue for xenial and bionic, feel free to drop it if you have anything else10:30
ogra_ppisati, https://forum.snapcraft.io/t/linux-4-15-0-snaps/6401/510:31
ogra_ppisati, and there seems to be an issue with "no such target "firmware_install" at the end of the build10:32
ppisatiogra_: yep, i have patch similar to that10:32
ogra_right, then only the missing firmware_install target is left ....10:33
ppisatiogra_: 3794440b47ceada080b365e281b76313c7a2e25510:33
ogra_grepping the whole tree the only mention of firmware_instakk is in debian/scripts which i thought wouldnt be run ...10:33
ogra_*firmware_install10:33
boxrickHello, I added some values to the environment of my machine ( proxy ) and need the snapd service to reload those, is this possible without a full restart of the service?10:43
boxrickAnd second if I wish to pin a package version, is that doable?10:43
boxrickIE disable auto refresh10:43
Chipacaboxrick: there are several knobs you can use to change when a refresh happens, but you can't disable it from the device, no10:46
Chipacamvo, pedronis, #5522 is the fix10:46
mupPR #5522: overlord/snapstate: dedupe default content providers <Created by chipaca> <https://github.com/snapcore/snapd/pull/5522>10:46
Chipacafeel free to tag it and target it appropriately10:46
Chipacaboxrick: what're you wanting to stop refreshing, and why?10:47
boxrickSince if and when it breaks, I want it to be in a controlled fashion. Or perhaps a checked upgrade in my dev environment before I roll it out in the real world.10:49
boxrickSimilar reasons I pin to software versions in config management10:50
boxrickIf I have a working environment, I need that to remain consistent.10:50
Chipacaboxrick: as far as I know you get that level of control when you use a branded store10:52
Chipacaboxrick: if this is for a device, you can also do revision pinning (but i'm not sure that isn't also tied to a branded store)10:53
ogra_i think it is10:53
ogra_(you actually pin it in the store ... )10:54
Chipacaogra_: k10:54
ogra_(AFAIK at least ... :) )10:54
Chipacaboxrick: depending on the snap, in some cases it'll be appropriate to let production track stable and have a canary tracking candidate10:55
boxrickAny of example of how I can pin a version?10:55
Chipacaor I could just be talking to a wall10:56
* Chipaca wanders off10:56
boxrickPerhaps I have missed your point I apologise.10:58
boxrickWell kind of unrelated, reloading enviroment. Any tips without a full snapdrestart?10:59
boxrickOr some way of printing out the current environment that it has loaded up.11:02
ogra_boxrick, i'd just try "systemctl reload snapd" ... technically that should reload the units config, parctically no idea if snapd picks it up though11:05
ogra_*practically11:05
boxrickSadly not, seems I will have to poke the systemd service to find the PID then check the environment of that PID11:11
Chipacaboxrick: how did you set the environment?11:12
boxrickJust setting /etc/environment11:12
boxrick( Proxy settings in this case )11:13
boxrickWhich I then need snapd to read11:13
boxrickAnd just restarting it every time is super ugly.11:13
Chipacaboxrick: 'every time'?11:13
Chipacaboxrick: (not sure why it's super ugly, but you can't change the environment of another process; not easily at least)11:14
boxrickWell for example, I am deploying this with config management11:14
boxrickSo as part of a task it needs to make sure the environment is installed and snapd is running with it for example11:15
ogra_well, systemctl reload should send a kill -HUP to the daemon ... and i would expect it to also process the .service file ... if snapd respects the -HUP it should then pick up the new env11:15
boxrickReload just bombs out with unsupported which is ashame11:16
boxrickNot to worry anyway, I have a workaround. Its just a little long winded11:16
Chipacaogra_: systemctl reload does not work like that11:16
ogra_oh ?11:16
niemeyerHeya11:17
niemeyermvo: Any good hints about why the systems were hanging?11:17
Chipacaogra_: systemctl reload needs the service to have an ExecReload line11:17
niemeyerI'm gcing just now11:17
ogra_ah11:17
ogra_so it isnt sysv-init ... who'd have thought that ! :)11:17
Chipacaogra_: and, on the other hand, sending a HUP does not cause an environment re-read :-)11:17
ogra_depends on the daemon ... i have seen some do it11:18
r3r57Hello, after I restart my computer I regularly get the following error when running some snap applications: 'cannot change profile for the next exec call: No such file or directory \n snap-update-ns failed with code 1: No such file or directory'. I don't know whether it's a distribution specific issue or not and I'm not able to fix it myself. Does anyone have a clue what might be the problem here? Thank you in advance.11:27
popeyr3r57: what's the output of "snap version" please?11:28
r3r57popey, 'snap    2.32.9 snapd   2.32.9 series  16 solus   3.9999 kernel  4.17.3-81.current'11:28
popeyahh, i think zyga mentioned this problem recently. I believe there is a workaround.11:29
Son_Gokuniemeyer, zyga, mvo: woohoo! https://pagure.io/flock/issue/8711:29
Son_Gokunote the tag on the right ;)11:29
popeyyay11:29
zygaHey r3r5711:30
zygaThere is a workaround but ikey needs to fix solid11:31
zygaSolus11:31
zygaHey Son_Goku11:31
Son_Gokuzyga, I just sent the confirmation email to bexelbie for our talk11:31
zygaThat looks very good11:32
r3r57zyga, okay thank you, did you mind tell me the workaround or should I ask in #solus?11:33
Son_Gokuthis is good news to wake up to after having to stay up late last night for an OpenStack server migration last night :)11:33
zygar3r57: no, Just harder to type from my phone11:35
zygaDo this please11:35
zygasudo apparmor_parser -r /var/lib/snapd/apparmor/profiles/*11:36
r3r57magic11:37
r3r57zyga, popey, thanks for your help, everything is working again.11:38
r3r57and good luck with your talk ;)11:38
popeyExcellent, thanks zyga11:38
pedronisChipaca: I updated the wiki  https://github.com/snapcore/snapd/wiki/REST-API/_compare/2b0fc8772a1ac9cb57585f32e24ebd9a169fe940...acf58ecbbb071c4be741431ac648f9c5f0b63202 if you could double check11:38
pstolowskimvo: hey, a question to https://github.com/snapcore/snapd/pull/545611:47
mupPR #5456: snapstate: refuse to remove bases or core if snaps need them <Created by mvo5> <https://github.com/snapcore/snapd/pull/5456>11:47
=== pstolowski is now known as pstolowski|lunch
zygamvo: there?11:57
zygamvo: please fetch my remote11:57
zygamvo: and see if 47665f978a1d94ed44b3943a1d33f0e39be96459 makes any difference11:57
kenvandinecan anyone help me understand why /proc/mounts is significantly different from inside a snap that from the host?12:22
kenvandine /dev/loop30 /snap/spotify/13 squashfs ro,nodev,relatime 0 012:22
kenvandineon the host12:22
kenvandineand12:22
Chipacakenvandine: because snaps have their own private mount namespace12:22
kenvandine /dev/loop30 /var/lib/snapd/hostfs/snap/spotify/13 squashfs ro,nodev,relatime 0 012:22
kenvandinein the snap12:22
kenvandinewe're trying to figure out how to filter out the noise in the gnome-system-monitor snap12:23
kenvandineandyrock, ^^12:23
Chipacaah. Maybe zyga has insight into that.12:24
andyrockI guess what happens to all the udev (and afterall udev-udisks2 rules)12:25
ogra_i thought that was long fixed12:28
ogra_oh ... "in the snap" ... sorry, missed that12:29
kenvandineogra_, yeah... looks terrible in the gnome-system-monitor snap, which is seeded12:30
kenvandineogra_, andyrock had patched libgtop2 to filter it out, but it filters based on what the host sees not the snap12:31
ogra_right ... but that was fixed through a udev rule ... which likely doesnt apply from inside the sanp12:31
ogra_yep, i remember discussiong it with him back then12:31
ogra_did you try to ship said libgtop version in your snap ?12:32
kenvandineyes12:32
ogra_dang12:32
kenvandinebut it filters with a mnt of /snap12:32
kenvandinethere are other things showing up inside the snap as well, that don't on the host12:32
kenvandinelike /etc/alternatives12:32
kenvandineand others12:33
ogra_well, so filter with the hostfs prefix too12:33
ogra_/var/lib/snapd/hostfs/snap is effectively /snap12:33
kenvandineyeah12:33
kenvandinebut that would still leave noise12:33
ogra_so you could just extend the filter12:33
kenvandine /dev/loop55 /var/lib/urandom squashfs ro,nodev,relatime 0 012:34
kenvandinefor example12:34
kenvandinethe mount points are all over the place12:34
kenvandinemaybe we should ignore all loop12:34
kenvandinenot sure those are useful for gnome-system-monitor12:34
ogra_but that would break something like mounted isos12:34
ogra_(in case you want to allow people seeing them)12:34
pedronispstolowski|lunch: I merged the conflict streamling branch, as expected there are conflicts with disconnect-hooks12:35
kenvandinenot sure those are interesting12:35
ogra_probably a combo of loop and squashfs12:35
kenvandineandyrock, what do you think?12:35
andyrockkenvandine: I say that to filter snaps we need to extend the filter12:37
andyrocklet me check for the others12:37
ogra_it will get really bad if you start having layouts too ...12:37
kenvandinemaybe we can filter all squashfs12:38
andyrockkenvandine: btw the proposed upstream fix it this: https://gitlab.gnome.org/GNOME/libgtop/merge_requests/212:38
kenvandinethe real use case for gnome-system-monitor is to see how much snap you have left12:39
kenvandines/snap/space :)12:39
=== pstolowski|lunch is now known as pstolowski
pstolowskipedronis: right. thanks12:39
zygakenvandine: because a snap runs with pivot root and many things in the mount namespace are different12:44
zygaYou will also find that the x- mount options are stored in a file in user space12:45
ogra_i'm not so sure "nodev" is  good filter ... tht just tells that char and block devices *inside* the filesystem should be ignored12:45
zygaAnd that file is off when looked at from inside a snap12:45
ogra_you will also have it by default on nfs mounts or samba shares ..12:45
zygaSo libmount will not return those flags12:45
ogra_(and i think udisks also sets it by default for everything it automounts under /media ... )12:46
Chipacapedronis: https://pastebin.ubuntu.com/p/YfPFpgQdDw/12:46
Chipacaor maybe mvo12:46
Chipacadunno12:46
Chipaca:-) just rfc as to whether that is too informal12:46
Chipacaand, i need to go get the boys12:47
Chipacattfn12:47
ogra_tma !12:47
ogra_(too many acronyms)12:48
kenvandine:)12:48
mvoChipaca: nice12:49
mvoChipaca: ttfn12:49
mvozyga: running12:50
zygathanks12:50
mvozyga: running your python code12:50
zyganote that the patch includes support for sd_notify use inside the service12:51
zygabut it should be fully optional12:51
mvozyga: ok12:51
andyrockzyga: is /proc/filesystems visible inside a snap?12:54
zygayes12:54
zygathough confinement may block it12:54
zygaso it's there (/proc, /sys and /dev are)12:54
zygabut apparmor and device cgroups prevents access to arbitrary parts of it12:55
threshso uh12:55
threshhow do I go about moving the publisher rights for the snap to a different account?12:55
threshas opposed to granting another account publisher rights12:56
threshwe (VLC) originally used our supreme leader's account to publish it, and then he granted me publish rights12:56
timothyhi, I have a problem to generate any snap:12:57
timothyErr http://security.ubuntu.com/ubuntu bionic-security/main DEP-11 64x64 Icons12:57
ogra_thresh, i think you need to file a post under the store category in the forum12:57
timothy  Hash Sum mismatch12:57
ogra_thresh, there should be a documented way (also in the forum)12:57
threshthanks ogra_12:58
ogra_thresh, and while i have you here ... would it be possible to have an armhf build of vlc (i'm recently working on kiosk images for arm boards and having a vlc snap would be really helpful)12:58
threshwe don't have hardware for that12:59
ogra_well, i'd be fine with just having it switched on in build.snapcraft.io ... or do you use your own buuld infra ?13:00
threshyes, we build the snaps on our infra13:00
ogra_ah, k13:00
popeyor launchpad could mirror it13:00
popeyand build _only_ the armhf build13:00
ogra_yeah13:00
threshalso I've just checked and kde neon repos (which we use to get newer Qt) dont have armv7/aarch64 packages13:01
ogra_ah, ouch13:01
mvocachio: welcome back!13:01
thresh*maybe* when we switch to 1804 core...13:01
zygacore1813:02
zygacachio: hey :)13:02
threshright13:05
threshI would very much like not to depend on anything external to ubuntu repos, but that's impossible at the moment13:05
Chipacamvo: 5522 merged, was a single commit13:20
Chipacaogra_: dunno if your tma was on purpose or not, but TTFN started at ITMA :-)13:26
andyrockzyga: would be possible to get /run/mount/utab visible inside a snap?13:27
andyrockin this way we could mount all the squashfs with a x- user option13:28
andyrockand the snap can read /run/mount/utab in order to filter out some squashfs13:28
mvoChipaca: thanks, I will cherry-pick it13:31
mvoChipaca: cherry-picked and pushed, thanks again13:32
zygaandyrock: yes but note that it would be not showing the content you expect13:32
zygaandyrock: we can meet and discuss this but it's not a trivial problem13:33
zygalet me show you some notes13:33
zygahttps://forum.snapcraft.io/t/namespace-awareness-of-run-mount-utab-and-libmount/5987/513:33
=== abeato_ is now known as abeato
cachiomvo, these are some results for 2.34 https://paste.ubuntu.com/p/Rmxw9t2NF6/13:44
zygamvo: hey, can you add to 2.34.1 a patch that fixes CUDA13:47
zygaah, please ignore me, they are out13:48
mvocachio: looking, thank you13:53
cachiomvo, oood, I am checking 32 bits right now13:53
andyrockzyga: regarding the private utab file proposed here https://forum.snapcraft.io/t/namespace-awareness-of-run-mount-utab-and-libmount/5987/5, would it show all the squashfs e.g.  (/etc/ssl, /var/lib/sudo, etc.) ?14:10
zygaandyrock: we really don't know14:11
zygaI'd rather not do that14:11
zygabecause we have no sane way of keeping that file correct now14:11
pstolowskihttps://github.com/snapcore/snapd/pull/5433 needs 2nd review and is simple14:30
mupPR #5433: interfaces/repo: added AllHotplugInterfaces helper <Simple> <Created by stolowski> <https://github.com/snapcore/snapd/pull/5433>14:30
zygapedronis: thank you for the review of the remapper15:39
zygaI will address the comments15:39
zygaI'm super excited to see this land15:39
pedroniszyga: I think mvo is workong on it as well15:40
zygayes, we just talked about it, mvo needs to work on release bits for a sec15:40
zygaand I have a moment before the next session15:40
mvopedronis: just looking at 2.34 test failures, annoying :/15:42
zygagustavo just mentioned15:42
pedronisah15:42
zygawe have 17 days for core1815:42
zygaso ...15:42
zygaI pushed an update to the remapping branch15:49
zygajust one comment left15:49
mvozyga: ta15:49
zygawe need to use the configstate.RemapToResponse in a few places15:50
zygaadding those now15:50
mvocachio: looking at your failure list now, I think    - external:ubuntu-core-16-64:tests/main/snap-interface  and     - external:ubuntu-core-16-64:tests/regression/lp-1721518  should be fixed with pr 552515:55
zygaand pushed now15:55
mupPR #5525: tests: cherry-pick test fixes from master for 2.34 <Created by mvo5> <https://github.com/snapcore/snapd/pull/5525>15:55
zygamvo: it's ready15:55
zygaI'll resume signal work15:56
mvozyga: yay, I will check in 5min or so, just going over some more failures15:56
mvozyga: thanks for that!15:56
zygasure :)15:56
cachiomvo, yes15:57
cachiomvo, thanks for this15:58
cachioI'll take a look after lunch15:58
mvocachio: maybe also the catalog-refresh, just pushed a cherry-pick15:58
mvocachio: I think the prepare-image-uboot one is just a slow network, so hopefully (if 5525 passes) we will be green15:59
mvoagain :)15:59
cachiomvo, yes16:00
zygamvo: DOH16:00
zygaI'm such a moron :)16:00
zygamvo: I know why the python version fails16:00
zygabecause it doesn't have the file trigger16:00
cachioprepare-image-uboot used to faile because of network slowness16:00
mvozyga: oh, of course, racy16:03
mvocachio: yeah, cool16:03
zygaso I'll propose a python version16:03
mvocachio: almost done then I think16:03
zygawith the file "notification"16:03
mvozyga: thank you16:03
zygaand that should be good16:03
cachiomvo, yes, for 32 bits we have the same issues, so it should be fixed for free16:04
zygamvo: do you want me to propose that fix in a separate PR or roll it into PR 541016:09
mupPR #5410: tests: update tests to work on core18 <Core18> <Created by mvo5> <https://github.com/snapcore/snapd/pull/5410>16:09
=== pstolowski is now known as pstolowski|afk
mvozyga: it sounds like a separate is ok16:12
zygadoing that now16:12
pedroniszyga: mvo: 5491 still needs a 2nd review16:14
zygamvo: pushed https://github.com/snapcore/snapd/pull/552616:20
mupPR #5526: tests: fix raciness in stop mode tests <Created by zyga> <https://github.com/snapcore/snapd/pull/5526>16:20
zygapedronis: ack16:20
zygamvo: I updated 5410 with explanation about the raciness16:21
zygawe have lunch now so I'll check back later16:21
mvozyga: ta16:26
razer2The snap for Spotify does not run on Debian.16:44
cachioniemeyer, https://forum.snapcraft.io/t/how-to-deploy-spread-gce-gleaner/642216:54
cachioplease ping me in case something else is needed16:54
mvo5525 needs a review, all cherry-picks so should be trivial17:06
mvo(cherry-picks to 2.34)17:07
pedronis5527 needs to be tagged core18 ?17:56
mvocachio: new 2.34.1 beta will be ready soon (next 1h)17:56
mvopedronis: yes17:56
pedronismvo: did you backport 5522 ?17:57
mvopedronis: yes, cherry-picked it directly17:59
pedronisI see it now18:01
pedronissorry18:01
zygacan someone please review https://github.com/snapcore/snapd/pull/552118:09
mupPR #5521: snap-confine: mount internal tooling even for the core snap on core18 <Core18> <Created by mvo5> <https://github.com/snapcore/snapd/pull/5521>18:09
zygamvo: are you wrapping up for today?18:16
zygaMATCH failed again18:26
zygaman18:26
cwaynemvo: and this beta will have that canbus interface PR?18:27
zygacwayne: yes18:27
zygait does18:27
cwayneyay :)18:27
cwaynejhodapp: ^18:28
mvozyga: not yet18:42
mvocwayne: yes18:43
mvocwayne, cachio new beta should be ready in ~30min or so18:45
cachiomvo, waiting ifor this to validate it18:46
niemeyercachio: Thanks!18:46
cwaynemvo: will keep an eye out, thanks18:48
cachioniemeyer, yaw18:48
mvothanks guys18:54
=== JanC_ is now known as JanC
mvocachio, cwayne 2.34.1 ready in beta19:08
cachiomvo, already downloading inmages19:08
cwaynemvo: already testing :)19:09
mvocwayne: \o/19:11
* cachio afk19:18
jhodappcwayne, woohoo!19:22
=== chihchun_afk is now known as chihchun
=== chihchun is now known as chihchun_afk

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