15:30:05 #startmeeting Pulp Triage 2020-01-21 15:30:05 #info fao89 has joined triage 15:30:05 !start 15:30:05 Meeting started Tue Jan 21 15:30:05 2020 UTC. The chair is fao89. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:30:05 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:30:05 The meeting name has been set to 'pulp_triage_2020-01-21' 15:30:05 fao89: fao89 has joined triage 15:30:32 !next 15:30:33 fao89: 3 issues left to triage: 6025, 6016, 5991 15:30:33 #topic https://pulp.plan.io/issues/6025 15:30:34 RM 6025 - binlinf0 - NEW - Pulp 3.0 remote cert sha256 value doesn't match the input or the cert 15:30:35 https://pulp.plan.io/issues/6025 15:30:45 #info dkliban has joined triage 15:30:45 !here 15:30:45 dkliban: dkliban has joined triage 15:30:51 #info daviddavis has joined triage 15:30:51 !here 15:30:51 daviddavis: daviddavis has joined triage 15:31:05 #idea Proposed for #6025: Leave the issue as-is, accepting its current state. 15:31:05 !propose accept 15:31:05 fao89: Proposed for #6025: Leave the issue as-is, accepting its current state. 15:31:37 #idea Proposed for #6025: accept and add to sprint 15:31:37 !propose other accept and add to sprint 15:31:37 dkliban: Proposed for #6025: accept and add to sprint 15:31:45 +1 15:31:53 #agreed accept and add to sprint 15:31:53 !accept 15:31:53 fao89: Current proposal accepted: accept and add to sprint 15:31:54 #topic https://pulp.plan.io/issues/6016 15:31:54 fao89: 2 issues left to triage: 6016, 5991 15:31:55 RM 6016 - daviddavis - ASSIGNED - pulp_file nightly builds are failing 15:31:56 https://pulp.plan.io/issues/6016 15:32:10 accept and add to sprint. this is being worked on already. 15:32:10 is this about to be resolved daviddavis ? 15:32:14 sweet 15:32:18 yea actually 15:32:18 +1 15:32:20 #idea Proposed for #6016: accept and add to sprint 15:32:20 !propose other accept and add to sprint 15:32:21 fao89: Proposed for #6016: accept and add to sprint 15:32:28 #agreed accept and add to sprint 15:32:28 !accept 15:32:28 fao89: Current proposal accepted: accept and add to sprint 15:32:29 #topic https://pulp.plan.io/issues/5991 15:32:29 fao89: 1 issues left to triage: 5991 15:32:30 RM 5991 - jsherril@redhat.com - NEW - Sync fails with TypeError: unsupported operand type(s) for -=: 'Retry' and 'int' 15:32:31 https://pulp.plan.io/issues/5991 15:32:52 daviddavis: did we ever hear about python requests version? 15:33:06 no https://community.theforeman.org/t/foreman-proxy-content-not-synchronising/16774/6 15:33:07 #info bmbouter has joined triage 15:33:07 !here 15:33:07 bmbouter: bmbouter has joined triage 15:33:26 it's only been 4 days though. maybe wait a bit longer? 15:33:34 yeah ... we can wait till friday 15:33:45 #info dawalker has joined triage 15:33:45 !here 15:33:45 dawalker: dawalker has joined triage 15:33:47 +1 to wait 15:33:52 #idea Proposed for #5991: Skip this issue for this triage session. 15:33:52 !propose skip 15:33:52 daviddavis: Proposed for #5991: Skip this issue for this triage session. 15:33:55 +1 15:33:59 #agreed Skip this issue for this triage session. 15:33:59 !accept 15:33:59 fao89: Current proposal accepted: Skip this issue for this triage session. 15:34:00 fao89: No issues to triage. 15:34:07 Open floor! 15:35:53 FYI the plugin_template is moving towards all bindings based tests thanks to fao89 15:36:14 I was thinking, after we start to use bindings on functional tests, we should provide bindings on installer 15:36:54 I opened this issue #6032 for it 15:36:58 !issue 6032 15:36:59 #topic https://pulp.plan.io/issues/6032 15:36:59 RM 6032 - fabricio.aguiar - NEW - As a user I can run functional tests locally 15:37:00 https://pulp.plan.io/issues/6032 15:37:02 fao89: just for developers ? 15:37:37 fao89: cool, yeah we want to make it easy to use, but in user installations the system with the pulp server components (targetted by the installer) and the place the bindings run (the user's local machine) are usually different 15:37:51 still having the installer able to build them would be prbably helpful 15:37:59 also I think we have to [re]generate bindings on the fly too 15:38:03 yeah ... i think we want this in our dev environments 15:38:16 yes we do! 15:38:24 daviddavis: what about a bash function like pstart for doing tihs? 15:38:28 +1 15:38:31 I just thought that because what I had to do to test pulp_catdog locally 15:39:19 yeah ... we definiely want to easily test locally 15:39:21 as pulp_catdog isn't on pypi, I had to do all the steps for generating the bindings 15:39:37 yeah let's make that easier 15:39:47 yeah ... we should add the ability for a developer to easily generate python bindings 15:40:11 right now we have a repo called pulp-openapi-generator that enables this 15:40:33 yup and I see the CI fail for that regularly I was concerned about that 15:40:41 I'm not sure what the fialure causes are 15:41:30 bmbouter: it was fixed and then broke agian 15:41:44 anyway, fao89, i'll comment on the issue again with what we just discussed 15:41:58 dkliban: ty and ty 15:42:07 thanks! 15:42:19 fao89: ty for filing! 15:44:55 https://pulp.plan.io/issues/6032#note-3 15:45:23 dkliban++ 15:45:23 fao89: dkliban's karma is now 411 15:45:44 I think we should maybe add this to this/a sprint soon 15:46:02 if we start writing bindings tests, it's going to be hard to run them without this 15:46:20 i agree 15:46:41 I'll mark as a sprint candidate but I'm also happy to add it to this sprint 15:47:16 I also agree 15:47:19 +1 15:47:36 add to sprint because we need to reach that goal of bindings tests 15:47:41 (is my opinion) 15:48:21 ok, let's add to the sprint 15:48:45 !propose add to sprint 15:48:45 fao89: Error: "propose" is not a valid command. 15:48:54 might it be worthwhile to put totally-generic bindings test functions in pulpcore.app.tests.utils instead of a separate package 15:48:56 #idea Proposed for #6032: add to sprint 15:48:56 !propose other add to sprint 15:48:56 fao89: Proposed for #6032: add to sprint 15:49:20 #agreed add to sprint 15:49:20 !accept 15:49:20 fao89: Current proposal accepted: add to sprint 15:49:21 fao89: No issues to triage. 15:49:47 dalley: like the one that does the task monitoring? 15:49:53 exactly 15:50:03 that's the one I specifically had in mind :) 15:50:24 dalley: we can do that for now ... but i would like to just add it to the bindings when we are generating them 15:51:01 so the Python bindings at least would come with the helper method 15:51:19 that makes sense too, that would go into the pulpcore bindings? 15:51:24 yeah 15:51:40 we should file an issue for this 15:51:41 probably a better long-term solution to do that, yeah 15:52:02 bmbouter: did you file anything like that? i know we talked about it before 15:53:07 I put monitor_task on plugin.tests.functional.utils here - https://github.com/pulp/plugin_template/pull/175 15:54:27 that's good for right now 15:56:00 i'll write up an issue to improve the python bindings 15:57:57 jsherrill: does katello test this https://pulp.plan.io/issues/6025 ? 15:58:21 any other issue for open floor? 16:00:05 #endmeeting 16:00:05 !end