IRC logs for #buildstream for Tuesday, 2018-04-03

*** jsgrant has joined #buildstream01:47
*** jsgrant has quit IRC02:34
*** jsgrant has joined #buildstream02:56
*** jsgrant has joined #buildstream02:57
*** jsgrant has quit IRC03:21
*** tristan has joined #buildstream05:17
*** tristan has quit IRC05:41
*** tristan has joined #buildstream05:55
*** jsgrant has joined #buildstream06:16
*** jsgrant has quit IRC06:53
*** tristan has quit IRC06:53
*** mohan43u has quit IRC07:06
*** mohan43u has joined #buildstream07:09
*** tristan has joined #buildstream07:17
*** noisecell has joined #buildstream07:23
*** toscalix has joined #buildstream07:57
*** bethw has joined #buildstream07:58
*** jonathanmaw has joined #buildstream08:02
*** tiago has joined #buildstream09:05
*** mohan43u has quit IRC09:05
*** tiago has quit IRC09:06
jennistristan, hi, renaming these rst files, do you think it's a good idea to have a directory structure in doc/source/ that reflects the ToC?09:08
*** mohan43u has joined #buildstream09:09
jennisSo for example, all that we have in doc/source/ is index.rst and index/09:09
jennisOr do you think it's better to keep all of the rst files in doc/source/ and give them long names reflecting where they belong09:10
*** tiago has joined #buildstream09:16
*** dominic has joined #buildstream09:24
*** toscalix has quit IRC09:54
*** valentind has quit IRC10:07
*** bethw has quit IRC11:04
*** toscalix has joined #buildstream11:29
*** aday has joined #buildstream11:35
*** toscalix has quit IRC11:41
*** tristan has quit IRC11:43
*** tristan has joined #buildstream11:46
*** bethw has joined #buildstream11:47
tristanjennis, I dont really mind either way, consistency would be nice to have; such that any section has a "word" which is used to prefix subsections of that section11:48
tristandirectories, or words with underscores, doesnt make much difference... maybe directories will be nicer11:48
tristanconsidering addition of examples11:49
jennisyeah and maybe directories will encourage devs to think about structure more11:50
jennisMy only concern about this directories approach: It's nice to simply have index.rst and index/ in the doc/source folder. However, if you're hacking and execute `make -C doc` you'll get all the buildstream.* files and a couple of extra directories11:52
*** toscalix has joined #buildstream11:53
tristanjennis, I dont understand what it means "you'll get all the buildstream.* files and a couple of extra directories"12:01
tristanjennis, if you build the docs, the docs will be built, into doc/build/html or smth, you will not "get" ... I dont know what the issue is12:03
*** toscalix has quit IRC12:41
jmacIf I'm making an artifact cache that serves over HTTP, should it be necessary to create a GPG key?12:42
jmacMy server is being repeatedly asked for /artifacts/summary.sig which doesn't exist atm12:43
tlaterjmac: Pretty sure it should be, if it wasn't you'd have a wide-open security hole12:45
tristanjmac, ostree will probably ask for it indeed, but we currently dont do anything for that12:45
tristantlater, no, we dont use that feature yet, it's known12:45
tristantlater, that's why we currently only recommend serving over https12:46
tlaterAh, fair enough12:46
tristanwe are looking into artifact signing, but will need to do so in an ostree agnostic way12:46
tristan(we *do* support GPG verification in the ostree source plugin, though)12:46
tristanIt's plausible that we need to file an issue and fix upstream to avoid requesting the summary.sig in the case that you are pulling from an ostree repo which is not configured to do GPG ostree-built-in validation12:47
tristanif that is any significant overhead12:48
jmacRight, I'll stick with https then12:48
jennistristan, this is what I meant: http://termbin.com/xefi13:08
tristanjennis, myeah... so ?13:10
tristanjennis, if you want something to inform your choice, an idea might be: "What is the easier thing to specify in .gitignore ?"13:10
jennisok thanks13:11
tristanjennis, I dont really have a specific preference, that's why I'm reaching for a practical reason :)13:14
*** xjuan has joined #buildstream13:24
*** sstriker has joined #buildstream13:53
*** tristan has quit IRC13:53
*** sstriker has quit IRC13:54
*** sstriker has joined #buildstream13:54
*** tristan has joined #buildstream14:02
*** ernestask has joined #buildstream14:02
*** dplayle has joined #buildstream14:03
*** dplayle has quit IRC14:04
*** toscalix has joined #buildstream14:06
Nexustristan: could i get a quick update from you about the workspace changes you've been making over the weekend pls?14:51
Nexusas i just rebased to find that the section of code i've been working on has been moved :)14:52
tristanNexus, in a bit of a meeting here... it has not changed drastically; it has moved from Pipeline -> App mostly14:52
tristanNexus, it was a lot of bloat for Pipeline, and some workspace operations do not require an instantiated Pipeline, hence the change14:53
* tlater hates how gitlab caches pipeline results on MR pages15:08
*** Prince781 has joined #buildstream15:11
*** Prince781 has quit IRC15:36
*** toscalix has quit IRC15:45
tristanNexus, regarding changes related to workspaces, asides from moving the higher level code to a new venue, there is only one change in the API contract15:55
tristanWhich is Workspaces() object, in _workspaces.py, now takes an element name, instead of an element, for looking up and deleting a workspace15:55
tristanThis is necessary to work with workspaces without instantiated elements15:56
*** toscalix has joined #buildstream15:56
tlaterAh, that does indeed sound nicer15:56
tristanironfoot, any chance you could slap the gitlab bot ? I think he's been sleeping :)15:56
ironfoottough easter :/15:56
tristantlater, yeah, it was a part of fixing that issue where you cant close a workspace if you're project doesnt have the element anymore15:57
*** Prince781 has joined #buildstream15:57
Nexustristan: i'm mostly having trouble finding and replacing all of the points where calls were changed. E.G. raise pipelineError() -> raise appError()15:58
Nexusand alike15:58
tristanactually the weekend refactors went really nicely, the two branches I landed, A.) improved things... B.) deleted roughly ~70 or ~80 LOC, and C.) Added a lot of comments (meaning, a lot more LLOC were actually removed)15:58
tlaterNexus: Shouldn't tristan's commit tell you that?15:58
Nexustlater: i have to go through line by line and compare them, because it was all done in a single commit15:59
Nexusas far as git knows, the entire thing is new code, not just the changes15:59
tlaterAh, too bad, are you sure git's interactive rebase doesn't help?16:00
tlaterUsually it's really good figuring this stuff out16:00
tristan19e31adb00f19f0789a3c4622150ca8f6e9c8901 is not immensely huge, but was done this way to retain the policy that every commit should build and pass tests16:00
tristanit is separated from earlier supporting commits which change how initialization of the application works16:01
tristanI suspect interactive rebase is not very helpful, I moved main.py -> app.py in an earlier commit conform with regular naming policy16:01
tristannow that that file actually just implements App()16:01
tristanhistory for git blame is retained, but I suspect it will fool git rebase; probably looking at the diffs you had before and applying them by hand to the new HEAD is safer16:02
tlaterHm, I'm getting random failures where files in about-to-be cached artifacts disappear before I can `stat` them16:04
tlaterThis CI has an example of that: https://gitlab.com/BuildStream/buildstream/-/jobs/6088767816:04
*** gitlab-br-bot has joined #buildstream16:06
juergbitristan: what's the reason for not using double underscores for local private symbols in private classes?16:06
*** Prince781 has quit IRC16:06
* juergbi thinks this would be more consistent16:07
juergbiand Python would enforce that it's not accessed from outside the same file16:07
tristanjuergbi, my feeling was that those are generally the outlier, python developers dont generally expect them, nor do they recommend their use16:07
tristanprincipal of least surprise I guess16:07
jjardon[m]Hi, is there a plugin/extension somewhere to generate rootfs? something similar to the tar extension in baserock? https://gitlab.com/baserock/definitions/blob/morphs/clusters/build-system-x86_64-chroot-deploy.morph16:08
*** dominic has quit IRC16:08
tristanjuergbi, they are not exactly pretty either, I think we're better off only using them where needed16:08
tristanjuergbi, note that while I have documented it as "a means of disambiguation", the underlying reason is actually different16:09
juergbitristan: ah, if that's what's considered best practice in Python, then it's fine with me16:09
tristanMostly, for public classes which can be derived in plugins/extensions, we want to free up namespace, so there is a technical reason16:09
tristanHowever, the way I have documented it, happens to satisfy that need at the same time as disambiguating16:10
* tristan is waiting for pipeline to complete to send the email, so that I can link to the page in the docs16:10
*** valentind has joined #buildstream16:11
tristanthe HACKING.rst is now literally included into the docs, thanks to jjardon[m] :)16:11
juergbiright, one leading underscore for non-public methods and two leading underscores to avoid name clashes with subclasses matches PEP816:12
tristanSo, it means Sandbox also gets that treatment, even though it is not publicly derived, it is still nice to disambiguate   A.) What is hidden from public API from   B.) What will really only be used in this file16:14
tristanI've handled the most hectic of files so far, which are my fault (i.e. making Project and Context private at the last moment before 1.0 stable)16:15
tristanand Pipeline(), which was just getting really messy16:15
tristanAnd also improved doc comments for methods all around16:15
tristana lot of house cleaning16:16
tristanmail sent16:20
gitlab-br-botbuildstream: merge request (135-expire-artifacts-in-local-cache->master: WIP: Resolve "Expire artifacts in local cache") #347 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/34716:29
tristanjjardon[m], not per se, there is an issue report lying around somewhere to implement a tar streaming output from `bst checkout`, though.16:31
*** noisecell has quit IRC16:31
gitlab-br-botbuildstream: merge request (135-expire-artifacts-in-local-cache->master: WIP: Resolve "Expire artifacts in local cache") #347 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/34716:32
jjardon[m]tristan: what would be the correct thing to do if I want to simply generate a rootfs? write and element that do a tarball of everything or a plugin to deploy? I'm trying to understand what would be the equivalent of baserock clusters in buildstream16:36
gitlab-br-botbuildstream: merge request (135-expire-artifacts-in-local-cache->master: WIP: Resolve "Expire artifacts in local cache") #347 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/34716:43
gitlab-br-botbuildstream: merge request (135-expire-artifacts-in-local-cache->master: WIP: Resolve "Expire artifacts in local cache") #347 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/34716:52
gitlab-br-botbuildstream: merge request (135-expire-artifacts-in-local-cache->master: WIP: Resolve "Expire artifacts in local cache") #347 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/34716:52
gitlab-br-botbuildstream: merge request (135-expire-artifacts-in-local-cache->master: WIP: Resolve "Expire artifacts in local cache") #347 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/34716:52
gitlab-br-botbuildstream: merge request (135-expire-artifacts-in-local-cache->master: WIP: Resolve "Expire artifacts in local cache") #347 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/34716:52
gitlab-br-botbuildstream: merge request (135-expire-artifacts-in-local-cache->master: WIP: Resolve "Expire artifacts in local cache") #347 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/34716:53
gitlab-br-botbuildstream: merge request (jmac/artifact_cache_error_message->master: Artifact cache: Mention the remote URL when we fail to fetch remote refs) #354 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/35416:57
*** dominic has joined #buildstream16:57
*** gitlab-br-bot has quit IRC16:59
*** gitlab-br-bot has joined #buildstream16:59
*** brlogger has joined #buildstream17:03
*** gitlab-br-bot has joined #buildstream17:03
*** bethw has quit IRC17:03
tristanjjardon[m], sorry it's late, just obtained food from the last closing restaurant (damn I wanted chicken ! but unavailable)17:05
tristanjjardon[m], it would be better IMO to implement that checkout feature, and avoid an extra step of generating a tarball inside BuildStream, to be honest17:06
tristanbut that could be a workaround for not having the feature17:06
tristanthe problem with using `bst checkout` directly and tarring the result, is you have the filesystem and user permissions to worry about (files in the tarball will not be owned by root, etc)17:07
*** jonathanmaw has quit IRC17:07
tristanif we have a proper `bst checkout --tar` or such, then we can generate the tar with exactly the right file permissions and attributes17:07
jjardon[m]rigth17:08
*** jsgrant has joined #buildstream17:11
*** solid_black has joined #buildstream17:27
*** aday has quit IRC17:27
*** jsgrant has quit IRC17:27
*** aday has joined #buildstream17:28
*** aday has quit IRC17:32
*** jsgrant has joined #buildstream17:32
*** aday has joined #buildstream17:33
*** solid_black has quit IRC17:34
*** dominic has quit IRC18:01
*** jsgrant has quit IRC18:01
*** aday has quit IRC18:12
*** toscalix has quit IRC18:22
*** slaf- has joined #buildstream18:28
*** slaf has quit IRC18:30
*** slaf- is now known as slaf18:30
*** xjuan has quit IRC20:01
*** Prince781 has joined #buildstream21:02
*** ernestask has quit IRC21:06
*** valentind has quit IRC21:40
*** Prince781 has quit IRC22:09
*** sstriker has quit IRC22:26
gitlab-br-botbuildstream: issue #336 ("Error when running bst --track in big projects: "BlockingIOError: [Errno 11] Resource temporarily unavailable: Exception ignored when trying to write to the signal wakeup fd:"") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/33623:25

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