Wednesday, 2022-12-07

opendevreviewTim Burke proposed openstack/swift master: Inline parse_request from cpython  https://review.opendev.org/c/openstack/swift/+/86680100:27
opendevreviewTim Burke proposed openstack/swift master: Move non-ascii header parsing into parse_request()  https://review.opendev.org/c/openstack/swift/+/86681300:27
opendevreviewMatthew Oliver proposed openstack/swift-bench master: refactor bin/bench into swiftbench/cli for testing  https://review.opendev.org/c/openstack/swift-bench/+/86682606:59
opendevreviewTim Burke proposed openstack/swift master: Move non-ascii header parsing into parse_request()  https://review.opendev.org/c/openstack/swift/+/86681320:05
opendevreviewTim Burke proposed openstack/swift master: Take on header parsing ourselves  https://review.opendev.org/c/openstack/swift/+/86693420:05
kotagood morning20:58
seongsoochogood morning!20:59
kotaseongsoocho: o/20:59
seongsoocho\o/21:00
mattolivermorning21:01
acoleso/21:03
mattoliverso we just need a timburke 21:04
timburkeoh, right!21:06
timburke#startmeeting swift21:06
opendevmeetMeeting started Wed Dec  7 21:06:49 2022 UTC and is due to finish in 60 minutes.  The chair is timburke. Information about MeetBot at http://wiki.debian.org/MeetBot.21:06
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:06
opendevmeetThe meeting name has been set to 'swift'21:06
timburkelooks like we've already got people here for a swift meeting :-)21:07
mattoliveryup :)21:07
timburkei neglected to update the agenda, but mostly i just wanted to give updates on last week's items, anyway21:08
timburke#topic leading slashes bug21:08
timburkeclayg pushed back on continuing to hack do pre/post processing, instead thinking that just inlining (and fixing) parse_request may be better21:09
timburkei finally got around to trying that approach -- and i'm torn about which one i prefer21:10
timburke#link https://review.opendev.org/c/openstack/swift/+/86680121:10
timburke^^^ inlines and fixes up parse_request21:10
timburke#link https://review.opendev.org/c/openstack/swift/+/86344121:11
timburke^^^ undoes the change with some post-processing21:11
mattoliverI guess there is a bigger maintainence burden on the latter approach.. but the other is trying to fix things in potentually odd spots. 21:11
mattolivereither way, the initial refactor http protocol stuff is nice :) 21:12
timburkethe inlining did give me the opportunity to clean up some other hacks we had (specifically, by addressing https://bugs.python.org/issue33973 in a much more direct way)21:12
timburkeand the function itself hasn't seen *that many* updates in the past ten years or so, looking at main21:13
mattoliverOK well that's promising. Not too much of a maintence burden if it doesn't change too much21:14
acolestimburke: thanks for doing more work! I haven't had chance to look at the second approach yet21:14
timburkeotoh, there's a whole bunch more branches now present in our code that are likely untested, and it seems unlikely that we'd notice any upstream changes to the function in the future (so when there's inevitably another patch in a couple years, we won't even know to think about whether to apply it)21:15
mattoliverneed a monthly zuul git diff job :P 21:17
acolesmattoliver: volunteering ;-)21:17
timburkemattoliver, there's enough of a delta between us and upstream that i'm not sure how helpful that would be... though maybe diffing between upstream revisions could work well enough?21:17
mattoliverwell maybe no diff from what we have, but from current master of eventlet is. 21:18
mattoliveror whatever. so we can detect changes21:18
mattoliveror a git blame, or just an md5 check21:18
mattoliver(me is thinking out loud)21:18
timburkei also proposed a couple follow-ons -- the first moves another stdlib-workaround to parse_request, so we don't have to repeat a bunch of work that eventlet's doing; the second removes the need for the workaround entirely21:19
timburkeso if you get a chance, take a look at the new approach, see which way you prefer. i think we *do* still need to do *something* -- there are just too many versions of python in the wild that break us, and no traction from upstream to fix it21:21
timburkeand it'd be nice to have even our non-voting jobs green as we do some other CI maintenance stuff21:22
timburkespeaking of...21:22
timburke#topic pytest21:22
timburkestill no further feedback on the requirements change that's blocking us moving to pytest, which in turn is blocking us from testing on py310 in the gate21:23
timburke#link https://review.opendev.org/c/openstack/requirements/+/863581/21:23
timburkei'll continue to badger people about that21:24
mattoliverthanks for that21:24
timburkebut i also recently refreshed some gate results, and it looks like i might need to respin a bit anyway (some dependency errors around py2 probe tests)21:24
mattoliverahh py2 :( 21:25
kota:/21:25
timburke#topic py311 segfault21:25
timburkeupstream *did* respond quickly on https://github.com/python/cpython/issues/99886 -- the fix is merged, so it looks like there's just the one upstream release affected21:26
mattoliveroh cool21:26
kotanice21:27
mattolivergreat job timburke 21:27
timburkeunit tests still fail on py311, though, so some of https://review.opendev.org/c/openstack/swift/+/866051 will still be necessary (just not necessarily the __slots__)21:27
timburkei'll respin it soon; it should be even more targeted now that https://review.opendev.org/c/openstack/swift/+/866239 has landed21:28
timburkethat's all i've got21:29
timburke#topic open discussion21:29
timburkeanything else we should bring up this week?21:29
timburkein that case, we'll wrap up early :-)21:31
timburkethank you all for coming, and thank you for working on swift!21:32
timburke#endmeeting21:32
opendevmeetMeeting ended Wed Dec  7 21:32:14 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:32
opendevmeetMinutes:        https://meetings.opendev.org/meetings/swift/2022/swift.2022-12-07-21.06.html21:32
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/swift/2022/swift.2022-12-07-21.06.txt21:32
opendevmeetLog:            https://meetings.opendev.org/meetings/swift/2022/swift.2022-12-07-21.06.log.html21:32
mattoliverhey indianwhocodes 21:33
indianwhocodesi am late21:33
mattoliverthats ok, at least you made it :) 21:33
timburkeo/21:34
mattolivermeetings are weekly around this time. or rather starting on the hour 30 mins ago 2100 UTC, 1pm your time I think21:34
timburkethough it shifts in the summer :-)21:35
mattoliverbut there are minutes if you ever miss one21:35

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