Friday, 2020-08-14

openstackgerritMerged zuul/zuul master: Correctly fail cat/fileschanges when update fails  https://review.opendev.org/73976200:01
openstackgerritIan Wienand proposed zuul/zuul-jobs master: ensure-docker: remove amd64 architecture pin  https://review.opendev.org/74624500:09
*** hashar_ has joined #zuul00:26
*** hashar has quit IRC00:28
openstackgerritIan Wienand proposed zuul/zuul-jobs master: ensure-docker: remove amd64 architecture pin  https://review.opendev.org/74624500:29
openstackgerritIan Wienand proposed zuul/zuul-jobs master: ensure-docker: remove amd64 architecture pin  https://review.opendev.org/74624500:30
*** rfolco has quit IRC00:42
*** mgoddard has quit IRC01:00
*** mgoddard has joined #zuul01:06
*** reiterative has quit IRC02:53
*** Tahvok has quit IRC02:53
*** johanssone has quit IRC02:53
*** irclogbot_3 has quit IRC02:53
*** avass has quit IRC02:53
*** Miouge has quit IRC02:53
*** guillaumec has quit IRC02:53
*** bstinson has quit IRC02:53
*** frickler has quit IRC02:53
*** reiterative has joined #zuul02:59
*** Tahvok has joined #zuul02:59
*** johanssone has joined #zuul02:59
*** irclogbot_3 has joined #zuul02:59
*** avass has joined #zuul02:59
*** Miouge has joined #zuul02:59
*** guillaumec has joined #zuul02:59
*** bstinson has joined #zuul02:59
*** frickler has joined #zuul02:59
*** evrardjp has quit IRC04:33
*** evrardjp has joined #zuul04:33
*** zbr1 has joined #zuul05:05
*** zbr has quit IRC05:06
*** zbr1 is now known as zbr05:06
openstackgerritSimon Westphahl proposed zuul/nodepool master: Ignore unparsable/empty image upload ZNode data  https://review.opendev.org/73801305:33
swestclarkb: corvus: addressed your comments ^05:35
*** saneax has joined #zuul05:44
*** ianw has quit IRC05:48
*** ianw has joined #zuul05:49
*** logan- has quit IRC05:49
*** hashar_ has quit IRC05:50
*** logan- has joined #zuul05:51
*** logan- has quit IRC05:59
*** logan- has joined #zuul05:59
ianwcorvus: not sure why, but I'm not seeing https://review.opendev.org/746245 be deployed with depends-on in pyca/ repos.  i don't think it's a trusted repo?  i'm not sure why06:58
*** bhavikdbavishi has joined #zuul07:18
*** vishalmanchanda has joined #zuul07:21
*** hashar_ has joined #zuul07:33
*** hashar_ is now known as hashar07:35
AJaegerzbr: I see ansible-lint failing on zuul-jobs with E208 - but that is not documented in https://docs.ansible.com/ansible-lint/rules/default_rules.html ;(07:46
AJaegerzbr: and there are false positives on roles/add-build-sshkey/tasks/remote-linux.yaml AFAIU ;(07:48
zbrAJaeger: i am fully aware of it07:48
zbrAJaeger: maybe you can help me with https://github.com/ansible/ansible-lint/pull/949 fix07:48
zbri made it two days ago...07:49
zbrAJaeger: you will not find any documentation on ansible official website, that is outdated by more than an year07:50
zbrhttps://ansible-lint.readthedocs.io/en/latest/default_rules.html#file-permissions-not-mentioned07:50
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: Disable E208 for now  https://review.opendev.org/74631007:51
AJaegerzbr: thanks.07:52
AJaegerzbr: there seem to be more problems than you fix, see my commit message above07:52
zbrAJaeger: do a review on the linter even if you are not core, it will help me fastrack the fix.07:52
zbri can make a release on the linter at any time but I cannot merge my own patches.07:53
AJaegerzbr: will do ;)07:53
AJaegerzbr: and reading your change, it should adddress the spots I found - great!07:53
zbrthat fix resolves ~40% of issues reported on zuul-jobs07:53
zbrfor the rest I am afraid adding mode is needed, unless someone finds other criterias to lower the false-positives07:54
zbri plan to add an option to downgrade errors to warning level, to make transitions easier07:54
zbrdisabling the rule does not help adding new bugs or fixing them progressively07:55
AJaegerzbr: yes, we should fix the real problems... I started to go down that road and run into too many false positives.07:56
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: Disable E208 for now  https://review.opendev.org/74631007:57
zbravass: can you help with ^ linter fix above? i think your vote is counted.07:58
avasszbr: looking07:58
AJaegerzbr: do you ask avass to review https://github.com/ansible/ansible-lint/pull/949 or https://review.opendev.org/746310 - or both? ;)07:59
zbrboth07:59
avasszbr, AJaeger: approved both :)08:00
zbrAJaeger: fyi, anyone is welcomed to help with linter maintenance, just comment on https://github.com/ansible/ansible-lint/issues/81508:00
avassAJaeger: should I +wf that since it's blocking things? or is there any zuul-jobs maintainer here?08:01
AJaegerianw, frickler , do you have time to approve https://review.opendev.org/746310 to unblock zuul-jobs, please?08:02
AJaegeravass: let's ask first ^. And while it blocks - if we have an urgent fix, I agree with single-core accept it but I think we have time to wait a bit...08:03
avassAJaeger: sure :)08:04
avassAJaeger: there's not really a lot happening in zuul-jobs at the moment anyway :)08:05
AJaegeravass: yeah, vacation time for many...08:05
zbrvacation time makes merging anything a stuggle08:10
AJaegerless conflicts ;)08:10
zbri still hope to see https://review.opendev.org/#/c/739482/ merged to unblock other UI/UX changes.08:12
zbri have 6m+ changes waiting for preferences dialog08:13
zbrjust because some people asked for some changes to be "optional"08:13
*** hashar has quit IRC08:34
tobiashcorvus: did you not +w the zuul.ignore change on purpose or shall we merge it (744811)?08:59
openstackgerritMerged zuul/zuul-jobs master: Disable E208 for now  https://review.opendev.org/74631009:02
openstackgerritMerged zuul/zuul-jobs master: ensure-pip: add instructions for RedHat system  https://review.opendev.org/74375009:02
openstackgerritMerged zuul/zuul master: Annotate github client in mergePull  https://review.opendev.org/74475509:52
openstackgerritMerged zuul/zuul master: gitlab: support the labels requirement  https://review.opendev.org/74189309:52
*** wuchunyang has joined #zuul09:53
*** bhavikdbavishi has quit IRC09:54
*** wuchunyang has quit IRC09:59
openstackgerritMerged zuul/zuul master: Log complete output of kubectl port-forward  https://review.opendev.org/74518210:01
openstackgerritMerged zuul/zuul master: Fix some doc typos  https://review.opendev.org/74623210:06
*** tosky has joined #zuul10:22
*** bhavikdbavishi has joined #zuul10:24
*** bhavikdbavishi1 has joined #zuul10:27
*** bhavikdbavishi has quit IRC10:29
*** bhavikdbavishi1 is now known as bhavikdbavishi10:29
*** sanjayu_ has joined #zuul10:55
*** saneax has quit IRC10:57
*** sanjayu_ has quit IRC11:13
*** sanjayu_ has joined #zuul11:14
*** saneax has joined #zuul11:20
*** sanjayu_ has quit IRC11:23
*** saneax has quit IRC11:43
felixedelzuul-maint: How do you usually deal with breaking changes to the Zuul web API? I have sopmething in my mind that zuul-web should support the two latest versions of the frontend, right? So we could introduce something like an api_version parameter which must be set to get the new API result? Background: I'm currently implementing a pagination for the builds/ and buildsets/ pages. While this works quite well with12:13
felixedelpatternfly, we need the total number of builds/buildsets to make the pagination work properly as this information is used to calculate the total pages. By now, the builds/ endpoint directly returns the build list, which does not provide any room for additional attributes like total_builds. Thus, I would like to change this endpoint to return something like {"builds": [], "total_builds": 123} instead.12:13
felixedelThe same applies for the buildsets/ endpoint12:14
tobiashtypically zuul-web should support the last release, not two releases back so users can upgrade their services without having to care about the upgrade ordering12:15
tobiashrunning mixed version zuul deployments is actually not really supported except during upgrade paths12:16
*** hashar has joined #zuul12:18
mnasertobiash: i think the bigger concern is the fact the api behaviour changes -- felixedel: could you not for example as something where you implement offset/limit parameters which won't break the api12:22
mnaserso if they're missing, you get * -- if they're not, you get N builds -- but i think the problem with that is now you cant get your total count12:22
tobiashah yes, that's public api...12:25
tobiashthen yes, we need to think about this more12:55
felixedeltobiash: With the last two, I mean the last and the current :D12:56
felixedelmnaser: Yes, the problem is not the limit/skip as those are already available. But you don't know how many pages are available depending on your filters. Another way would be to somehow always allow moving to the next page, but then the last page would be empty when no results are available anymore. Which is also not a good solution in my opinion. Our we could implement an infinite scrolling but that's IMHO also not13:00
felixedelthe best solution for such a table13:00
*** bhavikdbavishi has quit IRC13:04
openstackgerritBenjamin Schanzel proposed zuul/nodepool master: OpenShift/k8s Provider: Basic Support for k8s nodeSelectors  https://review.opendev.org/74632013:24
mnaserfelixedel: yeah also its not nice if you want to point someone to a specific page13:30
mnaserif builds are page 4, "please scroll a bunch" :p13:30
zbrfelixedel: to avoid changing the REST url, you could specify the client version using http headers13:45
zbrothers like jira used an /api/version/... urls.13:46
felixedelzbr: Yes, api_version as http_header also came to my mind. Or something like Github does with the "beta" feature_flags13:46
zbrwhile nice, is a bit problematic as some clients may find hard to add headers, not even sure is possible with ajax13:47
zbrwhat they did at https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/ seems safer.13:47
zbrkeep in mind that this applies to /rest/api/13:48
openstackgerritBenjamin Schanzel proposed zuul/nodepool master: OpenShift/k8s Provider: Basic Support for k8s nodeSelectors  https://review.opendev.org/74632014:39
openstackgerritFelix Edel proposed zuul/zuul master: WIP: Return number of total builds from builds/ API endpoint  https://review.opendev.org/74632814:40
*** hashar has quit IRC14:46
corvustoday is a PTO day for me, i'll be back next week14:56
fungihave a good weekend!15:00
*** sgw1 has joined #zuul15:34
*** bhavikdbavishi has joined #zuul15:40
*** tosky has quit IRC15:43
zbr1h ago pytest-xdist==2.0.0 was released, and it breaks with pytest-cov, happy friday!15:49
fungii don't think we're using pytest not running coverage jobs for zuul, at least15:50
fungier, i don't think we're using pytest nor running coverage jobs15:50
*** bhavikdbavishi has quit IRC15:59
*** hamalq has joined #zuul16:01
openstackgerritMerged zuul/zuul-jobs master: ensure-docker: remove amd64 architecture pin  https://review.opendev.org/74624517:57
*** hashar has joined #zuul19:26
clarkbcorvus: swest I've +2'd https://review.opendev.org/#/c/738013/9. We hit a similar problem with that again today though it was through the getBuilds path I think20:22
clarkbso we may need to do similar there like ^ does with uploads?20:22
*** hashar has quit IRC20:48
openstackgerritClark Boylan proposed zuul/nodepool master: Ignore unparsable/empty image build ZNode data  https://review.opendev.org/74634920:53
clarkbswest: corvus ^ not sure if the udnerlying cause is the same but I think that will handle it for the build case20:54
*** vishalmanchanda has quit IRC21:43

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!