IRC logs for #buildstream for Thursday, 2018-02-08

*** Prince781 has quit IRC00:43
*** mcatanzaro has joined #buildstream01:23
*** ruben has quit IRC01:47
*** classtime has joined #buildstream01:47
classtimeСНRОПО IS TEACHING A CLASS @ iяс.sцреяиетs.ояg сни sцреявоwl01:48
classtimemcatanzaro tristan nexus rafaelff[m]01:48
*** classtime has left #buildstream01:48
*** shitface has joined #buildstream03:00
*** shitface has quit IRC03:03
*** mcatanzaro has quit IRC06:20
gitlab-br-botbuildstream: issue #240 ("Make a release of BuildStream") changed state ("closed") https://gitlab.com/BuildStream/buildstream/issues/24006:27
*** Prince781 has joined #buildstream07:44
*** Prince781 has quit IRC07:49
*** Prince781 has joined #buildstream07:52
*** jonathanmaw has joined #buildstream09:39
*** toscalix has joined #buildstream09:40
*** tristan has quit IRC09:40
*** jonathanmaw has quit IRC09:51
*** jonathanmaw has joined #buildstream09:51
*** ssam2 has joined #buildstream09:54
*** aday has joined #buildstream10:28
*** tristan has joined #buildstream10:31
*** toscalix_ has joined #buildstream11:21
*** toscalix has quit IRC11:22
tlaterjonathanmaw: Could you have another look at the docker image MR? https://gitlab.com/BuildStream/bst-external/merge_requests/911:58
* tlater fixed the issue you were having11:58
jonathanmawtlater: cool11:58
*** zalupik has quit IRC12:17
tlaterAnyone mind if I create a buildstream-examples repo? jmac, I think you were interested in seeing one of these as well.12:32
jmacI am, please create it12:32
* tlater notices that the bst-external repo doesn't have a license12:45
ssam2oops12:45
ssam2I'm sure it should be the same as buildstream.git12:45
tlaterI'll license both that and the buildstream-examples as lgpl v2.112:46
jmacI now seem to be in a rabbit hole, finding dependencies for a python module, making .bst files for those, then repeating with the dependencies for those. Is there an easier way to do this?12:48
tlater(There's no way this affects anything, I'll just push to master)12:48
tlaterHrm, I guess we could have a nice pip-to-bst conversion tool that throws out a bunch of .bst files12:48
* tlater doesn't think there's a way currently, jmac 12:48
jmacI'm thinking of making such a tool just for this task12:49
ssam2there's no such tool for buildstream yet12:49
ssam2https://gitlab.com/baserock/import has a way of doing this12:49
ssam2https://gitlab.com/baserock/import/blob/master/baserockimport/exts/python.to_lorry and https://gitlab.com/baserock/import/blob/master/baserockimport/exts/python.find_deps are the relevant bits12:50
ssam2the first one finds the source code, the second one finds the dependencies12:51
persiaSeems like deriving a tool from that for buildstream-extras would likely make folk happy12:51
* tlater should think about doing this for npm as well, given his delving into that over Christmas12:52
persiaI believe baserock has examples for npm and gems, although both might have aged and not match current upstream practice12:52
ssam2yes, all in here: https://gitlab.com/baserock/import/tree/master/baserockimport/exts12:54
juergbitlater: for examples we actually might want a very permissive license, if we want people to use the examples as starting point for their own projects12:59
tlaterjuergbi: I'm not sure what license would be appropriate then, MIT?13:00
* tlater knows far too little about licenses13:00
tlaterFrankly, it might be best to leave licensing up to individual projects in here13:01
tlaterBut I'm not sure how to do that - careful review?13:01
juergbiMIT would be fine with me. don't have strong opinions for this particular case13:01
persiaThat makes sense, although a first pass might be very broad (something like MIT or ISC)13:01
persiatlater: Put a LICENSES file in root, explaiing that each subdirectory has it's own license.13:02
persiaThen make sure that happens.13:02
tlaterpersia: ta, seems most sensible - would the root directory need a separate license?13:02
gitlab-br-botbuildstream: merge request (juerg/recursive-pipelines->master: Junctions and subprojects) #160 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/16013:06
juergbijonathanmaw: can you please review this commit? https://gitlab.com/BuildStream/buildstream/merge_requests/160/diffs?commit_id=a83c94b74e0f65aa3cee328bc37be57b9ae7a5c313:06
jonathanmawjuergbi: will do after I've reviewed ssam2/tlater's docker source MR13:07
juergbita13:07
persiatlater: No, because it wouldn't contain anything other than directories and the instructions saying where to find licenses: nothing that needs licensing.13:21
*** adds68 has quit IRC13:22
* tlater created the examples repository, will wait for his other branches to merge before he adds the first example13:22
*** adds68 has joined #buildstream13:22
tlaterjmac: If you had an example project you wanted to push, this is the repo: https://gitlab.com/BuildStream/buildstream-examples13:22
jmacOK. I don't have any examples right now but might be able to make something13:23
* tlater thinks jonathanmaw may have had one for dpkg stuff, but isn't sure anymore13:24
ssam2we talked about putting most of the benchmark script in a separate repo13:57
ssam2so, shall I create https://gitlab.com/BuildStream/benchmarks ?13:57
* ssam2 will do so after lunch if nobody objects13:58
*** toscalix_ is now known as toscalix14:11
* jonathanmaw finishes reviewing the docker merge request14:18
jonathanmawtlater, ssam2 ^14:18
tlaterta jonathanmaw14:18
* tlater saw a few of the comments already14:18
*** adds68 has quit IRC14:40
*** adds68 has joined #buildstream14:40
jonathanmawjuergbi: reviewed that commit14:41
juergbita14:42
tlaterHeh, not a single one of our files currently passes pylint's code quality checks14:49
persiaFixing that might be a reasonable thing for someone to do whilst learning the source code, if anyone is starting fresh.14:50
tlaterpersia: I don't think that's possible. We simply don't adhere to normal python standards14:51
persiaOn purpose?  Or because we didn't try?14:51
* tlater thinks we didn't try14:52
tlaterBut at this point it would be a massive refactor, including rewriting some of our class infrastructure14:52
tlaterIt would be a lot easier to just change pylint's rules to adhere to our standards14:52
tlaterMaybe start enforcing some of the easier stuff (like ordering of imports)14:53
juergbii guess we could enable additional checks one by one when we want to?14:55
* tlater will look at disabling most things that seem hard to fix and be happy to pass on refactoring everything else, after that we can do what juergbi suggests14:57
persiaFor the OpenStack project, when they decided they were large enough to need coding standards, they set up a test framework that let them opt out of things, and then each repo opted in when they had time.  There was some social pressure on repos with lots of opt-outs, but not so much everyone had to rewrite everything from scratch.14:57
tlaterDo we have a line-length limit? I think I recall the Hacking.rst file saying it was 121, but it doesn't specify a number anymore15:01
jmacISTR hacking.rst saying we ignore the line length bits of PEP815:02
ssam2from setup.cfg15:02
ssam2pep8maxlinelength = 11915:02
*** mcatanzaro has joined #buildstream15:02
tlaterta ssam215:02
ssam2tlater, which of us should do the fixups on bst-external!915:10
ssam2?15:10
tlaterAh, sorry ssam215:10
tlaterI could probably do a few of them, but I lack context for others15:10
tlaterIt might be easier if you did them15:10
ssam2ok15:10
* ssam2 creates gitlab.com/buildstream/benchmarks15:27
tlaterSo, looking at slightly more refined pylint output, we have a lot of issues such as too-many-x and too-few-x (where x is variables, arguments, methods, ...)15:31
tlaterThose would be *nice* to sort out, since they decrease perceived complexity - but I doubt this is work we'd get to.15:32
ssam2i don't find those warnings very helpful to be honest15:32
ssam2you can't automate taste :-)15:32
persia+1 on not automating taste.15:32
persiaThat said, if one has very complex objects, it is sometimes useful to reconsider them to see if they sensibly decompose.15:33
* tlater suspects that having these warnings enabled in pylint would help in pointing it out15:35
tlaterBut I think our codebase is just too large to do this at this point15:35
gitlab-br-botbuildstream: merge request (146-use-minimum-python-version-3-4-for-integration-tests->master: Resolve "Use minimum python version (3.4) for integration tests") #266 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/26615:41
gitlab-br-botbuildstream: merge request (juerg/recursive-pipelines->master: Junctions and subprojects) #160 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/16015:41
*** ruben has joined #buildstream15:57
gitlab-br-botbuildstream: merge request (juerg/recursive-pipelines->master: Junctions and subprojects) #160 changed state ("merged"): https://gitlab.com/BuildStream/buildstream/merge_requests/16016:16
juergbitlater: !256 i assume this is leftover from debugging?16:24
juergbi# pprint(sys.modules)16:24
* tlater thought he got rid of that16:25
tlaterBut yes16:25
juergbii've rebased the branch locally and removed that16:25
tlaterAlso gitlab appears to be down16:25
juergbiok, will update the branch16:25
juergbioh?16:25
tlatertyvm juergbi16:25
tlaterI get a 50016:25
juergbihere as well now16:25
*** tristan has quit IRC16:26
tlaterHm, do we want to follow pep8 import order?16:29
juergbitlater: shall i also add a Fixes #171?16:29
juergbitlater: that would be alphabetical? not sure how this would look like with from imports16:29
tlaterIt also groups by internal-external and stdlib imports16:30
juergbiwe tend to currently group internal vs external imports16:30
tlaterYeah, but we don't do so consistently16:30
juergbisounds sensible to me but i don't know the details16:30
* tlater enables it for now and will show the fallout later16:30
tlaterAh, yeah, I think #171 can be closed with this16:30
tlaterHm16:30
juergbiok, i'll add it to the commit message as reference16:30
juergbior not?16:30
tlaterit's still slow16:31
juergbiah, gitlab16:31
* tlater just doubts we'll be able to improve it much16:31
juergbior completions?16:31
tlaterNo, the bash completions16:31
tlaterMaybe leave the issue open, someone might come with a bright idea16:31
juergbiok16:31
gitlab-br-botbuildstream: merge request (completion-optimizations->master: Completion optimizations) #256 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/25616:32
juergbijonathanmaw: !259 should no longer be marked WIP, right?16:36
* paulsherwood wonders if there's any way at all to get a link to tristan's talk today16:39
gitlab-br-botbuildstream: issue #242 ("Allow building as non-root inside the sandbox") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/24216:41
persiapaulsherwood: Not that I see yet, other than pestering volunteers (which often results in the opposite of one's desire).  I see both the immediately preceeding and immediately following talks posted though, so they might be getting through the day.16:42
juergbistate is still waiting for reviewer but so are a lot of others: https://review.video.fosdem.org/overview16:43
gitlab-br-botbuildstream: merge request (completion-optimizations->master: Completion optimizations) #256 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/25616:44
jonathanmawjuergbi: that's right16:44
* jonathanmaw un-WIPs it16:45
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:45
ssam2could someone approve https://gitlab.com/BuildStream/buildstream-docker-images/merge_requests/19/diffs ?16:47
ssam2i've just spent 10 minutes trying to figure out why it wasn't in builds, but turned out I never clicked the 'merge' button16:47
ssam2and now I had to rebase, which means it needs approval all over again16:47
juergbidone16:48
ssam2thanks16:48
tlaterta for merging 256 juergbi :)16:51
juergbiyw16:52
gitlab-br-botbuildstream: merge request (completion-optimizations->master: Completion optimizations) #256 changed state ("merged"): https://gitlab.com/BuildStream/buildstream/merge_requests/25617:07
gitlab-br-botbuildstream: merge request (juerg/dbus->master: WIP: Inherit user id and group id for bst shell) #265 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/26517:10
gitlab-br-botbuildstream: merge request (sam/document-profiling-and-benchmarks->master: WIP: HACKING.rst: Mention benchmarking and profiling tools) #267 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/26717:15
*** jonathanmaw has quit IRC17:15
gitlab-br-botbuildstream: merge request (juerg/dbus->master: WIP: Inherit user id and group id for bst shell) #265 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/26517:15
gitlab-br-botbuildstream: issue #243 ("dpkg import source plugin") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/24317:19
*** ruben has quit IRC17:20
* tlater wasn't aware how frequently we use `global`17:20
tlaterI'm already finding small bugs in error messages and such though :)17:22
*** tristan has joined #buildstream17:24
* tlater wonders if pep8 testing should be a separate task, considering we're currently duplicating the work for the linux and unix platforms17:29
*** aday has quit IRC17:30
*** aday has joined #buildstream17:31
persiatlater: Yes, I think code quality tests should probably only be run on one (selected) platform.  Running the same series of code analysis and static analysis tooling on multiple platforms provides little developer benefit.17:31
juergbiit doesn't take that much time, though. not sure whether spinning up another worker is worth it17:33
tlaterHrm, that would be a separate issue, but I think I'll just add it to this MR17:33
juergbimy comment was based on current pep8 time, with pylint it may be significant, no idea17:34
tlaterjuergbi: Ah, sorry, skipped that line somehow17:35
tlaterWith pylint it does become more significant17:35
tlaterI also think with more platforms it's a waste of resources, tests are slow enough as it is17:35
persiaIn that case, if we're considering the feedback loop from push to CI results, it may be interesting to split.17:36
tlaterI'll draft it out as part of this MR, see what people say at merge time - tristan will probably want to be involved in this discussion eventually17:37
jmacIs sdk.gnome.org down?17:54
persiajmac: Does not respond to ICMP or HTTP for me.17:55
jmacBoo.17:56
jmacI'll do something else then: Do we have any elements which create bootable images as artifacts?17:57
* tlater has one17:59
persiafreedesktop-sdk merged a change from ssam2 today, including  sdk/elements/vm/desktop-vm-image-x86_64.bst17:59
tlaterAbout to add it to the buildstream-examples repo, just waiting for ssam2 to finish merging his docker plugin17:59
tlaterjmac: This is the most barebones image we could come up with: https://gitlab.com/BuildStream/buildstream-examples/tree/x86image18:00
jmacGreat, just what I was after!18:01
*** ssam2 has quit IRC18:03
juergbipersia: i don't think the feedback loop is a big concern, developers are expected to run pytest locally before pushing18:23
* tlater would also add a recommendation to run pylint in your IDE to the hacking file18:24
tlaterjuergbi: Linting currently takes about 51 seconds, so it's probably not necessary to split.18:25
tlaterI think the output is neater if it isn't interwoven with everything else, though.18:25
tlaterThen again, hopefully future branches won't have quite as much to nag about18:25
persiaAdding linters does tend to reduce nagging over time18:26
*** toscalix has quit IRC18:37
*** valentind has joined #buildstream19:41
*** aday has quit IRC19:44
*** bethw has joined #buildstream21:38
*** valentind has quit IRC21:51
*** ruben has joined #buildstream23:02
*** kektrain has joined #buildstream23:08
*** kektrain has quit IRC23:10

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