IRC logs for #buildstream for Thursday, 2019-05-16

*** benschubert has quit IRC00:05
*** nimish2711 has joined #buildstream04:07
*** nimish2711 has quit IRC04:12
*** nimish2711 has joined #buildstream04:13
*** nimish2711 has quit IRC04:37
*** nimish2711 has joined #buildstream04:38
*** nimish2711 has quit IRC04:43
*** nimish2711 has joined #buildstream04:43
*** nimish2711 has quit IRC04:53
*** juergbi has quit IRC05:07
*** juergbi has joined #buildstream05:09
*** nimish2711 has joined #buildstream05:39
*** nimish2711 has quit IRC05:59
*** nimish2711 has joined #buildstream05:59
*** nimish2711 has quit IRC06:24
*** nimish2711 has joined #buildstream06:25
*** paulsherwood has joined #buildstream06:32
*** paulsherwood has joined #buildstream06:32
*** paulsherwood has joined #buildstream06:32
*** nimish2711 has quit IRC06:40
*** tristan has joined #buildstream06:41
*** nimish2711 has joined #buildstream06:55
*** nimish2711 has quit IRC07:31
*** nimish2711 has joined #buildstream07:34
*** ikerperez has joined #buildstream07:56
*** rdale has joined #buildstream07:58
*** benschubert has joined #buildstream08:07
*** bochecha has joined #buildstream08:18
*** raoul has joined #buildstream08:43
*** bochecha has quit IRC08:45
WSalmonhi guys, i have been doing to work with the python tar lib, and i think i have some idea's for https://gitlab.com/BuildStream/buildstream/issues/912 could i get some feedback if this sulution seems good? I others like it then i think we can mark it as new comers but only if we are exact about what we want08:54
WSalmontristan, juergbi ^08:55
*** ChanServ sets mode: +o tristan09:02
tristanWSalmon, numeric_owner according to the docs, will attempt to set the ownership user/group bits according to the numbers recorded in the tarfile rather than attempting to lookup the named owners on the target system where things are being extracted, if I am reading the docs correctly I believe that is what it means09:02
tristanWSalmon, However for source extractions, I think we *always* want ownership of extracted files to be given to the effective uid/gid of the extracting process09:03
tristanI could be wrong about that, or we might want an option later down the road, for extracting sysroots where we want to preserve the ownership bits, but that must block on support for recording ownership bits in CAS fist09:04
tristan*first09:04
*** phil has joined #buildstream09:04
*** bochecha has joined #buildstream09:04
tristanHowever currently, extractions happen on a local filesystem without a privileged user, before being injected into a build09:04
WSalmonyep, thats why extractfile seems like such a good solution, for now, until the cas becomes more fancy.09:04
WSalmonyep, thats why `extractfile` seems like such a good solution, for now, until the cas becomes more fancy.09:05
tristanWSalmon, I'm a bit skeptical about dumbing down the surrounding code to only do what CAS *currently* supports09:06
WSalmonNot only have i been working with Tars, but something simmilar to this bug got me the other day for something i was trying to build09:06
tristani.e. I would much prefer that the day that we add support to CAS to record richer FS metadata, that we don't have to go chasing down other code paths09:06
WSalmononce the cas can take more info we can just add exactly what we can handle09:06
tristanin order to leverage it09:06
tristanWSalmon, however I think these are rather separate topics09:07
tristanWe are talking about source extractions09:07
tristanNot artifacts09:07
tristanSo the barrier here is that the user will always have limited permissions of what they can do with a source extraction09:08
tristanOnce it is in an artifact, permissions, ownership bits, abstract OS dependent filesystem metadata can start to be recorded09:08
tristanAnd CAS supporting that should just transparently/automatically support everything it can (not only CAS, I should say the sandboxing also plays a part in this)09:08
*** phil has quit IRC09:09
*** phildawson has joined #buildstream09:10
tristanWSalmon, I think that first off, extracted files need to belong to the active user in any case09:10
*** benbrown has joined #buildstream09:11
tristanThe behavior of GNU Tar is ... IIRC, to automatically assign files to the active user if the user is not superuser, and to assign UID/GID recorded in the tarfile in the case that the extracting user is superuser09:12
tristanWSalmon, I dont recall if it is that, or if it is a try/fallback approach for each file, but the point is that it is anyway nondeterministic (you can get different results depending on your privileges), that's not good09:12
tristanSo making sure that extracted files always belong to the user extracting them is certainly a good thing09:13
*** jonathanmaw has joined #buildstream09:14
WSalmonit seems like we can make the plugin sufficently reprojecable with `extractfile` but anything else would have some unknowns09:30
tristanIt's quite possible that we should be looping through the tarball itself rather than extractall yes09:31
tristanIt's probably not a newcommers issue, there are a few things that need careful consideration (for instance, the globbing of what to extract needs to be preserved)09:32
tristanWell, not sure if that's what newcommers means, we should probably not paint it as "dead easy to solve"09:33
*** bochecha has quit IRC09:39
*** bochecha has joined #buildstream09:39
*** lachlan has joined #buildstream09:42
*** tristan has quit IRC09:49
*** lachlan has quit IRC09:50
*** lachlan has joined #buildstream09:56
*** lachlan has quit IRC10:01
Kinnisonjonathanmaw: are our WSL runners dead?10:02
* jonathanmaw has a look10:02
jonathanmawWSL runner's log has a lot of "your browser sent an invalid request" messages, not sure if that's client error or server error though10:04
*** tristan has joined #buildstream10:05
jonathanmawhmm, the CI settings say that they can't contact the runner10:05
jonathanmawI'll give it a kick10:05
jonathanmawIt's receiving jobs now I restarted it10:07
*** lachlan has joined #buildstream10:19
*** lachlan has quit IRC10:31
*** lachlan has joined #buildstream10:37
raoulphildawson, is there a way of running a single plugins test suite now that it uses the generic tests? Would like to run those without having to run the whole test suite10:44
phildawsonraoul, there is indeed. See https://gitlab.com/BuildStream/buildstream/blob/master/tox.ini#L134 for the details :)10:48
raoulAh nice, thank you :)10:49
raoulcan you not pass pytest arguments with this? i.e. not use -n 410:56
*** lachlan has quit IRC11:06
*** lachlan has joined #buildstream11:08
*** lachlan has quit IRC11:12
*** nimish2711 has quit IRC11:39
*** nimish2711 has joined #buildstream11:48
*** tchaik[m] has quit IRC12:34
*** tristan has quit IRC13:14
jonathanmawjennis: are you satisfied by the explanation to https://gitlab.com/BuildStream/buildstream/merge_requests/1342#note_170862989 ?13:17
jennisjonathanmaw, yeah looks good, I must've missed the if statement in update state13:19
*** lachlan has joined #buildstream13:40
*** tristan has joined #buildstream13:41
*** lachlan has quit IRC13:46
gitlab-br-botcoldtom opened issue #1026 (Add meson subproject support) on buildstream https://gitlab.com/BuildStream/buildstream/issues/102613:47
*** lachlan has joined #buildstream13:53
*** lachlan has quit IRC14:04
gitlab-br-botraoul.hidalgocharman opened MR !1345 (raoul/440-fix->master: Fix init_workspace for multiple sources) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/134514:16
raoul^ Noticed a mistake I made in source cache so made a fix MR. Pretty small so should be easy to review and get in.14:17
*** lachlan has joined #buildstream14:20
*** lachlan has quit IRC14:29
*** lachlan has joined #buildstream14:33
*** lachlan has quit IRC14:45
WSalmon*Im asking for a friend, is there a easy way to allow all overlaps even if they seem dangerous? only to be used while hacking you understand ;) i think overlap-whitelist should be set to something like `*` can i do that in the project.conf vars?14:50
*** lachlan has joined #buildstream15:01
*** juergbi has quit IRC15:03
*** juergbi has joined #buildstream15:15
*** lachlan has quit IRC15:53
*** bochecha has quit IRC15:57
*** lachlan has joined #buildstream16:01
*** nimish2711 has quit IRC16:18
*** raoul has quit IRC16:30
gitlab-br-bottpollard approved MR !1345 (raoul/440-fix->master: Fix init_workspace for multiple sources) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/134517:03
*** rdale has quit IRC17:06
*** lachlan has quit IRC17:14
*** jonathanmaw has quit IRC17:35
*** xjuan has joined #buildstream17:46
gitlab-br-botmarge-bot123 merged MR !1342 (shared/split_out_update_state_2->master: Split Element._update_state into cache key and artifact state methods) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/134218:19
*** slaf has quit IRC18:22
*** slaf has joined #buildstream18:36
*** slaf has joined #buildstream18:37
*** slaf has joined #buildstream18:37
*** slaf has joined #buildstream18:37
*** slaf has joined #buildstream18:37
*** slaf has joined #buildstream18:38
*** slaf has joined #buildstream18:38
*** slaf has joined #buildstream18:38
*** nimish2711 has joined #buildstream18:39
*** xjuan has quit IRC19:42
*** nimish2711 has quit IRC19:57
*** em has joined #buildstream21:39
*** em has quit IRC21:40

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