IRC logs for #buildstream for Wednesday, 2019-06-26

*** brlogger has joined #buildstream09:34
*** lachlan has joined #buildstream09:42
*** lachlan has quit IRC09:49
gitlab-br-botmarge-bot123 merged MR !1416 (jennis/do_not_leak_project_specific_remotes->master: Do not leak subproject remotes) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/141609:52
*** lachlan has joined #buildstream09:56
*** tristan has joined #buildstream10:01
*** lachlan has quit IRC10:29
*** lachlan has joined #buildstream10:30
alexandrufazakasIf I use something like this https://pastebin.com/U64jkV8u and I want a test to trigger this, how should I check that it fails successfully?10:40
alexandrufazakasNot sure what to assert in the test10:40
juergbialexandrufazakas: result.assert_main_error(ErrorDomain.APP, 'directory-not-empty')10:47
alexandrufazakasjuergbi: oh, alright. Thank you :)10:47
benschubertjuergbi: hey, with the new auto pull of junctions, is it normal that I don't get the fancy new UI while the junctions are pulled?10:56
juergbihm, no, you should see the scheduler UI10:57
juergbiat least it seemed to work fine in my manual tests (that UI is not covered by CI)10:57
benschuberton WSL at least I am not10:57
juergbibut the fetching works fine, just no scheduler UI?10:59
*** lachlan has quit IRC10:59
benschubertjuergbi: yep!10:59
juergbithere might certainly be rough edges. maybe UI only shows up for some bst commands. not sure why that would be the case, though11:00
benschubertI just get stuck at 'Loading Element' for 30 minutes, then I have my usual crash :)11:00
tlater[m]WSalmon: After some exploration, it looks like hardlinks in python are actually created as if they were the original file when the original file does not exist :)11:00
juergbihaha11:00
benschubertah right I'm doing a 'show'11:00
benschubertthat might be it11:00
juergbiI actually did test with bst show, though, iirc11:00
WSalmontlater[m],  so what you were worried about is a non issue?11:01
WSalmonwith the python tar lib11:01
juergbibenschubert: is it possible that it's not about the fetching but about staging the subproject into the .bst temp directory?11:01
tlater[m]WSalmon: We can still hard link to files outside the staging directory11:01
juergbibenschubert: only fetching is done via scheduler11:02
tlater[m]It's just simpler to fix that (just check if we do that)11:02
benschubertjuergbi: no, it's definitely fetching11:02
*** lachlan has joined #buildstream11:04
gitlab-br-botaevri opened (was WIP) MR !1419 (aevri/set_resource_limits->master: platform: re-scope set_resource_limits) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/141911:17
*** tpollard has quit IRC12:02
*** tpollard has joined #buildstream12:03
*** lachlan has quit IRC12:15
gitlab-br-botcs-shadow opened MR !1422 (chandan/fix-readme-badges->master: README.rst: Fix path for badge images) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/142212:51
gitlab-br-botmarge-bot123 merged MR !1420 (chandan/fix-egg-info-gitignore->master: .gitignore: Fix path of .egg-info) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/142012:54
*** lachlan has joined #buildstream13:07
benschuberttristan: if you have time today for !1401 it would be much appreciated, I have 4-5 MRs waiting on this one13:17
gitlab-br-botMR !1401: introduce a Node api, and remove node_get https://gitlab.com/BuildStream/buildstream/merge_requests/140113:17
*** raoul_ is now known as raoul13:19
*** ChanServ sets mode: +o tristan13:26
tristanbenschubert, scanning it now...13:26
tristanbenschubert, sorry for the delay...13:26
benschuberttristan: no worries, I know it's a huge one, it was hard to split :/ thanks a lot!13:27
WSalmonplease could juergbi or tristan etc add Becky as a build stream developer, her gitlab username is beckyella1613:33
Beckytest13:38
tlater[m]Becky: test succeeded!13:39
juergbiWSalmon, Becky: done13:39
tristanjuergbi, mid-air collision :)13:39
Beckyjuergbi thankyou13:39
tristanYou get to doubly be a developer, as it appears to have succeeded twice !13:40
juergbihehe13:40
tristanbenschubert, I think I'm done with comments... in general it's looking great, but I think incomplete13:49
WSalmonthanks juergbi tristan13:50
benschuberttristan: thanks a lot! It might have slipped through but the target branch is 'bschubert/new-node-api' not Master , I plan into making more PRs to this branch and merge the new-node-api to master with the whole new API13:50
benschubertso it's expected that it doesn't fix everything yet :)13:50
tristanWe had our discussion about fetching special strings, like "project paths", that is kind of a separate discussion because the node needs to have knowledge of the project in order to resolve it - but in general I don't think we should be having APIs outside of `Node` which take nodes as arguments if we can avoid them13:50
benschubertI just wanted to have more manageable MRs and then a last huge round of review13:50
tristanEspecially fetching the provenance seems to be a no-brainer that it should be part of Node13:51
benschubertagreed, I want to get rid of all of those when it make sense (basically everything in _yaml)13:51
tristanYes, ok we are on the same page :)13:51
*** lachlan has quit IRC13:51
benschubertgreat! I'll change the default=, merge to new-node-api and  continue then, thanks a lot for the thorough review!13:52
tristanyeah I missed that the target branch was not master13:52
tristanbut I think that doesnt change my scan :)13:52
benschubertI know, it surprised everybody :D13:52
juergbitristan: bst source checkout currently requires --fetch to fetch uncached sources. should we drop this as well (always fetching as needed), in line with the change for subprojects/junctions?13:52
benschubertwe don't do that often in the project, but I think for such a thing it's easier13:52
tristanbenschubert, yes it makes sense, I hope that things aren't churning too much for your rebases though :)13:53
tristanjuergbi, good question13:53
tristanjuergbi, I think it makes sense to drop it13:53
benschubertIt's been surprisingly smooth, but that's one of the reasons I'm hunting for reviews, to not have to do it for too long ;)13:54
tristanjuergbi, granted of course we should have the UI kick in for fetches which happen and everything... I think it will be more intuitive that way yes13:54
juergbitristan: sounds good, should be better for consistency13:54
tristanjuergbi, But it presents a more difficult question13:54
juergbiyes, should obviously use the usual UI13:55
tristanheh now that I think of it13:55
tristanWell, we could at least do this step for source fetches in a uniform way13:55
tristanjuergbi, like... what about `bst artifact checkout` ?13:55
tristanhaha13:55
juergbiI was thinking about this as well13:55
tristan"Should the pull be implied ?"13:55
juergbiah, pull13:55
tristanLets not think about this for now I think13:55
juergbiI was only thiking about building13:55
benschuberttristan: actually, we often used 'default' in plugins already (https://gitlab.com/BuildStream/buildstream/merge_requests/1401/diffs#diff-content-ae21ae20fa7c1172671e2b7cd0c6ba979c572eaf), do you want to get rid of all of them?13:56
juergbiimplicit building is easier to argue against13:56
tristanjuergbi, yes it is hehe :)13:56
tristanbenschubert, I think it would be more consistent but honestly - I don't feel really very strongly on that point13:56
benschubertok, I'll keep it for now for simplicity and we can re-review later on13:57
benschubertthanks!13:57
juergbitristan: it's actually somewhat related to the second point here https://mail.gnome.org/archives/buildstream-list/2019-April/msg00027.html13:57
tristanbenschubert, I'm happy that it is not required to be a keyword argument though13:57
juergbicompleting a partial artifact is not that different from pulling one that is not yet local at all13:57
tristanjuergbi, Good point13:57
benschuberttristan: if we want cython access, we need to allow positional arguments anyways ;)13:57
juergbihowever, in any case, I think it's fine to consistently do implicit source fetching and think about pulling separately13:58
tristanbenschubert, Does cython prevent us from our `*` signatures ?13:58
benschuberttristan: sadly yes if we want to be able to access it with C-speed13:58
tristan:-/13:59
benschubertif we _really_ want to keep it, I can however have 2 versions, one for C access (the core) and one public13:59
tristanbenschubert, my issue with that is mostly about API extensibility13:59
benschubertwe can always have public wrappers for plugins13:59
benschubertits slightly less nice13:59
benschubertbut works13:59
tristanit's really nice to be able to put that `*` and know that anything beyond the `*` *must* be keyword arg, it lets us add things without breaking API more easily13:59
tristananyway, not such a huge hitch, I don't think we need to care much about it right now14:00
tristanbenschubert, then again this depends how pervasive the cython API surface will be14:01
gitlab-br-botmarge-bot123 closed issue #1056 (Badge images in README are broken) on buildstream https://gitlab.com/BuildStream/buildstream/issues/105614:01
gitlab-br-botmarge-bot123 merged MR !1422 (chandan/fix-readme-badges->master: README.rst: Fix path for badge images) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/142214:01
tristanright now for Node APIs I think it's not a big deal14:01
tristanfor Element API on the other hand, it's really good to have this control14:01
benschubertSure, I don't want to bring API extensibility problems with Cython, if we have to do something we'll make sure we have a wrapper :)14:02
tristanyeah lets see when we get there14:03
benschubertagreed14:03
tristanat least there are avenues14:03
gitlab-br-botBenjaminSchubert merged MR !1401 (bschubert/node-api-noget->bschubert/new-node-api: introduce a Node api, and remove node_get) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/140114:11
gitlab-br-botBenjaminSchubert opened MR !1424 (bschubert/node-api-nodel->bschubert/new-node-api: _yaml: Remove 'node_del' and support `del mapping[key]`) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/142414:23
gitlab-br-botBenjaminSchubert opened MR !1425 (bschubert/node-api-noset->bschubert/new-node-api: Remove 'node_set'. Now use MappingNode[key] = value) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/142514:29
*** tristan has quit IRC14:29
gitlab-br-botBenjaminSchubert opened MR !1426 (bschubert/node-api-keys->bschubert/new-node-api: Cleanup `MappingNode` key/values/items accessor) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/142614:30
gitlab-br-botjuergbi opened MR !1427 (juerg/source-checkout->master: Fetch sources as needed for bst source checkout) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/142714:35
*** lachlan has joined #buildstream14:36
tlater[m]alexandrufazakas: I'll give you developer permissions, would you mind reopening the MR on a branch on the main repo? It looks like CI doesn't want to run on your fork.14:37
alexandrufazakastlater: sure thing14:37
*** tristan has joined #buildstream14:38
tlater[m]It's just annoying to have to pull your branch to see your tests ;)14:38
alexandrufazakasHeh, yeah, no worries14:38
*** lachlan has quit IRC14:40
*** phildawson_ has joined #buildstream14:42
*** phildawson has quit IRC14:42
*** lachlan has joined #buildstream14:44
*** lachlan has quit IRC14:48
gitlab-br-botwillsalmon opened MR !1429 (willsalmon/platformRefactor->master: Refactor Platform and Snadboxes) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/142914:49
raoulWith anyone with some grpc/protobuf knowledge care to look at !1410? It's had some review but it'd be good if someone familiar with those things had a look14:56
gitlab-br-botMR !1410: Capabilities service https://gitlab.com/BuildStream/buildstream/merge_requests/141014:56
raoulmaybe you juergbi?14:56
WSalmonhi benschubert i seem to remember but i could be wrong that tests-fedora-missing-deps are meant as a proxy to WSL i was wondering why the test are run as root https://gitlab.com/BuildStream/buildstream/blob/master/.gitlab-ci.yml#L124 is root helpful for the proxy?15:05
juergbiraoul: added a couple of comments15:08
*** bochecha has quit IRC15:09
gitlab-br-botAlexFazakas opened MR !1430 (AlexFazakas/add-bst-init-argument->master: Add bst init argument) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/143015:10
*** lachlan has joined #buildstream15:19
tlater[m]alexandrufazakas: Sorry, I'm a little distracted, haha. I'll take a look once your CI run is through.15:25
alexandrufazakastlater: No hurry :)15:26
benschubertWSalmon: they are not a proxy, just to ensure we are marking our tests correctly :)15:50
benschubertrunning as root should not be needed15:50
WSalmonthat test confused me by making a user and chown'ing everthing and then running as root15:52
WSalmonthanks benschubert15:52
gitlab-br-botraoul.hidalgocharman opened issue #1057 (Use capabalities service in artifact cache) on buildstream https://gitlab.com/BuildStream/buildstream/issues/105715:53
*** lachlan has quit IRC15:53
alexandrufazakasIs there a way I can see print's I use inside tests? -s doesn't seem to help15:53
WSalmonalexandrufazakas, the stdout and stderr get printed seperatly15:54
WSalmonlook at the top of the stderr section to see the stdout15:54
WSalmonor ask print to print to stderr instead of stdout15:55
alexandrufazakasWSalmon: oh, you're right, it wasn't very obvious. Thanks :D15:55
raoulta juergbi, responded to the discussions so I'll pass over to marge once the pipelines passed unless you've got any other complaints. There's one point on !1402 that still needs a response to if you can have a look at that too15:56
gitlab-br-botMR !1402: Configuration option for disabling blob fetching with RE https://gitlab.com/BuildStream/buildstream/merge_requests/140215:56
WSalmonwe care about what goes to stdout and what gose to stderr so its helpfull to have them seperated in some regards even if it is a bit of a trap for new people15:57
WSalmonwe never want print() functions to end up in master but for debuging it can be handy, Becky alexandrufazakas -> https://stackoverflow.com/a/1580810515:58
juergbiraoul: yes, I took a look earlier but I'm not sure yet about the 2 config options15:59
juergbiit doesn't seem to be ideal but I don't have a better suggestion otoh15:59
raoulyeah it's a bit more cumbersome than I'd like but seemed better imo than extended the dependency scope16:00
raoulIf anyone else can think of a better way to do it, it'd be appreciated!16:01
BeckyWSalmon ah thanks16:01
*** phildawson_ has quit IRC16:08
*** phildawson_ has joined #buildstream16:08
benschuberttristan: I have https://gitlab.com/BuildStream/buildstream/merge_requests/1424, https://gitlab.com/BuildStream/buildstream/merge_requests/1425, and https://gitlab.com/BuildStream/buildstream/merge_requests/1426 for followups already (much shorter :D)16:09
*** phildawson_ has quit IRC16:10
*** phildawson has joined #buildstream16:11
WSalmonjuergbi, after way to much flaffing i have https://gitlab.com/BuildStream/buildstream/merge_requests/142916:15
gitlab-br-botraoul.hidalgocharman approved MR !1427 (juerg/source-checkout->master: Fetch sources as needed for bst source checkout) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/142716:15
*** lachlan has joined #buildstream16:16
gitlab-br-bottpollard approved MR !1427 (juerg/source-checkout->master: Fetch sources as needed for bst source checkout) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/142716:18
*** lachlan has quit IRC16:20
gitlab-br-botmarge-bot123 closed issue #915 (Artifact As A Proto: Capabilities Service) on buildstream https://gitlab.com/BuildStream/buildstream/issues/91516:32
*** raoul has quit IRC16:46
*** lachlan has joined #buildstream16:48
*** alexandrufazakas has quit IRC16:49
*** lachlan has quit IRC16:53
*** lachlan has joined #buildstream16:55
*** slaf has quit IRC17:00
*** slaf has joined #buildstream17:01
*** slaf has joined #buildstream17:01
*** slaf has joined #buildstream17:01
*** slaf has joined #buildstream17:01
*** tpollard has quit IRC17:05
*** tpollard has joined #buildstream17:05
*** slaf has quit IRC17:13
*** phildawson has quit IRC17:22
gitlab-br-bottlater opened MR !1431 (tar-target-renaming->master: tar.py: Make link target renaming work between base-dirs) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/143117:26
*** johnward has quit IRC17:47
*** johnward has joined #buildstream17:48
*** benbrown has quit IRC17:50
*** paulsherwood has quit IRC17:51
*** Becky has quit IRC17:51
*** ikerperez has quit IRC17:51
*** adds68 has quit IRC17:51
*** samkirkham has quit IRC17:51
*** samkirkham has joined #buildstream17:51
*** ikerperez has joined #buildstream17:51
*** adds68 has joined #buildstream17:51
*** Becky has joined #buildstream17:51
*** benbrown has joined #buildstream17:52
*** paulsherwood has joined #buildstream17:52
*** jonathanmaw has quit IRC18:09
*** lachlan has quit IRC18:19
*** ironfoot has quit IRC18:21
*** ironfoot has joined #buildstream18:22
*** ChanServ sets mode: +o ironfoot18:22
*** lachlan has joined #buildstream18:42
*** lachlan has quit IRC18:47
*** lachlan has joined #buildstream19:11
*** lachlan has quit IRC19:23
*** slaf has joined #buildstream20:39
*** slaf has joined #buildstream20:39
*** slaf has joined #buildstream20:39
*** slaf has joined #buildstream20:40
*** slaf has joined #buildstream20:40
*** slaf has joined #buildstream20:40
*** slaf has joined #buildstream20:40
*** slaf has joined #buildstream20:41
*** slaf has joined #buildstream20:41
*** slaf has joined #buildstream20:41

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