21:00:18 <timburke> #startmeeting swift
21:00:18 <opendevmeet> Meeting started Wed Jun 21 21:00:18 2023 UTC and is due to finish in 60 minutes.  The chair is timburke. Information about MeetBot at http://wiki.debian.org/MeetBot.
21:00:18 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:00:18 <opendevmeet> The meeting name has been set to 'swift'
21:00:25 <timburke> who's here for the swift meeting?
21:00:31 <kota> hi
21:01:08 <acoles> o/
21:01:51 <timburke> i *did* remember to update the agenda! (though only just now)
21:01:54 <timburke> #link https://wiki.openstack.org/wiki/Meetings/Swift
21:01:59 <timburke> first up
21:02:09 <timburke> #topic ssync metadata corruption bug
21:02:34 <timburke> #link https://review.opendev.org/c/openstack/swift/+/884240
21:02:43 <timburke> has the fix
21:02:51 <timburke> but it could use reviews
21:04:13 <timburke> #link https://review.opendev.org/c/openstack/swift/+/884954
21:04:30 <timburke> is a follow-on to update a probe test, but i'd like a little more consensus about switching to direct client instead of going through the proxy. if we have that consensus, i'm fine with squashing it into the fix
21:06:21 <acoles> IIUC that is to avoid a swiftclient bug?>
21:07:51 <timburke> yep -- py3 stdlib won't parse non-ascii header names correctly
21:09:48 <timburke> i think i looked into working around it, but eventually gave up -- too many layers to cut through, and it's especially difficult to do it in a way that doesn't involve monkeypatching stdlib for *everything*
21:10:05 <timburke> (which seems risky for client code)
21:10:32 <acoles> ok
21:10:56 <mattoliver> Sorry im late
21:12:17 <timburke> can anyone volunteer to review the fix?
21:14:25 <acoles> I will
21:15:09 <timburke> thanks, acoles. and maybe i can hunt down the bug reporter, have him try the fix and report back 😁
21:15:23 <mattoliver> I'm still catching up on things, and stuck down a rabbithole at work, but can add it to my todo.
21:15:42 <timburke> #topic get info backend request logging/metrics
21:15:56 <timburke> #link https://review.opendev.org/c/openstack/swift/+/884931
21:16:31 <timburke> acoles and jian have done some reviews, thanks guys!
21:17:19 <timburke> there was a point at which i had it in a place that it didn't actually fix things, but i think it's in a good place again now
21:17:46 <timburke> so if you get a chance, i'd appreciate some fresh eyes on it. and thanks again for the new tests, acoles!
21:18:23 <acoles> NP
21:18:31 <timburke> #topic py311 support
21:18:36 <acoles> yes I will take another look
21:19:18 <timburke> i took a bit of time the last week or so to get to the point of having tests pass on py311
21:19:50 <timburke> culminating in having a passing gate job!
21:19:52 <timburke> #link https://review.opendev.org/c/openstack/swift/+/886541
21:20:39 <timburke> there are a few pre-req patches to fix up some tests, but zaitcev has been quick to review & approve (thanks!)
21:20:53 <zaitcev> Sure.
21:21:07 <mattoliver> Oh nice
21:21:10 <timburke> i maybe should have proposed them as separate changes, with a Depends-On in the CI change to bring them all together
21:21:17 <zaitcev> I may not know how sharding works, but I know what a subclass is in Python.
21:22:07 <timburke> 'cause the base of the chain could probably use a bit of work (better commit message, bug report, probably even an upstream python bug)
21:23:44 <timburke> note that the gate job is still using jammy, which has got a 3.11.0 RC, so it still needed the __slots__ workaround for the segfault
21:24:28 <timburke> next up
21:24:34 <timburke> #topic tagged metrics
21:25:16 <timburke> i forget if i'd mentioned it before, but i finally got a patch up to try out some statsd extensions for labeled metrics
21:25:23 <timburke> #link https://review.opendev.org/c/openstack/swift/+/885321
21:26:10 <mattoliver> I'm really interested in checking it out! I was off last week, so will try and get around to poking around it this week
21:27:21 <timburke> i'd really appreciate it if people could take a look at how it affects the calling code in something like proxy-logging, say, before i get too far into fixing up tests and such
21:27:51 <indianwhocodes> sorry im late
21:27:53 <timburke> and i still need to get some docs together about how to try it out in a SAIO
21:28:25 <mattoliver> The docs would be good
21:28:55 <timburke> all right, that's all i've got
21:29:00 <timburke> #topic open discussion
21:29:06 <timburke> anything else we should bring up?
21:29:12 <acoles> exciting!
21:29:23 <acoles> labeled metrics I mean :)
21:30:16 <mattoliver> I got nothing this week
21:31:35 <timburke> it's been like 3 months since our last release, i should put another one together
21:31:58 <timburke> if anyone has patches they feel should be sure to get into the next release, please let me know!
21:32:08 <mattoliver> Kk
21:33:10 <timburke> all right, i think i'll call it then
21:33:20 <timburke> thank you all for coming, and thank you for working on swift!
21:33:24 <timburke> #endmeeting