IRC logs for #buildstream for Tuesday, 2020-06-02

*** Aaliyah9331 has joined #buildstream00:13
*** Aaliyah9331 has quit IRC00:15
*** Julia4306 has joined #buildstream00:35
*** Julia4306 has quit IRC00:36
*** Julia6672 has joined #buildstream02:53
*** Julia6672 has quit IRC02:54
*** Chloe3225 has joined #buildstream04:47
*** Chloe3225 has quit IRC04:49
*** Kaylee7001 has joined #buildstream05:21
*** Kaylee7001 has quit IRC05:22
*** tristan has quit IRC07:16
*** tristan has joined #buildstream07:20
*** ChanServ sets mode: +o tristan07:24
*** jude has joined #buildstream07:54
*** rdale has joined #buildstream08:02
*** phildawson has joined #buildstream08:12
WSalmonhttps://gitlab.com/BuildGrid/buildbox/buildbox-common/-/commits/juerg/grpc-retry juergbi this has seems to have worked well for my FD branch using what was bst-master. is there anything i can do to help with getting it landed and a new release?08:24
juergbiWSalmon: thanks for testing. no, I don't think further help is needed right now. I'll try to get this over the line soon08:25
WSalmonbrill thanks juergbi08:27
*** benschubert has joined #buildstream08:29
*** Peyton7250 has joined #buildstream08:30
*** Peyton7250 has quit IRC08:32
juergbiironfoot, jjardon, tristan: can we limit this channel to registered users? I'm getting tons of privmsg spam and they seem to be gathering the nick from this channel08:33
juergbior is there an alternative to block them? haven't looked into IRC possibilities for quite a while08:34
jjardonjuergbi: sure, do you know the IRC mode ? I will search for it if not08:35
juergbinot otoh08:35
jjardonjuergbi: +r should be already active08:36
juergbijjardon: this means only registered users can write to the channel, but they can still join, right?08:37
juergbiif they can join, they get the channel list and they can send privmsg08:37
jjardonlet me recheck08:37
juergbior can I limit my privmsg to registered users?08:37
jjardondocs says "Prevents users who are not identified to services from joining the channel."08:37
juergbihm08:37
jjardonhere: https://freenode.net/kb/answer/channelmodes08:38
juergbijjardon: see top join/quit lines: https://irclogs.baserock.org/buildstream/%23buildstream.2020-06-02.log.html08:38
juergbithese are the spam sources08:38
jjardonmmm,  maybe GIMPNET have different meanings08:38
jjardonI will ask in sysadmin08:38
juergbita08:38
*** Elizabeth7281 has joined #buildstream08:39
juergbiif it's just me they're targeting for some reason, maybe I can block them somehow on my side08:39
juergbiand the next Elizabeth728108:39
coldtomjuergbi, i've been having a lot of spam from privmsgs too08:39
juergbiok, so we should block it generally08:39
jjardonjuergbi: I've been receiving priv messages as well, but I'm in a lot of other channels in GIMPNET08:40
*** Elizabeth7281 has quit IRC08:40
*** Elizabeth8633 has joined #buildstream08:41
juergbiI'm also in other channels but I see the spam sources only in #buildstream, as far as I've checked08:42
benschubertjuergbi: csing and I were also receiving some08:42
benschubertand we're only on this channel08:42
juergbiok, thanks for confirming08:42
abderrahim[m]juergbi: you can restrict privmsg to registered users08:42
abderrahim[m]set your user mode to +R08:42
abderrahim[m](that's what the matrix bridge currently does, and it seems to work)08:42
*** Elizabeth8633 has quit IRC08:43
juergbiok, thanks. will do that but would be good to find a solution without user config, of course08:43
juergbiand also avoiding the join/quit spam08:43
abderrahim[m](that's what the matrix bridge currently does)08:47
abderrahim[m]juergbi: you can set your user mode to +R to block priv messages from non-registered users08:49
juergbiyes, got that. thanks08:49
*** santi has joined #buildstream08:50
abderrahim[m]I wasn't identified and fractal didn't tell me, so I switched to riot and posted again in case it didn't go through08:50
*** tpollard has joined #buildstream08:57
*** jjardon sets mode: +R 08:58
jjardonjuergbi: seems the correct mode is +R08:58
juergbita08:58
*** jude has quit IRC09:05
tristanbenschubert, I edited my last comment on !1948, with what I think is a reasonable explanation as to why we cannot simply cache the target of the element in a loader's local `_elements` cache09:20
benschuberttristan: ah sorry, forgot to answer that one, yeah seems reasonable. let's go for what we have then :)09:21
tristanno worries, I was temporarily stuck in a meeting anyway :)09:21
traveltissuesi think the bots are just joining the channel and skimming the user list09:21
cphangthat sounds plausible09:22
* tristan just comes in in the morning and deletes a hand full of PMs09:22
traveltissuessince they always join, leave after 2 seconds and then after some time i get a query09:22
*** tristan has quit IRC10:16
*** tristan has joined #buildstream11:04
*** ChanServ sets mode: +o tristan11:04
WSalmonbst will cache failure, this can be good as if this happens in CI i can then pull down the artifact and look at the log. but some times things fail for intermittent reasons, if i have a runner with a "semi" persistent cache and i try to rerun the job bst will not try to rebuild, i have to go and manually clear the runner's cache. is there a way to keep the creation and pushing of artifacts but have bst rerun when it finds cached failure? and if it11:45
WSalmondose rerun push the successful artifact over the failed on?11:45
WSalmoni basiclly want to do `bst --no-interactive build --always-retry ELEMENT.bst`11:50
WSalmonjuergbi, benschubert ^11:50
juergbiWSalmon: yes, we should add such an option. always-retry might not be the best name as it might also mean retry failures in the new session11:51
juergbiand we should make sure push replaces the artifact proto on the server11:51
juergbiI'm wondering whether it would make sense to implicitly expire failed artifacts11:52
juergbiat least in terms of considering an element cached11:52
juergbii.e., always retry builds if the only cached artifact is an old failed build. the question would be how do we define 'old'11:53
juergbimaybe even have a userconfig for this. and if you specify 0s as expiry, it will never use cached failures11:54
WSalmonsounds good to me, just wanted to check we didnt have this already, ill make a issue11:55
WSalmoni presume this is addional cli so dosent need to block bst2?11:55
juergbiyes, I don't think this needs to block bst211:56
juergbi(but would still make sense to get done before)11:56
WSalmon+111:57
WSalmonjuergbi, tpollard https://gitlab.com/BuildStream/buildstream/-/issues/133512:07
tristanjuergbi, I think user config makes sense here too12:18
tristanOriginally, I thought "Every user config should be in the user config, and only special/frequently changing ones should be exported additionally to CLI options"12:18
tristanBut then we found some exceptions to that which made sense12:19
tpollardWSalmon: cheers for raising the issue12:26
tpollard+1 to user config12:27
tristanbenschubert, please remember the junctions thread :)13:07
tristanTook me a while to rebase but !1901 is up and running again13:08
*** tristan has quit IRC13:13
traveltissuescan i have a review please https://gitlab.com/BuildStream/bst-plugins-experimental/-/merge_requests/11713:27
*** narispo has quit IRC13:50
*** tristan has joined #buildstream13:54
*** ChanServ sets mode: +o tristan13:54
*** rdale has quit IRC14:03
WSalmonhttps://gitlab.com/libreml/libreml/-/jobs/577469860/raw is confusing, it tries to pull many elements that are cached but clames they are not not the remote, it then builds them and then when it pushes says they were already on the remote, this seem quite confusing16:18
WSalmoneg matplotlib.bst16:18
WSalmonwe dont think that it expired16:21
WSalmonjuergbi, do you have any idea what could cause this?16:21
coldtomthe artifact server has logged no UpdateArtifact requests with that cache key, if that's relevant at all16:22
cphangWSalmon coldtom I suspect we'll need to create a smaller test case to be able to reproduce locally?16:23
*** tpollard has quit IRC17:13
douglaswinshipdoes anyone know why Buildstream would tell me that "bst-plugins-experimental does not contain a plugin named 'git_tag'", when it clearly does?17:56
douglaswinshipi've checked, and i'm pip-installing from a local copy of the experimental repository, and it has git_tag.py in sources.17:57
*** santi has quit IRC19:02
tristandouglaswinship, two thoughts come to mind, did you configure it in project.conf: https://docs.buildstream.build/master/format_project.html#pip-plugins ?19:17
tristanif not, and the error is due to missing config, please file an issue about improving the error message19:17
tristanOtherwise, the other thought is you might have bst-plugins-experimental installed twice19:18
tristanpython is confusing that way, leaving you in situations with 10 different places where things get installed overshadowing eachother19:18
tristanif that ends up being the cause, it might be worth improving the error message to indicate what path the plugin was loaded from (possibly helping the user identify the issue)19:19
tristanAnother less likely reason is if bst-plugins-experimental has the plugin but has not created an entry point for it in setup.py, that's quite unlikely19:22
*** benschubert has quit IRC19:58

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