IRC logs for #buildstream for Friday, 2018-06-22

*** tristan has quit IRC00:12
*** Prince781 has joined #buildstream00:15
*** toscalix has joined #buildstream01:37
*** Prince781 has quit IRC01:44
gitlab-br-botbuildstream: issue #301 ("Fix circular imports") changed state ("closed") https://gitlab.com/BuildStream/buildstream/issues/30102:19
*** Prince781 has joined #buildstream02:46
*** mohan43u has joined #buildstream02:57
*** toscalix has quit IRC03:09
*** tristan has joined #buildstream03:10
*** Prince781 has quit IRC05:18
*** tristan has quit IRC06:26
*** Trevinho has quit IRC06:28
*** Trevinho has joined #buildstream06:29
*** ernestask has joined #buildstream06:36
*** toscalix has joined #buildstream07:30
*** toscalix has quit IRC07:46
*** coldtom has joined #buildstream07:57
*** Phil has joined #buildstream08:06
jmacGrr, GitLab's issue interface is unusable on my laptop screen08:06
gitlab-br-botbuildstream: merge request (138-aborting-bst-push-command-causes-stack-trace-3->master: WIP: Resolve "aborting bst push command causes stack trace") #514 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/51408:21
gitlab-br-botbuildstream: merge request (138-aborting-bst-push-command-causes-stack-trace-3->master: WIP: Resolve "aborting bst push command causes stack trace") #514 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/51408:25
gitlab-br-botbuildstream: merge request (valentindavid/331_include->master: WIP: Add support for include in project.conf) #471 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/47108:29
*** slaf has quit IRC08:35
*** slaf has joined #buildstream08:37
*** slaf has joined #buildstream08:37
*** slaf has joined #buildstream08:37
*** slaf has joined #buildstream08:37
laurencecoldtom, thanks for the recent MR :)08:37
laurencecould you add an avatar onto gitlab?08:38
laurencehelps identifying people08:38
*** slaf has joined #buildstream08:38
*** slaf has joined #buildstream08:38
*** slaf has joined #buildstream08:38
*** bethw has joined #buildstream08:38
*** slaf has joined #buildstream08:38
*** slaf has joined #buildstream08:39
*** slaf has joined #buildstream08:39
*** jonathanmaw has joined #buildstream08:39
*** slaf has joined #buildstream08:39
*** slaf has joined #buildstream08:40
paulsherwoodis buildgrid a real thing yet?08:41
paulsherwoodif so is there documentation somewhere?08:41
jmacYes, https://gitlab.com/BuildGrid/buildgrid08:42
jmacfinn is the maintainer08:42
paulsherwoodsuper thanks08:45
laurenceWe are due another announcement to the Buildstream and BuildFarm ML actually08:46
laurencefinn_, do you want to do it ?08:46
finn_I'll announce later today after The Great Restructure08:47
*** finn_ is now known as finn08:48
laurencefinn, I committed straight to master yesterday when fixing the CONTRIBUTING.rst doc08:53
laurenceso i think we need to re-look at gitlab permissions08:54
finnCould be because you have owner permissions08:56
finnmaster is a protected branch for which Maintainers are allowed to push / merge08:57
gitlab-br-botbuildstream: merge request (phil/203-BuildStream-crashes-when-dependency-tree-too-deep->master: WIP: Phil/203 build stream crashes when dependency tree too deep) #512 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/51209:04
tlaterjmac: To scroll through the right, abuse text selection by selecting something and dragging your mouse to continue the selection09:26
* tlater also dislikes this09:26
jmacYeesh09:27
coldtomthe source for the autotools example/tests is currently giving a 50309:43
gitlab-br-botbuildstream: issue #434 ("Add documentation on workspaces") changed state ("closed") https://gitlab.com/BuildStream/buildstream/issues/43409:50
jmaccoldtom: Which URL is that?09:53
Philjmac, it's gnome7.codethink.co.uk09:54
jmacNot familiar with that09:55
coldtomyup that's the one09:56
tlaterjmac: It's where we host some tarballs...10:23
tlaterAlso I believe the gnome-modulesets conversion used to be written into that10:23
jmacOK, thanks. Has anyone reported it to Codethink? I can do so if need be10:24
tlaterjmac: That would be handy10:26
tlaterI think our test suite will fail for most of the day otherwise10:26
laurencejmac, i think jjardon is in talks with Codethink Ops about this already...10:26
laurencejjardon, ?? or is that another issue re struggling to access the moonshots?10:27
jmacOK then10:27
gitlab-br-botbuildstream: merge request (reduce_history_in_cache->master: Reduce history in cache) #482 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/48210:28
jjardonLaurence not about that, no10:28
*** dominic has joined #buildstream10:31
*** dominic has quit IRC10:31
laurencejjardon, ok thanks10:40
laurencejennis, i think i have missed some irc conversation here, so will just ask: did we agree that migrating the examples from the examples repo to the main repo makes sense?10:46
jennisYes, it's what we ultimately want to do as they will fit nicely into the new doc structure, and the projects themselves can live under doc/examples in the main repo10:47
persiaIf we do that, we should be sure to create a build process that can easily exclude them (or segment them as docs) to ease installs for folk not running from the git repo10:47
persiaThat works :)10:47
jennis:)10:48
jennishowever, as it currently stands, the projects themselves in the buildstream-examples repo do not actually build... so that needs to be fixed first10:48
laurencejennis, cheers10:49
gitlab-br-botbuildstream: issue #438 ("Migrate X86 image example from examples repo to main repo") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/43810:56
gitlab-br-botbuildstream: issue #439 ("Migrate Netsurf example from examples repo to main repo") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/43910:57
jmacWe have a Netsurf example? Cool.10:57
paulsherwood"on BuilStream internals."10:58
gitlab-br-botbuildstream: merge request (ps-fix-typo->master: Fix BuilStream typo) #515 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/51511:10
tlaterlaurence: I updated #438, it now lists the entire task breakdown. Sorry, been carrying this around in my mind.11:15
tlaterCan't comment much on what's missing for #439, sssam wrote that example. I suspect it's just a case of reformatting it, though.11:16
*** aday has quit IRC11:18
*** aday has joined #buildstream11:19
gitlab-br-botbuildstream: merge request (ps-fix-typo->master: Fix BuilStream typo) #515 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/51511:20
*** bethw has quit IRC11:22
gitlab-br-botbuildstream: merge request (ps-fix-typo->master: Fix BuilStream typo) #515 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/51511:28
* paulsherwood fixes a one-char typo, then sees the CI pipeline fail on multiple OSes... what kind of shonky project is this? :)11:40
laurencetlater, thanks a lot!12:07
laurencetlater, there's also the summary that's required for `bst shell` should be able to stage the specified element on top of a base element - https://gitlab.com/BuildStream/buildstream/issues/42212:08
laurencesorry, i am nagging now, but let's capture it whilst it's fresh12:08
tlaterpaulsherwood: Our server that hosts test data is down12:09
* tlater is pretty annoyed as well :|12:09
tlaterlaurence: Planning to write that this afternoon, it takes a bit more thought to express properly12:10
laurencecool12:18
laurencethanks!12:19
*** ernestask has quit IRC12:35
*** bethw has joined #buildstream12:42
*** toscalix has joined #buildstream12:58
toscalixjjardon[m]: around?12:59
jjardontoscalix: yes12:59
toscalixI wrote again to the organisers of GUADEC12:59
toscalixI just saw that the rooms have been taken but I did not received any response13:00
toscalixI do not know what to do if they not answer me13:00
toscalixdo you have any contact I can ping directly?13:00
toscalixlooking at the wiki, the only available slots for our hackfest is wednesday13:00
jjardon#guadec in irc.gnome.org ? who did you email? maube you can CC me?13:01
toscalixI just did13:02
toscalixCC you13:02
jjardontoscalix: did you read https://wiki.gnome.org/GUADEC/2018/Hacking%20days ? Seems you simply have to add you BOF there13:02
jmacThanks for the email finn_13:03
jmacBTW, I'm working with bazel-buildfarm at the moment to see if we can get it to work with Buildgrid, so should be able to do a review13:03
noisecellfinn, in the README on https://gitlab.com/BuildGrid/buildgrid "BuildGrid is a python remote execution service which implements the Remote Execution API and the Remote Workers API." both links points to the same place "Remote Workers API" file -13:08
toscalixjjardon: will try to add it myself then13:09
finnta, shall correct13:09
toscalixit will need to be on monday and wednesday13:10
toscalixmornings13:10
toscalixI would like to avoid wednesday afternoon13:10
toscalixjjardon: I am editing directly the wiki13:17
toscalixshould we use the monday morning for sync up with the release team and gnome devs and wed morning for hacking on BuildStream?13:17
*** finn has quit IRC13:30
tlaterNB ALL: gnome7 is back up, your CI should now happily pass again :)13:33
Phil\o/13:33
*** Sebastian has joined #buildstream13:33
tlatertristan (whenever you appear): *only* the IP address of gnome7 has been changed, any other pending configuration is left for you to complete.13:33
*** Sebastian has quit IRC13:37
*** finn has joined #buildstream13:59
*** aday has quit IRC14:05
*** ernestask has joined #buildstream14:14
*** sstriker has joined #buildstream14:16
*** aday has joined #buildstream14:31
*** toscalix has quit IRC14:34
*** aday has quit IRC14:37
*** aday has joined #buildstream14:38
*** aday has quit IRC14:42
*** aday has joined #buildstream14:42
laurencefinn, have you had a poke around the API since it's been on github?14:47
laurencehttps://github.com/bazelbuild/remote-apis/14:47
laurencewondering if the worker API is in there too14:47
laurenceor it's just the remote execution14:48
finnThat's just the remote execution api14:49
finnI am now wondering why the worker isn't in there too14:49
laurenceseems odd that the workers API is still on a google doc14:49
laurenceaye14:49
laurencenoisecell, links fixed now, thanks14:52
gitlab-br-botbuildstream: issue #430 ("BuildStream.doap is incorrectly included in MANIFEST.in") changed state ("closed") https://gitlab.com/BuildStream/buildstream/issues/43015:14
gitlab-br-botbuildstream: issue #430 ("BuildStream.doap is incorrectly included in MANIFEST.in") changed state ("closed") https://gitlab.com/BuildStream/buildstream/issues/43015:14
gitlab-br-botbuildstream: merge request (430-buildstream-doap-is-incorrectly-included-in-manifest-in->master: Resolve "BuildStream.doap is incorrectly included in MANIFEST.in") #508 changed state ("merged"): https://gitlab.com/BuildStream/buildstream/merge_requests/50815:14
*** tristan has joined #buildstream15:23
*** Prince781 has joined #buildstream15:30
tristanvalentind, are you still around ? I think we had to catch up on includes but yesterday around this time I was busy with Nexus ...15:33
gitlab-br-botbuildstream: merge request (ps-fix-typo->master: Fix BuilStream typo) #515 changed state ("closed"): https://gitlab.com/BuildStream/buildstream/merge_requests/51515:44
valentindtristan, I was also busy yesterday.15:46
valentindSo, this is about this separation of the plugin configuration code from Project class.15:47
valentindThe reason we have to extract it is that because we now have 2 configurations for the plugins. One before includes are processed. One after.15:48
valentindAnd the reason we have two configurations instead of updating configuration is to make sure that junctions are always interpreted the same way.15:49
valentindSo that a source plugin used in a junction becomes different whether you use the junction or not for finding include files.15:50
tristanAh here we are15:56
gitlab-br-botbuildstream: issue #440 ("Should we implement a (remote) CAS-based SourceCache?") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/44015:57
*** Sebastian has joined #buildstream15:58
tristanvalentind, soooooo from what I understand... you reinstantiate junctions ?15:58
valentindtristan, No.15:58
valentindI do not. That is the point.15:58
valentindI have only one instance of it.15:58
tristanhehe15:58
tristanyou reinstantiate the sources ?15:59
tristanof the junctions ?15:59
valentindBut for that, it means we always need to load it like the project.conf was incomplete.15:59
valentindYes, we have several instance of the plugins.15:59
tristanI see what you mean, I think15:59
valentindAt least the ones used in by junctions.15:59
tristanWhat I have in mind, is that we load everything at once and let the includes "float", and do composition in a later pass16:00
tristans/have/had16:00
tristanbut16:00
tristanI think you are pointing out that is not really possible, at least: It is impossible to use an include to configure a junction source16:00
*** Phil has quit IRC16:01
valentindI think it is not possible right.16:01
valentindAlso there would be so many corner cases.16:01
*** Sebastian has quit IRC16:01
tristanThere are a few ugly edge cases, one thing I wanted to test for is that `bst track` correctly updates the included file which was used to configure the associated Source16:01
tristanbut that has to trigger an error in the case that you include a cross-junction file to configure your source16:02
valentindtristan, Can you describe the case, I can write a test for it.16:02
*** Sebastian has joined #buildstream16:02
valentindYes. so there are things like a junction needing a configuration from another junction, the problem is that we have no way to know the order of loading.16:02
valentindSo, the best is to say for now, it is not possible.16:03
valentindAnd because include is a new feature, we have the right to restrict inclusion for junctions.16:03
tristanThis is true, well; I was thinking about making include illegal in `project.refs`16:04
tristanvalentind, if we say that include is illegal for a junction element, and illegal for `project.refs`, is it allowed everywhere else ?16:07
* tristan has to refresh his memory on the patch itself now16:08
tristanright, I didnt like how we are creating new high level Source/Element thingies again, for plugins16:08
valentindYes. I think it should be fine.16:08
valentindI have not seen in the code any other case that was tricky.16:09
tristanThere is some precedent for sharing project loading codepaths16:09
tristanproject hands off some loading stuff to the artifact cache16:09
tristannot necessarily that it's a good thing16:09
valentindI am not sure what you mean here.16:11
valentindYour objection was about this new class for loading plugin configurations. Which was legitimate. But I want you to see the reason behind. Because what you asked for, I am not sure it would work for what we need.16:13
valentindWe need to have 2 sets of plugin configuration.16:13
*** Sebastian has quit IRC16:17
tristanRight16:18
tristanvalentind, if we added that in PluginContext once, we'd have already two instances of that16:18
*** Sebastian has joined #buildstream16:18
tristanvalentind, well two instances for each project, actually16:18
tristanthere is on ElementFactory and one SourceFactory for each loaded project16:19
valentindtristan, OK, I can try that. I will see if it works.16:19
valentindI think there was some downsides. But I do not remember. I think the best is for me to try it and see how it looks.16:19
valentindSo we would have 2 ElementFactory and 2 SourceFactory in a project.16:20
tristanWould we ? ok hold on a second16:20
valentindAnyway, I already have a class for duplicated fields.16:20
* tristan rereads, it's early16:20
valentindWell. We do not need 2 ElementFactory.16:21
valentindBut we do need 2 SourceFactory.16:21
*** Sebastian has quit IRC16:21
tristanAha I see16:22
valentindAh yes. We do need to load the junction plugin with the other ElementFactory.16:22
tristanright, 2 configurations16:22
valentindOne with includes. One without.16:22
tristanWhen do we resolve project includes ?16:22
*** Sebastian has joined #buildstream16:23
valentindIt is in Project._load16:24
valentindWe have two pass.16:24
*** finn has quit IRC16:26
*** sstriker has quit IRC16:26
*** bethw has quit IRC16:28
*** finn has joined #buildstream16:32
*** ernestask has quit IRC16:35
*** aday has quit IRC16:36
gitlab-br-botbuildstream: issue #418 ("Should we use a CAS-based source cache as a mirror?") changed state ("closed") https://gitlab.com/BuildStream/buildstream/issues/41816:41
tristanvalentind, error handling looks clever16:45
tristanSo, we're squeezing validation through, but is that really required ?16:45
tristanit should not be16:45
tristanvalentind, is it late for you ?16:45
tristanI can do more comments on the issue at this point I think16:45
valentindIt is a bit. But it is fine. But now you got what I meant, I think you can write the comments on the MR. I will look at them later.16:46
tristanI think that we don't need that cleverness of validating within the includes16:46
tristanThe way it's supposed to work:16:46
valentindI think you are right, we could delay validation. Though we do interpret options. So it should work.16:46
tristan o Blind dictionary composition16:47
tristan o Validation and _yaml.node_get()16:47
tristan o When an error occurs, use the associated Provenance object16:47
valentindWhat do you mean by blind?16:47
tristanThe Provenance object should show that the undesired value comes from the file/line/col it was introduced at16:48
tiagoI am getting a "/home/tiagogomes/buildstream/doc/source/buildstream.sandbox.rst:document isn't included in any toctree" error when trying to build the documentation. Is this a known issue?16:48
*** tiago is now known as tiagogomes16:48
tristanvalentind, I mean, not blind but; without caring about the details of validating them one by one :)16:48
valentindOh OK. I can remove some of the validation.16:48
tristanvalentind, so we only validate once (and probably change a bit less code, as the validations stay where they approximately were)16:49
tristanI think the principal of Provenance object is sound and we've been relying on it; the thing might have bugs but... mostly it's working16:49
tristanthere is a case where it needs interaction to tell it a specific file, I think that case is when something is expected but not found16:50
valentindtristan, OK. Just add that the MR. I will soon go to the store. Will be back in 1h30. I can read the comments and then talk to you if there are any other issue I want to discuss.16:50
tristanok ok16:50
tristanvalentind, I'm not sure about having to change that project plugin collection thing, lemme look a bit deeper16:51
*** aday has joined #buildstream16:52
*** jonathanmaw has quit IRC16:59
*** coldtom has quit IRC16:59
gitlab-br-botbuildstream: merge request (jjardon/host_deps->master: Document BuildStream's plugins host packages dependencies) #495 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/49517:01
gitlab-br-botbuildstream: merge request (tristan/host-deps->master: Rebase and fixup Javier's host dependency docs branch !495) #516 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/51617:10
gitlab-br-botbuildstream: merge request (jjardon/host_deps->master: Document BuildStream's plugins host packages dependencies) #495 changed state ("closed"): https://gitlab.com/BuildStream/buildstream/merge_requests/49517:12
*** tiagogomes has quit IRC17:19
*** Sebastian has quit IRC17:40
gitlab-br-botbuildstream: merge request (tristan/host-deps->master: Rebase and fixup Javier's host dependency docs branch !495) #516 changed state ("merged"): https://gitlab.com/BuildStream/buildstream/merge_requests/51617:50
*** aday has quit IRC19:07
*** tristan has quit IRC19:44
*** bethw has joined #buildstream20:07
*** bethw has quit IRC20:09

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