IRC logs for #buildstream for Wednesday, 2020-04-01

*** mohan43u_ has quit IRC03:17
*** mohan43u has joined #buildstream03:17
*** mohan43u has quit IRC07:16
*** benschubert has joined #buildstream07:26
gitlab-br-botBenjaminSchubert approved MR !1848 (juerg/buildbox-run-error->master: _sandboxbuildboxrun.py: Check for buildbox-run initialization errors) on buildstream https://gitlab.com/BuildStream/buildstream/-/merge_requests/184807:27
*** tristan has quit IRC07:28
*** mohan43u has joined #buildstream07:42
gitlab-br-botjuergbi merged MR !1848 (juerg/buildbox-run-error->master: _sandboxbuildboxrun.py: Check for buildbox-run initialization errors) on buildstream https://gitlab.com/BuildStream/buildstream/-/merge_requests/184807:44
*** tpollard has joined #buildstream08:12
*** rdale has joined #buildstream08:31
*** tristan has joined #buildstream08:34
cphangtpollard, I've come across this before, this is the way that urllib is setup. Some servers block the default user agent https://gitlab.com/libreml/libreml/-/blob/master/elements/matplotlib.bst08:40
cphangA workaround by the matplotlib developers is to pass an empty user agent, but I'm not sure that's something that should be done by default: https://github.com/matplotlib/matplotlib/commit/21150c002bcc3817917b010c9636b807634b2cbd#diff-2eeaed663bd0d25b7e608891384b7298R13008:41
tpollardthat is..... interesting08:41
tpollardthis seemingly tracks elsewhere, I wonder if it's hitting a mirror08:45
juergbicould it make sense to set user-agent to BuildStream?08:45
juergbior do some servers whitelist certain UAs?08:46
WSalmonmight be worth asking the gnome people why it works in there ci but not locally08:46
WSalmonare they intersepting something..08:46
WSalmontpollard, have you checked that you can build the elements before you started changing things?08:47
tpollardI can track it in gbm08:48
*** santi has joined #buildstream08:48
tpollardif I track it in gbm, and then transpose that new url over to the fork, it works08:51
* tpollard boggles08:51
*** lachlan has joined #buildstream09:07
*** phoenix has joined #buildstream09:35
*** narispo has quit IRC09:40
*** narispo has joined #buildstream09:41
gitlab-br-botwillsalmon opened issue #1280 (Junction in junction requires top level junction) on buildstream https://gitlab.com/BuildStream/buildstream/-/issues/128009:47
*** phoenix_ has joined #buildstream09:50
*** phoenix has quit IRC09:50
*** chipb has quit IRC09:50
*** jward has quit IRC09:50
*** douglaswinship has quit IRC09:50
*** lchlan has quit IRC09:50
*** chipb has joined #buildstream09:51
*** jward has joined #buildstream09:51
*** douglaswinship has joined #buildstream09:51
*** lchlan has joined #buildstream09:51
*** phoenix_ is now known as phoenix09:51
*** lachlan has quit IRC09:58
*** narispo has quit IRC10:05
*** narispo has joined #buildstream10:05
valentindOn Debian sid now, I cannot call tox with the current requirements. I had to run "make" in requirements/10:07
valentindI think one of the issue is the version "packaging".10:08
valentindWhich is too old from my installed pip. And tox seems to use the installed pip.10:09
valentindAre there any plan to use a systemd user socket to launch buildbox-casd? Would be better to make sure it is linked to the user session and that systemd kills if buildstream crashed.10:18
valentindIt is also much better to have the socket in /run than /tmp.10:19
juergbivalentind: unfortunately, systemd socket activation is blocked by https://github.com/grpc/grpc/issues/1913310:21
juergbiwell, it might be possible to work around it by writing our own socket handling code bypassing the one from gRPC, but not sure how much effort that would be10:22
valentindjuergbi, I would expect that systemd has already work arounds for that.10:22
juergbiI don't think this can really be worked around on the systemd side (in a reasonable way, without ptrace)10:24
valentindI would expect some kind of piping.10:24
valentindBut OK, maybe it is more complex that I imagine.10:25
juergbiit might not be that difficult to work around it inside buildbox-casd10:25
juergbia python workaround is linked in the bug I mentioned10:26
juergbisomething similar may be possible in C++10:26
juergbiI was originally hoping it would be properly fixed in gRPC by now10:26
*** lachlan has joined #buildstream10:33
valentindjuergbi, I will create an issue on buildbox-casd.10:33
*** lachlan has quit IRC10:58
*** lachlan has joined #buildstream11:02
*** lachlan has quit IRC11:29
abderrahim[m]Hey guys, I just noticed my messages didn't get through as I didn't identify with nickserv11:31
abderrahim[m]was wondering why I was invisible11:31
abderrahim[m]am I visible now?11:31
tpollardyep11:31
abderrahim[m]so tpollard about your track problem: are you sure you're not defining a mirror in your fork?11:32
abderrahim[m]and tracking shouldn't change the url, btw11:32
abderrahim[m]did you mean the ref?11:33
tpollardthe project.conf was un-altered in the fork11:33
tpollardit was subbing in the alias from the project.conf into the url field after tracking in the working tree though11:34
tpollardanyhow, back up & running now, not really sure what went on11:34
gitlab-br-bottristanvb merged MR !1846 (tristan/bst-1/testsuite-py38->bst-1: Pass CI with python3.8) on buildstream https://gitlab.com/BuildStream/buildstream/-/merge_requests/184611:54
abderrahim[m]tristan: Hi :)11:55
*** ChanServ sets mode: +o tristan11:55
* tristan will also set this one line https://gitlab.com/BuildStream/buildstream/-/merge_requests/1847 to merge when completed...11:55
tristan*when pipeline completes11:56
tristanHi abderrahim[m] :)11:56
abderrahim[m]for 1.4.2, I'd like to have !1842 merged too11:56
gitlab-br-botMR !1842: mount: don't pass nonempty option https://gitlab.com/BuildStream/buildstream/-/merge_requests/184211:56
tristanaha11:58
tristanabderrahim[m], do you know off hand what that option does/means ?11:58
abderrahim[m]allow to mount on top of non empty directory11:59
abderrahim[m]we only mount on empty directories so it doesn't matter11:59
tristanI think the tests passing are a good indication of that :)12:00
tristanOk lets do that, I suppose this is irrelevant to master ?12:00
abderrahim[m]already merged in master, this is a backport12:00
tristanAh, more context :D12:01
gitlab-br-bottristanvb approved MR !1842 (abderrahim/fuse3-1->bst-1: mount: don't pass nonempty option) on buildstream https://gitlab.com/BuildStream/buildstream/-/merge_requests/184212:01
tristanAlright it's on the way12:01
*** phoenix has quit IRC12:36
*** hasebastian has joined #buildstream12:53
*** lachlan has joined #buildstream12:55
gitlab-br-bottristanvb merged MR !1842 (abderrahim/fuse3-1->bst-1: mount: don't pass nonempty option) on buildstream https://gitlab.com/BuildStream/buildstream/-/merge_requests/184212:55
tristanremote: GitLab: You are not allowed to push code to protected branches on this project.13:18
tristanThat's new ^^^^13:18
gitlab-br-bottristanvb opened MR !1849 (tristan/bst-1/news-update-1.4.2->bst-1: NEWS: Updated for 1.4.2 release) on buildstream https://gitlab.com/BuildStream/buildstream/-/merge_requests/184913:19
* tristan awaits another round of CI so he can create a new tag13:20
* tristan hopes he is allowed to push a tag !13:20
*** phoenix has joined #buildstream13:34
tristanvalentind, seems we still have CI issues, e.g.: https://gitlab.com/BuildStream/buildstream/-/jobs/49413210213:34
tristanhappening now :-S13:34
tristanbut please don't start killing jobs, I think we can get https://gitlab.com/BuildStream/buildstream/pipelines/131824526 through so I can push a release tag13:35
coldtomhttps://docs.gitlab.com/ee/ci/yaml/#skipping-jobs might be of use for doc/news changes like that, tristan13:36
tristanohhhh that's good to know13:39
tristancoldtom, do you know why I don't have an enabled "merge" button here: https://gitlab.com/BuildStream/buildstream/-/merge_requests/1849 ?13:42
coldtomlooks like you need approval if ci is skipped13:43
coldtomwhich i guess makes sense13:43
*** phoenix has quit IRC13:43
tristanStill says no approval required13:43
valentindtristan, looking at the logs13:43
tristanCan someone approve !1849 ?13:44
tristanSee if that helps ?13:44
tristanI think that it might be a gitlab bug, as I may have had that on "Merge when pipeline succeeds", and then force pushed a version with [skip ci]13:44
valentindSame thing as yesterday I think. gitlab-runner seems to be stuck in some loop trying to remove machines.13:45
valentind422 creating this/these droplet(s) will exceed your droplet limit13:48
valentindtristan, jjardon, have we set a droplet limit?13:48
gitlab-br-botcoldtom approved MR !1849 (tristan/bst-1/news-update-1.4.2->bst-1: NEWS: Updated for 1.4.2 release) on buildstream https://gitlab.com/BuildStream/buildstream/-/merge_requests/184913:50
jjardonvalentind: IT always has been 50; it was increased to 100 like 2 months ago13:50
tristancoldtom, ummm, did the button become enabled ? I just pushed one more revision of that branch, can you reapprove please ?13:51
gitlab-br-botcoldtom approved MR !1849 (tristan/bst-1/news-update-1.4.2->bst-1: NEWS: Updated for 1.4.2 release) on buildstream https://gitlab.com/BuildStream/buildstream/-/merge_requests/184913:51
jjardonvalentind: something is wrong if we need more than 100, I think13:52
valentindI can increase the frequency of running cleanup-docker-machine.timer13:52
tristancoldtom, thanks... unfortunately still cannot merge it :-S13:52
tpollardon the DO dashboard there's many droplets that are over 6 hours old13:52
tpollardI presume they're all stuck again13:52
valentindWait that was not that script13:54
tristanOk well, I'll remove the [skip ci], repush, and wait for the pipeline to chug along I guess13:54
tristanShould I wait for the runner situation to get fixed ?13:54
valentindThere was one script that was removing old machines.13:54
* tristan queues a CI of the NEWS entries13:56
tpollardvalentind: https://gitlab.com/BuildStream/infrastructure/infrastructure13:56
tpollardthat should be cronning hourly13:56
*** hasebastian has quit IRC13:58
valentindtpollard, Does this delete the droplets?13:59
jjardontristan: Id skip CI for README/ NEWS changes14:00
valentindAh right. droplet.destroy()14:00
jjardontristan: -o ci.skip when you push14:00
valentindWell it is not what is on the machine.14:00
valentindSo it is broken.14:00
valentindSomeone modified the script to remove docker machine files.14:01
valentindBut this is done by another script.14:01
coldtombenbrown was looking around in there recently i believe14:01
valentind/root/destroy_droplets/destroy_old_droplets.py14:02
valentindThis was modified to do something that /usr/local/bin/cleanup-docker-machine already does.14:03
valentindBut it stopped removing droplet.14:03
valentindI put back the old file then.14:03
valentindSo it deleted few. But many are not that old. I will automatically delete the ones that are older than 12 hours.14:07
tpollardOk14:09
tpollardI think 12 is lose enough threshold14:09
valentindOK, that should be a bit bettr.14:09
tpollard*loose14:10
valentind"Invalid user appserver from 45.55.238.20 port 55422"14:12
tristanjjardon, that doesn't work, though14:12
tristanjjardon, we just tried it; it results in a merge request being confused and not being able to merge14:13
valentindtristan, there are still some issues14:13
valentindBut now it is creating new builders. Let's see if those work.14:13
valentind"429 Too many requests"14:14
jjardontristan: mmm, maybe you have some special config in buildstream ci, but it should work: https://docs.gitlab.com/ee/user/project/push_options.html#push-options-for-gitlab-cicd14:14
tristanstill some issues with CI ? or issues with !1849 ? (sorry ambiguity... the merge request was telling me I needed to resolve "all the issues" above before I can merge)14:15
gitlab-br-botMR !1849: NEWS: Updated for 1.4.2 release https://gitlab.com/BuildStream/buildstream/-/merge_requests/184914:15
tristanjjardon, we are not allowed to push to protected branches from the command line, that might be a special config14:15
tristannot sure14:15
tristanAnyway, it's not like these commits are super frequent14:16
tristanIt's not particularly urgent either but I'd like to finish the release tonight heh14:16
valentindWe are under attack, see: journalctl | grep "invalid user"14:20
valentindThey are scanning lots of users.14:22
tpollardouch, yep that's getting hit hard14:24
tristanheh14:25
tpollardthey're scrambling the IP's too14:28
valentindMost are from digital ocean.14:29
valentindBut I suppose it is compromised.14:29
valentindtristan, Can you tell me if the ci is working better for your now?14:33
valentindHow do we contact the security team of digital ocean?14:34
valentindProbably abuse@14:34
tristanvalentind, it's been working alright except for that pipeline which had some retries going on earlier, at least for the couple of pipelines I've triggered14:36
tristanvalentind, All I can really observe here is (A) Long time to assign a runner / not all jobs being processed in parallel... (B) Errors in trying to get a runner14:37
tristanThose two things don't seem to be happening right now14:37
tristanhttps://gitlab.com/BuildStream/buildstream/pipelines/131839312 seems almost done now14:38
valentindtristan, Can you tell me if you see it again happening? I fixed a few things. I think there will still be some issues with retries due to some throttling from digital ocean API.14:40
valentindBut I hope that the complele failures that were due to a modified script and a limit in the number of droplet, should be fixed.14:41
tristanOk nice :)14:43
tristanYup I'll keep you posted14:43
gitlab-br-bottristanvb merged MR !1849 (tristan/bst-1/news-update-1.4.2->bst-1: NEWS: Updated for 1.4.2 release) on buildstream https://gitlab.com/BuildStream/buildstream/-/merge_requests/184914:45
*** tristan changes topic to "BuildStream 1.4.2 is out ! | https://gitlab.com/BuildStream/buildstream | Docs: https://docs.buildstream.build/ | IRC logs: https://irclogs.baserock.org/buildstream | Mailing List: https://mail.gnome.org/mailman/listinfo/buildstream-list | Roadmap: https://wiki.gnome.org/Projects/BuildStream/Roadmaps"14:49
*** tristan has quit IRC14:54
valentind\o/15:06
tpollard:)15:07
valentindI realize there is now a fix for fuse3 in master. Was this backported to 1.4?15:09
coldtomvalentind, yep15:13
valentindYeah!15:14
valentindI can now update!15:14
*** lachlan has quit IRC15:20
juergbidebian 9 docker image build fails because it can't install cmake15:38
juergbifrom stretch-backports15:39
juergbiThe following packages have unmet dependencies:15:39
juergbi cmake : Depends: libarchive13 (>= 3.3.3) but 3.2.2-2+deb9u2 is to be installed15:39
juergbii.e., it seems cmake was updated in stretch-backports but the required dependency was not updated15:39
juergbiI can install more recent libarchive13 from stretch-backports-sloppy but I'm not sure whether that's the proper solution15:40
juergbianyone more familiar with debian backports here? to me it seems like a distro bug15:41
juergbiit worked fine a few weeks back where stretch-backports still had an older cmake version but it seems the older package has been deleted from the archive :-/15:42
*** lachlan has joined #buildstream15:43
juergbimaybe it's time to discuss dropping support for python 3.5 / debian 915:44
benschubert^ I think that might be a good thing for bst 2.0 anyways. We could use async for some parts also now15:48
*** tristan has joined #buildstream15:49
*** lachlan has quit IRC15:55
tpollardThere's a few other 3.5 niggles we can drop too15:56
tpollardblack not supporting 3.5 is one that comes to mind15:58
juergbiregular EOL of Debian 9 is anyway expected in a few months, although LTS support will be available for another two years or so16:00
juergbishould probably propose this on the mailing list16:01
tpollardthat reminds me, 20.04 Ubuntu will be LTS too won't it?16:01
*** lachlan has joined #buildstream16:01
juergbiyes16:04
juergbi18.04 is already on Python 3.616:04
* tpollard nods 16:04
*** mohan43u has quit IRC16:59
*** tpollard has quit IRC17:01
*** mohan43u has joined #buildstream17:03
*** lachlan has quit IRC17:05
*** mohan43u has quit IRC17:10
*** mohan43u has joined #buildstream17:13
*** lachlan has joined #buildstream17:23
*** santi has quit IRC17:59
*** santi has joined #buildstream17:59
*** traveltissues has quit IRC18:06
*** traveltissues has joined #buildstream18:07
*** robjh has quit IRC18:07
*** jward has quit IRC18:07
*** valentind has quit IRC18:07
*** WSalmon has quit IRC18:07
*** bethw has quit IRC18:07
*** bethw has joined #buildstream18:07
*** jward has joined #buildstream18:07
*** robjh has joined #buildstream18:08
*** valentind has joined #buildstream18:11
*** WSalmon has joined #buildstream18:13
*** lachlan has quit IRC18:14
*** santi has quit IRC18:22
*** ikerperez has quit IRC18:28
*** cphang has quit IRC18:28
gitlab-br-botdylanmccall opened issue #1281 (Downloadable file source is not setting a user agent; rejected by gitlab) on buildstream https://gitlab.com/BuildStream/buildstream/-/issues/128118:46
*** cphang has joined #buildstream19:19
*** toscalix has joined #buildstream19:24
*** benschubert has quit IRC19:55
*** phoenix has joined #buildstream20:26
*** rdale has quit IRC21:39
*** toscalix has quit IRC22:42

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