/srv/irclogs.ubuntu.com/2019/07/04/#snappy.txt

mborzeckimorning05:24
zygaGood morning05:58
=== morphis52 is now known as morphis
mborzeckizyga: hey06:17
mborzeckizyga: have you seen https://bugzilla.redhat.com/show_bug.cgi?id=1726382#c3 ? my best bet is that he's running oracle linux :)06:23
mborzeckizyga: btw. this one can probably be closed https://bugzilla.redhat.com/show_bug.cgi?id=1706020 but I have no clue whether we need to do anything special to have the whole BZ/notification machinery do its thing (Pharaoh_Atem maybe?)06:29
zygaChecking06:38
zygaha06:42
zygathat's some automaton catching up with CVEs06:42
zygabut that's all fixed for a while now06:42
zygahttps://bugzilla.redhat.com/show_bug.cgi?id=1706013 is closed already so probably nothing more needed06:43
zygabut I don't know for sure06:43
zygamborzecki: I made spread.zygoon.pl refresh yesterday06:46
zygamborzecki: no longer backed by my server, this time backed by CDN06:46
zygamborzecki: I tried to make debian images by my cloud init foo was insufficient and I only recalled jdstrand's post late in the evening06:47
mborzeckizyga: nice06:47
zygamborzecki: I learned that qemu can use qcow images that are not real images but instead contain an embedded https reference06:57
zygamborzecki: perhaps spread could keep "embeded" images that point to spread.zygoon.pl :)06:57
zygamborzecki: I don't know the caching story though, would depend on being usable this way06:58
mborzeckizyga: qcow can reference http? interesting06:59
zygayeah07:02
zygastuff we learn07:02
zygaprobably full of CVEs pending ;D07:02
zygaok, quick pass through PRs07:04
=== pstolowski|afk is now known as pstolowski
pstolowskiheya07:11
zygahejka07:12
mborzeckipstolowski: hey07:13
mborzeckionly 2 pages of reviews07:18
pstolowskiyay07:46
mborzeckipstolowski: added a comment https://github.com/snapcore/snapd/pull/7052#discussion_r30027649508:05
mborzeckipstolowski: in Commit() you could probably do `purgeNulls(t.pristine)` too, but maybe doing it per snap is less work in the end08:06
mborzeckiheh, 17C, while last week it works 30C this time of day08:11
mborzeckiheh s/works/was/08:15
zygais mvo off today?08:16
zygamborzecki: woow08:16
zygaenvy08:16
zygait's so hot here already08:16
zyga28 in the morning08:16
Chipacazyga: iirc mvo is off yes08:17
Chipacaand ijohnson08:17
zygaI dismissed his needs changes review on https://github.com/snapcore/snapd/pull/705308:17
zygaI would love to get a 2nd review to be sure it's ok08:18
zygathe only thing I'm not sure about is the modprobe mechanism08:18
zygawhere I suspect the comment is incorrect but ... we're not sure08:18
Chipacazyga: no, you need two reviews08:22
zygaChipaca: I said this already but https://spread.zygoon.pl/08:22
zygaChipaca: I know, I dismissed mvo's -1 review after addressing the requests08:23
Chipacazyga: i mean, you dismissed one of mvo's reviews, you should dismiss the other one too?08:23
zygaChipaca: why? jamie was ok with the review :)08:23
zygaChipaca: and mvo only commented on the commit message08:23
mborzeckiis https://elixir.bootlin.com flaky for you too?08:24
Chipacahm, fair08:24
zygaChipaca: review it if you can, it's relatively short08:24
zygait's just comments and two new lines08:24
zygahome and tmp08:24
Chipacai'll try08:24
zygamborzecki: yes08:24
zygamborzecki: still negotiating ssl stuff08:24
zygait's loading a little now08:24
mborzeckihmm08:25
zygaloaded08:25
zygahey pedronis08:25
zygapedronis: just sharing https://spread.zygoon.pl/08:25
zyga(now backed by proper CDN and stuff, not my pico-server)08:26
pedronisdid I mention, did people see, this? https://forum.snapcraft.io/t/remodeling-devicectx-refactoring-and-new-test-helpers/1211408:37
pedronisChipaca: hi, is 6878 ready for re-review?08:38
Chipacapedronis: I didn't change the struct yet, but other than that yes08:40
Chipacapedronis: the struct order i mean08:40
pedronisunderstood08:40
Chipacathat shouldn't break anything else :-)08:40
Chipacapedronis: found another merge issue, fixing that08:49
Chipaca:-/08:49
pedronisChipaca: ok, anyway need to look at some other PRs and forum topics first, but wanted to know if to look at it after08:50
Chipacapedronis: ah ok08:50
Chipacapedronis: it's no biggie, i'll have it fixed and push it and the struct reorg in no time08:50
pedroniszyga: not urgent, but I was looking at spread tests set to manual, and wondering if the test here can be reenabled now:  https://github.com/snapcore/snapd/pull/3076/files08:59
zygaoh, good catch09:00
zygaI think so09:00
zygalet's see09:00
zygabreakfast09:26
mborzeckiChipaca: https://github.com/snapcore/snapd/pull/706309:34
Chipacathe interface-calendar-service test is rather flaky09:41
Chipacaor rather its restore09:41
zygabrb09:56
Chipacazyga: note #7061 has two +1's09:59
Chipacaniemeyer: can you add anonymouse64 to snapd-committers?10:00
zygammm10:05
zygaoh indeed10:05
zygathank you10:05
zygaI asked about this and mvo said he did add him10:05
zygabut perhaps my question was misunderstood10:05
Chipacazyga: there's a maze of groups, all different10:10
zygaaha10:10
zygasucky10:10
* Chipaca notes it is Time For A Break, and complies10:15
Eighth_Doctorzyga: are we going to be dead in the water for Fedora 31?10:24
Eighth_Doctorwith the cgroupsv2 switch10:24
zygahopefully not, we want to support it but it's not on the roadmap as an item for us10:25
zygaperhaps pedronis can advise since he's running the  schedule with mvo10:25
Chipacazyga: https://github.com/snapcore/snapd/pull/7062#issuecomment-508434440  http://i.imgur.com/eTic1wS.jpg10:37
zygainteresting10:38
zygait _feel_ more like a different bug though10:38
zygaabout the fact we build snapd incorrectly in testing10:38
zygabecause we build it on the host10:38
zygaand  then happily stick it into 16.04 world10:38
zyga18.04+ has some incompatibility it seems10:38
zygathe error is  /usr/lib/snapd/snap-confine: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.27' not found (required by /usr/lib/snapd/snap-confine)10:39
zygaso...10:39
zygait's not the test10:39
zygait's all the tests10:39
zygawe discussed  this in the past10:39
* Chipaca adds more http://i.imgur.com/eTic1wS.jpg10:39
mborzeckifedora repos are down?10:49
zygamborzecki: dunno11:05
zygamborzecki: small update to mountinfo-tool11:05
zygamborzecki: https://github.com/snapcore/snapd/pull/706411:06
zygamborzecki: I have a  few more patches after this one11:08
Chipacamborzecki: #7063 GTG11:08
mborzeckiyay11:10
Chipacazyga: what's the status of all the per-user mount ns work?11:11
zygaChipaca: it's paused after MS_SHARED bug which will also include extra  new tests, this is coming off that pipeline11:13
zygaChipaca: mountinfo-tool needs to grow a few more patches to be useful here11:13
zygaChipaca: one of them is interesting11:13
zygaChipaca: rest are pretty boring and obvious11:13
zygaChipaca: (renumbering that keeps peer group IDs in sync across more than one file, so that we can test parent/slave relationship between per snap and per-user nses)11:14
Chipacazyga: is there a reason #6341 isn't labelled with the per-user ns thing?11:14
zygano, not really11:15
zygaperhaps it pre-dates that?11:15
zyganot sure11:15
zygasome changes are bound to come that way11:16
zygabased on the feedback I have already11:16
Chipacamborzecki: what's blocking #6708 ?11:16
zygabut I want to properly test properties of each ns before proceeding11:16
zygaChipaca: nobody fixed https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/182438411:16
Chipacazyga: ISTM that a lot of that work is too early to actually be reviewed11:17
mborzeckiChipaca: let me check11:17
mborzeckiChipaca: apparmor packages in ubuntu are built without -fPIE  https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/182438411:18
Chipacaso much stuff is blocked or whatnot, it seems like we'd all make lousy gardeners11:18
mborzeckiChipaca: -fPIC11:18
Chipacamborzecki: -fCAKE11:18
mborzeckiChipaca: -fLONGFLAG, as a result we can't build s-c as a (sweet-cherry)PIE binary11:18
zygaISTM?11:18
zygaah11:19
zygait  seems to me11:19
zygaChipaca: 6341?11:19
Chipacazyga: and the rest of per-user-ns11:19
mborzeckihm mvo is off today, maybe someone else can take a look at https://github.com/snapcore/snapd/pull/7041 ?11:20
zygaI it's not early, it was ready to  be  reviewed for a long time before we realized sharing was broken, but was very slow to  review or got stuck on prerequisites. e.g. https://github.com/snapcore/snapd/pull/6347 is a chunk of  the bigger WIP  branch and the bigger WIP branch was reduced tenfold since it was first opened11:20
zygaI wish there was a "parked" label that would let us keep a PR open and not lose state but not worry reviewrs11:21
zyga*reviewers11:21
Chipacazyga: closing it doesn't lose state though11:21
zygayeah, except finding  it is harder11:21
zygaI can consider that if you want to run the numbers down11:22
zygabut then again https://github.com/snapcore/snapd/pull/5644 is close to its first anniversary :)11:22
pedronismborzecki: I will look at 6939 today (have to read some things first though)11:24
mborzeckipedronis: thank you!11:24
mborzeckizyga: hm oracle linux is missing from your os-release-zoo11:25
zygamborzecki: do we need special casing in snapd?11:26
zygaI don't recall running it ever11:26
Eighth_Doctorpedronis: https://fedoraproject.org/wiki/Changes/CGroupsV211:26
mborzeckizyga: i'm trying to come up with possible reasons for https://bugzilla.redhat.com/show_bug.cgi?id=172638211:26
zygawe reexec11:26
zygaand then all stuff breaks?11:26
mborzeckizyga: other than oracle linux or some old centos, or rexec (but that's off by default on non ubuntu?)11:27
mborzeckizyga: but it's snapd trying to call snap-seccomp from /usr/lib/snapd, even with reexec that path isn't baked into snapd11:27
Eighth_Doctormborzecki: we should _never_ be attempting re-exec11:28
Eighth_Doctorunless someone broke the override11:28
pedronisEighth_Doctor: thanks, we'll have to reevalute this, as zyga said is not in our immediate plans atm11:29
mborzeckiEighth_Doctor: i'm wondering what could possibly be the system that guy has, he's clearly getting the package from epel11:29
Eighth_Doctorpedronis: well, at least we had two years heads up...11:29
Eighth_Doctormborzecki: right, I'm confused too because I don't have that problem on my rhel or centos systems11:30
pedronisEighth_Doctor: is there somewhere where I can see the timeline, like when is beta freeze etc11:30
Eighth_Doctorthere are a lot of CentOS derivatives though11:30
Eighth_Doctorpedronis: https://fedoraproject.org/wiki/Releases/31/Schedule11:30
Eighth_Doctorpedronis: the discussion in devel@ makes me think that there will be almost no chance it'll get reverted11:31
Eighth_Doctorall the container tools in Fedora are cgroupsv2 ready11:31
mborzeckii suppose once fedora does the switch, arch will follow11:32
mborzeckibc bleeding edge and such ;)11:32
Eighth_DoctorYep11:35
Eighth_DoctoropenSUSE will switch at the same time as well11:35
Eighth_DoctorRichard is trying to beat Fedora to "breaking everything" with a cgroups v2 switchover11:35
mborzeckihahah11:35
Eighth_Doctormy estimation is that basically all major upstream distros except Debian (well, because Debian :( ) will be switched to cgroups v211:36
zygaBreak11:38
ograContinue11:39
mborzeckizyga: hm that --self-test makes me uneasy, but so does `mv mountinfo-tool mountinfotool.py && ln -s mountinfotool.py mountinfo-tool && python -m unittest ./mountinfotool.py`11:45
zygaWhy does it make you uneasy?11:46
zygaI like it because you can copy it around as a single file11:47
zygaAnd it works pretty much anywhere11:47
mborzeckizyga: feels a bit off, otoh it's nice to have some tests there, so maybe if there's no other way we'll do it like you prooposed11:47
pedronismborzecki: which PR is that ?11:54
mborzeckipedronis: https://github.com/snapcore/snapd/pull/7064/11:54
pedronismade a couple of comments about this there11:58
pedronisI'm not particurly against given the nature of the tool11:59
zygaReplied, will tweak after lunch12:00
=== ricab is now known as ricab|lunch
pedroniszyga: read bzr help selftest, I stand that is not a great name for that, indeed the help is confusing, it never clarifies what these tests are12:08
zygapedronis: I’ll gladly rename it12:24
cachiopstolowski, hey12:34
pstolowskicachio: hi, what's up?12:35
cachiopstolowski, I am debugging the test auto-refresh-retry which is failing on beta validation12:36
cachioand I see this12:36
cachiohttps://paste.ubuntu.com/p/g58SRvmZhZ/12:36
cachiopstolowski, it never shows "state ensure error: persistent network error"12:37
pstolowskicachio: where are you seeing this?12:37
cachioin jenkins logs12:38
cachiopstolowski, I am using a vm inside real hardware12:39
cachioto validate the image12:39
cachiobeta image12:39
pstolowskicachio: and it's core 16?12:40
cachiopstolowski, yes12:40
pedronismborzecki: sorry for noticing this late, where is the verb "position" coming from in the gadget work? is it a ubuntu-image term?12:43
mborzeckipedronis: positiona as in gadget.PositionVolume()? this one is from reviews, iirc the first version was LayoutVolume()12:45
pedronismborzecki: because we have already layouts ?12:45
pstolowskicachio: ok, it seems that it fails much earlier at device registration (because of no network), before even reaching the logic of auto refresh that we're trying to test there12:45
mborzeckipedronis: yeah, not to confuse people12:45
pedronismborzecki: but the new verb create messages that are to relate to12:46
mborzeckipedronis: also, the structures are named PositionedSomething, as in positioned within the volume12:46
pedronisthat's what I'm noticing reading the last PRs12:46
pedronisthere is no general sense of what "positiong a volume" means12:46
pstolowskicachio: is this run with no network at all?12:46
pedronismborzecki: "cannot position volume" is a fairly obscure message12:46
cachiopstolowski, it has network12:46
mborzeckipedronis: we can go back to LayoutVolume(), then `cannot layout volume contents` or something similar12:47
cachiopstolowski, the test is executed in a vm indice a machine (real hardware)12:47
cachiolike the nested suite12:47
pstolowskicachio: okay; maybe we need to wait for registration before entering network namespace in the test. i'll see. is it possible for me to run tests from my local branch there?12:48
pstolowskicachio: or can i give you a diff to try out?12:48
cachiopstolowski, sure12:49
pstolowskiokay, i'll try to tweak the test a little bit12:49
mborzeckipedronis: hmm https://www.thesaurus.com/browse/lay%20out verb synonyms are even more confusing12:50
pedronismborzecki: yes, I think  the expected verb here is "lay out"12:50
pedronisand we just have to live with the double use12:50
pedronisthe context is fairly different anyway12:50
mborzeckipedronis: LayOutVolume() then? caps are different since it really stands for 'lay out'12:51
pedronisyes, or VolumeLayout (more functional)12:51
pedronisand then  s/Positioned/LayedOut/  and s/Positioning/Layout/12:52
pedronissorry LaidOut12:52
mborzeckimhm12:52
pedronisI mean for Positioned12:53
pedronismborzecki: anyway I commented on this also in 6939, don't know if you prefer to fix everything in master and update that one12:56
pedronisor do it after12:57
pedronis6939 needs a 2nd review anyway ATM tough12:57
mborzeckipedronis: probably after mounted updater lands, there's fewer conflicts with each PR that lands12:58
pedronismborzecki: anyway I have some other comments about external message terminology in 6939 (and probably previous code)12:58
pedronisthat I put there12:59
mborzeckipedronis: ok, will check that, thanks!12:59
pedronisChipaca: standup?13:02
Chipacatrying to :)13:02
=== ricab|lunch is now known as ricab
Chipacamborzecki: question, why partx instead of losetup?13:35
Chipacamborzecki: (for after the standup)13:35
Chipacaum13:35
Chipacamborzecki: not you13:35
mborzeckicmatsuoka: ^^13:35
Chipacacmatsuoka: you ^ :)13:35
Chipacasilly people having same-length nicks13:36
zygain the past losetup could not do partitions13:36
zygaperhaps kpartx just because13:36
Chipacayes, but it can now, since 16.04 at least13:37
zygamkcoffee ---no-sugar13:38
Chipacaoh wait, partx and kpartx are different animals13:38
zygaChipaca: muscle memory13:38
ChipacaI don't know partx13:39
Chipacakpartx was poison13:39
cmatsuokaChipaca: partx was available inside the image and I used it because it was there. I don't know if losetup uses the same call or not, but we can test it13:40
zygaChipaca: can you look at python bit13:41
zygapretty please13:41
zygahttps://github.com/snapcore/snapd/pull/706413:41
zygaI will push two more but they depend on this test setup13:42
cmatsuokaanyway, the bio race in kernel seems to be a real bug13:42
Chipacacan somebody with an 18.04 server do an uname -r just to confirm something for me please?13:49
cmatsuokaChipaca: 4.15.0-54-generic13:51
Chipacacmatsuoka: thanks13:51
cmatsuoka(and my 18.04 desktop says 4.15.0-52-generic)13:52
Chipacacmatsuoka: thanks²13:53
cmatsuokayaw13:54
pstolowskicachio: can you grab 'snap changes' of that failing autorefresh retry test?14:00
cachiopstolowski, sure14:07
pstolowskithanks14:07
cachiopstolowski, it will take a time to run14:07
pstolowskiok14:08
mborzeckizyga: we got our answer https://bugzilla.redhat.com/show_bug.cgi?id=1726382#c514:19
zygaInteresting14:23
zygaOh well14:23
zygaNeeds a well made answer14:23
zygaI’m AFK with dog now14:23
zygamborzecki: do you think the question warrants a FAQ response from us14:36
zygamborzecki: like "we want to have one codebase, we want to support reexec, etc'14:36
cachiopstolowski, I think it is related to the model issue14:57
cachiopstolowski, because I cannot reproduce it when I run console conf and register the user14:57
pstolowskicachio: right, i thought so as you discussed that on standup14:58
pstolowskicachio: snap changes would help confirm it14:58
cachiopstolowski,  yes, I'll add that to the test15:02
cachiothanks15:02
pstolowskicachio: good idea15:02
pedroniscachio: I created the card I discussed15:09
cachiopedronis, nice, thanks15:09
zygamborzecki: one more small review perhaps?15:16
zygahttps://github.com/snapcore/snapd/commit/cbf0afae9c43716f2c9ef73b849947163769091d15:16
zygaI'll open it in a sec, just waiting for travis15:16
zygaeh portal test..15:21
* cachio lunch15:35
zygahttps://github.com/snapcore/snapd/pull/7065 is ready now :)16:03
zygaand now I can work on the rest, because base has landed16:03
zygawhee16:03
=== pstolowski is now known as pstolowski|afk
iceysergiusens: I don't mind you making that change in the rust PR, or I can get to it tomorrow16:56
sergiusensicey: thanks, i might do it late tonight17:01
iceyI'll look before I start on it then :-)17:02
zygahttps://github.com/snapcore/snapd/pull/7065 anyone?17:15
zygasergiusens: ^ python, wanna see?17:15
=== Greyztar- is now known as Greyztar
ogrageez, was the store just down ??17:25
ogra(i'm just hacking on a new architecture and spent the last hour debugging because i got "error: unable to contact snap store" ... now it started working out of the blue)17:26
ograbad timing i guess17:26
ograogra@pi4:~$ sudo hdparm -tT /dev/sda117:52
ogra Timing cached reads:   1508 MB in  2.00 seconds = 754.22 MB/sec17:52
ogra Timing buffered disk reads: 1106 MB in  3.00 seconds = 368.64 MB/sec17:52
ograhmm, not to bad for a pi ...17:52
zygaWow18:49
zygaWill you have models soon?18:50
ograyou wish ... no u-boot port yet18:51
ograi'm running classic on a USB3.1 SSD with the raspbian kernel currently18:52
ograstill ... makes a nice build machine ;)18:54
bulldog68hi am running into a problem with my application when it is snap packaged :(  , the issue is with reading the data from fifo file18:56
bulldog68https://forum.snapcraft.io/t/no-read-from-fifo-device-in-snap-packaged-app/12150/418:56
bulldog68am getting apparmor denials when i try to read from fifo file18:57
bulldog68Uploaded file: https://uploads.kiwiirc.com/files/fd0e794c69323a8d5976f6d3a6a544c3/pasted.txt18:57

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