IRC logs for #buildstream for Thursday, 2020-05-21

*** mohan43u_ has quit IRC00:20
*** mohan43u_ has joined #buildstream00:24
*** mohan43u_ is now known as mohan43u00:26
*** mohan43u has joined #buildstream00:26
*** mohan43u has quit IRC00:38
*** mohan43u has joined #buildstream02:06
*** tristan has quit IRC02:55
*** tristan has joined #buildstream03:19
*** aminbegood has quit IRC03:49
*** tristan has quit IRC04:56
*** traveltissues has quit IRC05:39
*** traveltissues has joined #buildstream05:39
*** benschubert has joined #buildstream07:18
*** tristan has joined #buildstream07:26
*** ChanServ sets mode: +o tristan07:27
*** jude has joined #buildstream07:39
*** tpollard has joined #buildstream08:03
*** mohan43u has quit IRC08:19
*** mohan43u has joined #buildstream08:19
*** santi has joined #buildstream08:51
*** mohan43u has quit IRC09:39
*** aminbegood has joined #buildstream10:30
*** aminbegood has quit IRC10:35
*** santi has quit IRC10:54
*** santi has joined #buildstream10:54
*** santi has quit IRC11:06
*** santi has joined #buildstream11:06
*** santi has quit IRC11:10
*** santi has joined #buildstream11:10
*** santi has quit IRC11:12
*** santi has joined #buildstream11:15
gitlab-br-bottristanvb opened MR !1935 (tristan/junction-plugin-origin->master: Introduce new `junction` plugin origin) on buildstream https://gitlab.com/BuildStream/buildstream/-/merge_requests/193511:56
tristanbenschubert, if you could benchmark !1935 at this point that would be great... it's also ready for review \o/11:57
traveltissueshas anyone had the following issue when running a build: "Error loading user configuration: /usr/local/lib/python3.7/dist-packages/buildstream/data/userconfig.yaml: Severely malformed YAML:11:59
traveltissues'NoneType' object is not callable11:59
traveltissues"11:59
traveltissuesthis was from a pip install of 1.93.3.dev012:00
valentindtristan, for the includes, there is an issue with order of processing (?) vs (@). The issue is because we need to process (?) nodes before we merge includes together. Otherwise some of the (?) nodes disappear. There are two solutions. 1) Either we make the process of (@) call the process of (?) every time it sees such a node. 2) Or we tweak _yaml.composite so that (?) nodes are always merged.12:01
valentindI would prefer 1), which would force us to move all options definitions in project.conf. But at least it makes behavior always the same, because we already have to process (?) during process of (@) for files from junctions.12:02
tristanHmmm12:05
tristanvalentind, So here is my first conundrum: I dislike the idea of allowing project options being declared anywhere outside of project.conf anyway... But, this would be a blatantly breaking change for bst-112:06
valentindIt is already not possible to load options through junction.12:07
valentindSo we would not break much.12:07
tristanthe backport is a "technically breaking change" however goes with the presumption that; you couldn't really have been relying on the already broken behavior and getting away with it in the first place12:07
tristanit would break in any case that some person decided they wanted to store the options in a separate file12:07
valentindYes.12:07
tristanwhich I think we don't know the scale of12:07
valentindWell, the other option is to have "options.conf"12:08
valentindWhich is seperate and not included.12:08
valentindBecause we cannot really process any nodes on that. It is kind of special.12:08
tristanHow is that an option for bst-1 ?12:08
valentindIf someone really wants a separate file, then it can be done.12:09
valentindBut it is a fixed name.12:09
tristanvalentind, I think we need to do this in a way that doesn't break any existing projects in bst-1, and however we feel is the best way in bst-212:09
tristanhaving options.conf and forcing a change: Is a bad break12:09
valentindI do not think we have to add this possibility. Just that if we find out some people want it, we can add that in the future.12:09
valentindoptions.conf would be optional.12:10
tristanSo you mean in bst-212:10
tristanSure we could have that option if it ever becomes desirable to people, but I think we would be happy to just disallow it12:10
valentindtristan, OK, I will try to see if I can make something that tries to load options from includes for bst-1.12:11
valentindI can just add a 3rd pass.12:11
valentindBut maybe not for bst-212:11
tristanThings getting hairy haha12:11
valentindYes,  but I do not think it is that difficult. But we should not have it in bst-2, because it makes things a bit harder to maintain.12:12
tristanYeah I mean, lets aim for a clean maintainable codebase for bst-2, and in bst-1 lets aim for compatibility12:12
benschuberttristan: will try to have a look tomorrow12:12
tristanbenschubert, thanks !12:12
benschuberttraveltissues: try pip install --reinstall ruamel.clib12:12
traveltissuesthanks12:13
* tristan flees the scene of the crime...12:13
valentindtristan, OK, for now I do some changes on bst-1 to try to get gnome build meta to include stuff. Then when I have something I will make merge requests.12:13
tristanvalentind, thanks :D12:13
traveltissuesis there a missing dependency constraint in the setup or someway to avoid this when reinstalling benschubert12:13
benschuberttraveltissues: it's not a missing dependency, it should work, but I found out that sometimes, ruamel.yaml.clib installs an empty package instead of itself12:14
traveltissuesnice12:14
benschubertand ruamel is in kind of a bad shapre currently, and has moved to sourceforge, which makes contributing kind of hard :'D12:14
benschubertthe root cause I think is that it tries to compile itself before building (yes...) and does it in an incorrect way, leading it to break, and it catches that and then installs an empty package instead12:15
traveltissuesis there an alternative we could use12:15
benschubertpyyaml is deprecated12:16
benschubertand there is nothing else in the scope12:16
traveltissuesright, i recall now12:16
benschubertI'd almost be tempted to rewrite what we need, but the track ability to rewrite would be annoying so I'd rather not12:16
*** tristan has quit IRC12:16
*** tpreston has joined #buildstream12:20
*** mohan43u has joined #buildstream12:20
robjhwhats the command to have buildstream retry failures again?12:25
robjhbuildbox is being unstable12:25
robjhfound it, its bst artifact delete blabla.bst12:31
*** mohan43u has quit IRC12:38
*** mohan43u has joined #buildstream12:42
*** mohan43u has quit IRC13:00
*** mohan43u has joined #buildstream13:03
*** mohan43u has quit IRC13:05
*** mohan43u has joined #buildstream13:07
*** mohan43u has quit IRC13:18
*** mohan43u has joined #buildstream13:18
*** mohan43u has quit IRC13:24
*** mohan43u has joined #buildstream13:33
*** narispo has quit IRC14:07
*** narispo has joined #buildstream14:07
*** narispo has quit IRC14:10
*** narispo has joined #buildstream14:11
*** narispo has quit IRC14:28
*** narispo has joined #buildstream14:28
*** narispo has quit IRC14:37
*** narispo has joined #buildstream14:37
*** hasebastian has joined #buildstream14:41
*** santix has joined #buildstream14:49
*** santi has quit IRC14:50
WSalmonbenschubert, juergbi https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/jobs/562446406 this looks like some vars are still not getting updated..14:53
WSalmonim not user if something needs updating in FD or if the Variable updating MR fixes are still missing something14:54
WSalmonim not sure if something needs updating in FD or if the Variable updating MR fixes are still missing something14:54
WSalmoninstall-info: %{infodir}/dir: could not read (No such file or directory) and could not create (No such file or directory)14:55
WSalmonim not sure if the var should have been resolved in that log or if its meant to look like that14:56
traveltissuescan i have a review on https://gitlab.com/BuildStream/bst-plugins-experimental/-/merge_requests/111 please14:59
*** narispo has quit IRC15:05
*** narispo has joined #buildstream15:05
*** hasebastian has quit IRC15:26
*** narispo has quit IRC15:35
WSalmontraveltissues, a more verbose discription would not go amiss ether15:37
WSalmonsome times juergbi etc link to archive of this chanels IRC, can some one point me at it and is it for all gnome irc channels?15:50
tpollardhttps://irclogs.baserock.org/buildstream15:51
tpollardnope, brlogger is doing it for us :)15:51
* tpollard pats the robot15:52
WSalmonah, is there a way to ask what channels are there ? https://irclogs.baserock.org just gose to #baserock15:52
tpollardnot sure, ironfoot might know?15:53
ironfootno easy way, no, but I can tell you15:54
WSalmon#gnome-os15:54
WSalmondudno if it dont like the slash or its not there15:55
ironfootnah, it's not there15:56
ironfoothttps://gitlab.com/baserock/infrastructure/-/blob/master/baserock_webserver/irclogs/irclogs-generation.service15:56
ironfoot^ please don't scream when seeing that service file15:56
WSalmonthanks ironfoot16:00
WSalmonim sure i have seen worce16:00
*** tristan has joined #buildstream16:27
*** Riley7591 has joined #buildstream17:06
*** Riley7591 has quit IRC17:07
*** tpollard has quit IRC17:19
*** santix has quit IRC17:49
*** radiofree has joined #buildstream18:28
*** toscalix has joined #buildstream18:44
*** tpreston has quit IRC18:55
*** narispo has joined #buildstream19:21
*** tpreston has joined #buildstream19:33
*** tpreston has quit IRC19:36
*** Hannah9599 has joined #buildstream19:48
*** Hannah9599 has quit IRC19:49
*** finnb has quit IRC20:30
*** finnb has joined #buildstream20:30
*** benschubert has quit IRC21:08
*** jude has quit IRC21:39
*** toscalix has quit IRC22:18

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