IRC logs for #buildstream for Wednesday, 2018-02-14

*** mcatanzaro has joined #buildstream00:01
*** tristan has quit IRC00:08
*** Prince781 has quit IRC00:11
*** Prince781 has joined #buildstream01:12
*** mcatanzaro has quit IRC05:24
*** Prince781 has quit IRC06:53
*** valentind has joined #buildstream08:30
*** dominic has joined #buildstream08:33
*** Prince781 has joined #buildstream08:45
*** tristan has joined #buildstream08:50
*** aday has joined #buildstream08:59
*** valentind has quit IRC09:05
*** toscalix has joined #buildstream09:12
*** ernestask has joined #buildstream09:19
*** Prince781 has quit IRC09:23
*** ssam2 has joined #buildstream10:00
*** jonathanmaw has joined #buildstream10:05
ssam2I had a go at sketching out a BuildStream quick start guide: https://wiki.gnome.org/SamThursfield/BuildStreamQuickStart10:43
ssam2feedback welcome, although i don't guarantee spending more time on it myself10:44
ssam2but i had some ideas about how to structure it and such that i wanted to get out of my head :-)10:45
jmacLooks good, I'll have a proper read through later10:46
aidenwhy `bst` and not `bs`?10:47
ssam2LOL10:47
aiden`bs` might stick a bit more10:47
ssam2'bs' has some ... negative connotations10:48
persiaaiden: Unfortunate connotations to "bs", also memetic heritage encouraging three letter filename extensions.10:48
aiden`git` also has negative connotations10:48
skullmanless negative than `bs`10:48
persiaYes, but the author of git is famous for not caring if other folk are offended.  That luxury does not apply to most folk.10:49
jmac"bst" conjures up images of long summer evenings if you're in Britain10:50
nexusthat was the name i gave to my remote for a while :p10:50
*** theawless[m] has joined #buildstream10:50
tristanI came up with the BST_ namespaced inspired from gstreamer and GST_ fwiw; it seems that only my close colleagues on this project had ever thought up `bs`, aiden gets an award :)10:50
aidenit would make me smile if i had to type `bs` more than `bst`10:51
aidenjust saying10:52
tristanheh10:52
gitlab-br-botbuildstream: merge request (image-authoring->master: WIP: Image authoring documentation) #262 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/26211:30
gitlab-br-botbuildstream: merge request (image-authoring->master: WIP: Image authoring documentation) #262 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/26211:30
gitlab-br-botbuildstream: merge request (image-authoring->master: WIP: Image authoring documentation) #262 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/26211:30
*** jennis has quit IRC11:32
*** jennis has joined #buildstream11:34
gitlab-br-botbuildstream: merge request (buildproject->master: Added buildproject doc) #238 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/23811:36
*** toscalix has quit IRC11:44
*** toscalix has joined #buildstream11:45
gitlab-br-botbuildstream: merge request (image-authoring->master: WIP: Image authoring documentation) #262 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/26211:45
*** toscalix has quit IRC11:47
*** toscalix has joined #buildstream11:52
jmacHmm, where do I go with this error? https://paste.gnome.org/p9ibo5nln12:00
ssam2that's some error in variable resolution which isn't reported very clearly12:01
ssam2i imagine you used a variable that isn't defined in an element12:01
ssam2and buildstream reports the last place it looked for it, instead of where it actually came from12:01
ssam2i've had this before, but always been in too much of an excited rush to actually file an issue12:02
tristanoooh nice catch; that would be good to fix12:05
nexusjuergbi: ok, i've added the fix and written a test for it, going to push the MR shortly12:20
juergbigreat12:24
gitlab-br-botbuildstream: merge request (sam/plugin-error->master: _plugincontext.py: Fix unhandled exception if plugin is not found) #274 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/27412:28
gitlab-br-botbuildstream: merge request (issue-166_yaml_removing_underscores->master: WIP: Issue 166 yaml removing underscores) #245 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/24512:31
gitlab-br-botbuildstream: merge request (issue-166_yaml_removing_underscores->master: Issue 166 yaml removing underscores) #245 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/24512:34
gitlab-br-botbuildstream: merge request (issue-166_yaml_removing_underscores->master: Issue #166 yaml removing underscores) #245 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/24513:16
gitlab-br-botbuildstream: merge request (issue-166_yaml_removing_underscores->master: Issue #166 yaml removing underscores) #245 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/24513:16
gitlab-br-botbuildstream: merge request (issue-166_yaml_removing_underscores->master: Issue #166 yaml removing underscores) #245 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/24513:17
nexusjuergbi: i've updated my commit message and added the file. However my CI is still failing and is up to date with master13:29
juergbinexus: it still says '1 commit behind' here13:29
juergbiand the summary line of the commit message is still: This fixes #166 and adds tests13:30
gitlab-br-botbuildstream: merge request (issue-166_yaml_removing_underscores->master: Issue #166 yaml removing underscores) #245 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/24513:35
persianexus: I thought the new test in context.py was going to test fetchers: "twenty-two"14:04
persiaI also thought the 1.23.4 and 1_23_4 were going to be new tests in yaml.py14:05
*** tristan has quit IRC14:06
juergbii already commented on the MR14:07
persiaAnd your comments are much more in-depth and useful than mine :)14:10
juergbinexus: btw: i suggest using branches in the main repo in the future as that will use our CI runner which seems to be faster (and reliably uses a cache)14:10
*** tristan has joined #buildstream14:18
*** toscalix has quit IRC14:19
*** toscalix has joined #buildstream14:21
*** mcatanzaro has joined #buildstream14:29
nexusWhen implementing my tests, there is currently one that fails "string parsing for floats". Should i have this test skipped or have it as an expected failure, or have it expect 1.2 and not 1.20 (basically testing that it still doesn't work) <- not a fan of the last one14:36
nexusjuergbi:14:37
nexusjuergbi: i can't create branches in the main repo14:37
persianexus: Hrm?  What is the failure on parsing 1.20 as a string and getting 1.20 as a string?14:38
juergbinexus: i would suggest also fixing the float case at the same time. if it's more work than just adding add_constructor() for floats and you want to handle this as a separate merge request, i would move the float test also to that other MR14:39
nexuskk14:41
juergbinexus: i just added your user to the buildstream group. you can push new branches for future MRs14:41
nexuswoo \o/14:42
gitlab-br-botbuildstream: issue #253 ("Unhelpful error message on missing variables") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/25314:55
nexushm. that was easy14:57
nexusjuergbi: re: the functionality causes quotes to be added to the track value.15:05
nexusAs we discussed earlier today, would it not be nicer to keep this, and in the docs, encourage them to be used to prevent this issue, whilst allowing people to not do so without it breaking stability?15:05
nexusThis way, we can phase in the use of quotes for tracking values, without forcing the user to do so on existing projects15:05
juergbinexus: it does also convert double quotes to single quotes, though, afaict15:06
nexusdoes that matter?15:06
juergbimainly just about diff noise15:07
juergbinot sure how much of an inconvenience it would be in practice15:07
juergbiwe might need to check with tristan what he thinks about this15:07
nexuswouldn't it only happen once?15:07
nexuskk15:08
juergbiif the change is committed, yes15:08
juergbiwhich means that it might be ok in practice but i still think it's not ideal15:08
juergbii assume it will do this also for unrelated values, not just for track15:08
juergbiso it might be more than just one line15:09
juergbiyes, it will quote all values that could be interpreted as non-strings in the file15:11
juergbi(and change quotes to single where currently double quotes are used)15:12
juergbii would definitely check whether we can easily avoid this15:12
juergbiif it turns out to be a lot of work, we can re-evaluate15:12
ssam2we might as well just switch to https://github.com/imbal/safeyaml at that point15:13
nexusWouldn't it be bad to have to convert them every time? Wouldn't it be faster if they were all just read as strings initially?>15:13
juergbissam2: hm?15:14
ssam2for a computer to convert an integer to a string? that takes nanoseconds ...15:14
juergbinexus: with this MR, we do read them as strings15:14
juergbiit never even goes via integer15:14
nexusssam2: kk15:14
ssam2i mean, if we convert all non-string values to strings, we are starting to reimplement the "SafeYAML" subset of YAML documented at https://github.com/imbal/safeyaml15:14
juergbissam2: ah ok15:14
juergbiso i take it you're also in favor of fixing this issue15:15
ssam2which may be a good idea, but not something we should sneak in by the back door15:15
juergbiif this were pre-1.0 days, i'd say it makes sense to discuss this. now, i'd say it's too late unless we hit serious roadblocks with the current approach15:15
ssam2yes... i mean, `bst track` is still a neat thing, but also having computers and people editing the same file is a recipe for madness15:15
ssam2but if we are going to try to edit files the user wrote, we should do it properly, not decide to rewrite stuff for them in different ways15:16
nexussimple, lets just replace people with machines15:16
*** cs_shadow has joined #buildstream15:22
tristanssam2, agreed; diffs are "bad", and you might be surprised to know how many times I've received bugs along the lines of "Glade completely changed the .ui file I created by hand, bad bad diffs !!"15:34
tristanwhile I think in that context the expectation is unreasonable, it could totally be done and would be nice15:34
*** Prince781 has joined #buildstream15:49
*** dominic has quit IRC15:53
*** dominic has joined #buildstream15:53
persiassam2: Do we expect any yaml bahviours that are not implemented by SafeYAML?  Are SafeYAML dependencies small enough to be a sensible alternative to ruamel for us?15:56
ssam2SafeYAML is a subset of the YAML standard15:57
ssam2so yes, we expect behaviours that it doesn't implement15:57
ssam2or rather, explicitly forbids15:57
skullmanhaving had a quick look at the ruamel code, it should be possible to preserve quoting style so it doesn't get normalised to single quotes by passing preserve_quotes=True to ruamel.yaml.load15:59
juergbithe issue about failing to preserve the quoting style is already present in master. e.g., it removes quotes if they are not necessary16:05
juergbiso it wouldn't be a regression of !245 and i'd be fine handling this separately (if at all)16:06
juergbinexus: ^^16:06
* juergbi should rather add this to the MR16:06
gitlab-br-botbuildstream: merge request (212-git-source-needs-a-way-to-disable-checking-out-submodules->master: Resolve "Git source needs a way to disable checking out submodules") #259 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/25916:28
*** toscalix has quit IRC16:44
nexus15:59 <skullman > having had a quick look at the ruamel code, it should be possible to preserve quoting style so it doesn't get normalised to single quotes by passing preserve_quotes=True to ruamel.yaml.load17:07
nexusjuergbi: this worked17:07
juergbinice17:07
nexusyou happy for this to be pushed?17:08
juergbinexus: you haven't updated the branch yet, have you?17:14
juergbii'm certainly happy to add preserve_quotes in the same MR. although i would put it in a separate commit17:14
nexusno17:14
nexusok17:15
nexusis there an issue for this?17:17
ssam2this has been discussed to death so much that i know it from memory ...17:20
ssam2#16617:20
nexusi mean for preserving quotes :)17:30
juergbino, i don't think so17:30
*** valentind has joined #buildstream17:34
*** Prince781 has quit IRC17:40
*** tiago has quit IRC17:48
*** jonathanmaw has quit IRC17:56
*** jonathanmaw has joined #buildstream18:02
*** Prince781 has joined #buildstream18:07
*** jonathanmaw has quit IRC18:18
*** dominic has quit IRC18:33
*** ssam2 has quit IRC18:43
*** Prince781 has quit IRC18:49
*** ernestask has quit IRC20:49
*** mcatanzaro has quit IRC21:16
*** Prince781 has joined #buildstream22:29
*** valentind has quit IRC22:51
*** tristan has quit IRC23:29

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