21:00:12 <timburke> #startmeeting swift
21:00:12 <opendevmeet> Meeting started Wed Feb  7 21:00:12 2024 UTC and is due to finish in 60 minutes.  The chair is timburke. Information about MeetBot at http://wiki.debian.org/MeetBot.
21:00:12 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:00:12 <opendevmeet> The meeting name has been set to 'swift'
21:00:18 <timburke> who's here for the swift meeting?
21:00:42 <mattoliver> o/
21:00:48 <acoles> o/
21:00:52 <mattoliver> I got the time right today!
21:01:08 <timburke> 🎉
21:02:18 <timburke> i neglected to update the agenda, but we can start with updates on last week's items
21:02:26 <timburke> #topic swiftclient reviews
21:03:03 <timburke> acoles reviewed p 904652; sounds like yan will be addressing comments later this week
21:03:03 <patch-bot> https://review.opendev.org/c/openstack/swift/+/904652 - swift - Add ClosingIterator class; be more explicit about ... - 7 patch sets
21:03:50 <timburke> i didn't get to poking at the path-normalization bug, unfortunately
21:04:12 <timburke> clayg helped characterize the issue in https://review.opendev.org/c/openstack/python-swiftclient/+/907118
21:04:12 <patch-bot> patch 907118 - python-swiftclient - WIP: test for invalid segment name - 3 patch sets
21:04:42 <timburke> #topic s3 compat
21:05:33 <timburke> the part number patches are still in review, but seem likely to merge soon-ish
21:05:55 <timburke> on the follow-ups, i think https://review.opendev.org/c/openstack/swift/+/906906 should probably get squashed into the main s3api patch
21:05:55 <patch-bot> patch 906906 - swift - s3api: return 400 if partNumber and Range sent - 3 patch sets
21:06:18 <timburke> while https://review.opendev.org/c/openstack/swift/+/906391 can probably continue to be a follow-up
21:06:19 <patch-bot> patch 906391 - swift - slo: Support range requests for part-number queries - 2 patch sets
21:06:48 <acoles> sounds like a plan
21:06:50 <timburke> acoles also wrote up some more MPU cross-compat tests: https://review.opendev.org/c/openstack/swift/+/907751
21:06:50 <patch-bot> patch 907751 - swift - WIP s3api: add more MPU cross-compat  tests - 1 patch set
21:07:10 <mattoliver> kk, I promise to get to review these myself over the next week. They are on my list.. just never seem to get to them
21:07:59 <acoles> I marked the cross-compat test patch as WIP: not all tests pass with Swift s3api
21:08:10 <timburke> i've been poking at them as something detached from the chain, and have it down from 8 failures to 5 -- we'll see what i can do for the rest
21:08:40 <acoles> I don't plan to immediately address those failures (they're not data-path related discrepancies)
21:09:20 <acoles> Instead, I'm trying to make progress towards an all-new swift s3api MPU implementation, but it's very early days
21:09:48 <timburke> it'll be great :D
21:11:41 <timburke> while i'm still on the topic of s3 compat, i still haven't done much with https://review.opendev.org/c/openstack/swift/+/836755 but want to dig in more over the next week
21:11:42 <patch-bot> patch 836755 - swift - Add support of Sigv4-streaming - 8 patch sets
21:12:33 <timburke> #topic py312
21:12:43 <timburke> acoles merged https://review.opendev.org/c/openstack/swift/+/904601 (thanks!)
21:12:44 <patch-bot> patch 904601 - swift - tests: Fix float expectations for py312 (MERGED) - 5 patch sets
21:13:41 <acoles> 👌
21:14:05 <mattoliver> Speaking of py312, when having 312 as your default tox pep8 fails as it pulls in a later version of something, pinning it doesn't fix it.
21:14:05 <timburke> and i think we're lined up to continue pushing on https://review.opendev.org/c/openstack/swift/+/904652 (which may help with some other issues we've seen on py37 🤞)
21:14:05 <patch-bot> patch 904652 - swift - Add ClosingIterator class; be more explicit about ... - 7 patch sets
21:15:01 <mattoliver> importlib-metadata > 5 removed an api that flake8 uses.
21:15:03 <timburke> mattoliver, oh boo -- i think i hadn't tried linting yet, just tests
21:15:26 <mattoliver> I could set a basepython to <312 in tox and it fixes it.
21:15:37 <mattoliver> But that isn't great.
21:16:32 <mattoliver> So might need to check on the status of flake8 upstream and see if they're working on using the new importlib-metadata api
21:16:47 <mattoliver> raise an issue or maybe even fix it myself 🤷
21:18:38 <timburke> i wonder if maybe it's down to the version pins hacking uses 🤔
21:19:05 <mattoliver> Because my default python is 312 (thanks to fedora) I might continue chasing this down because it bugs and effects me most.
21:19:48 <timburke> i also remembered recently that there's 312 work outside of swift -- we want https://review.opendev.org/c/openstack/pyeclib/+/839643 to get pyeclib tests working
21:19:48 <patch-bot> patch 839643 - pyeclib - Drop support for liberasurecode<1.4.0 - 10 patch sets
21:20:05 <mattoliver> maybe, I went in an forced a pin to the right version, but then it complained about wanting 2 versions of the module.. so yeah either something else is pulling it in, or is packaged/coming with my py312
21:20:24 <mattoliver> oh yeah. I forget about those repos.
21:20:25 <timburke> (because of the deprecation called out in the commit message; py312 made good on the promise to remove)
21:21:43 <timburke> but it'll also be really nice to finally close #1639691!
21:21:44 <patch-bot> https://bugs.launchpad.net/swift/+bug/1639691 - EC: Swift can return corrupted Data and be able to go data lost at isa_l_rs_vand policy with >=5 parities (Fix Released)
21:22:55 <timburke> i think that's it for updates from last week
21:23:05 <timburke> #topic open discussion
21:23:14 <timburke> anything else we want to bring up here?
21:23:35 <acoles> not from me
21:24:08 <mattoliver> Thanks to acoles p 809969 has been reworked and much better
21:24:08 <patch-bot> https://review.opendev.org/c/openstack/swift/+/809969 - swift - sharding: don't replace own_shard_range without an... - 15 patch sets
21:24:52 <acoles> I wonder if we'll get any hint as to the mystery epoch-resetting bug?
21:25:45 <mattoliver> yeah no idea. I mean the reason we added device name to db_ids was a hope to find the culprit.
21:25:54 <mattoliver> Also now that the namespace and container auto get patches have landed. I'm reworking p 877584
21:25:55 <patch-bot> https://review.opendev.org/c/openstack/swift/+/877584 - swift - internal_client: Add iter_{shard_ranges,namespaces... - 12 patch sets
21:26:51 <mattoliver> Still working it through, but there is now an iter_shardranges and iter_namespace that do to the backends. And now also have a iter_namespaces_from_cache which only attempt to pull from cache (if enabled). Return nothing on cache_miss
21:27:03 <mattoliver> which will be useful for smartening up the object updater
21:28:01 <mattoliver> Last night I had to make dinner so quickly pushed up what I had. Almost have a more polished one to push up now. maybe after the meeting
21:28:05 <timburke> i like smarter daemons :-)
21:29:12 <timburke> all right, i think we'll call it early then
21:29:17 <mattoliver> oh and I still have p 905064 lingering, but thats probably more on me :)
21:29:17 <patch-bot> https://review.opendev.org/c/openstack/swift/+/905064 - swift - wip: shard replication sync points - 5 patch sets
21:29:22 <mattoliver> yup, that's all I got :)
21:29:30 <timburke> thanks for coming, and thank you for working on swift!
21:29:33 <timburke> #endmeeting