Jump to: navigation, search

Difference between revisions of "Meetings/Swift"

Line 3: Line 3:
 
! '''2100 UTC Meeting'''
 
! '''2100 UTC Meeting'''
 
|-
 
|-
| '''Next meeting:''' Nov 30th, 2022
+
| '''Next meeting:''' Dec 14th, 2022
 
|-
 
|-
 
| '''Location:''' #openstack-swift on OFTC
 
| '''Location:''' #openstack-swift on OFTC
Line 11: Line 11:
 
|
 
|
 
<!-- List 2100UTC meeting items below here -->
 
<!-- List 2100UTC meeting items below here -->
* CPython broke our func tests
+
* CPython parse_request bug
 
** https://github.com/python/cpython/issues/99220 | BaseHTTPRequestHandler.parse_request() loses client-provided information
 
** https://github.com/python/cpython/issues/99220 | BaseHTTPRequestHandler.parse_request() loses client-provided information
 
*** Still no response :-/
 
*** Still no response :-/
 +
** Causing failures in our stable branches (eg, https://review.opendev.org/c/openstack/swift/+/861763)
 
** DSVM job is currently pinned to focal: https://review.opendev.org/c/openstack/swift/+/864946
 
** DSVM job is currently pinned to focal: https://review.opendev.org/c/openstack/swift/+/864946
 
** https://review.opendev.org/c/openstack/swift/+/863441 | Preserve client-provided paths that start '//'
 
** https://review.opendev.org/c/openstack/swift/+/863441 | Preserve client-provided paths that start '//'
*** Has one +2, any objections?
+
** https://review.opendev.org/c/openstack/swift/+/866801 | Inline parse_request from cpython
 
* Testing under py310
 
* Testing under py310
** https://review.opendev.org/c/openstack/requirements/+/863581/ | Add new dependency: pytest-cov
 
*** Still current blocker; just pinged to see if we can move forward on it
 
* We helped find a cpython 3.11.0 bug!
 
** zigo first discovered it: https://meetings.opendev.org/irclogs/%23openstack-swift/%23openstack-swift.2022-11-24.log.html
 
** timburke eventually tracked it down and wrote up https://github.com/python/cpython/issues/99886
 
** Looks like there will probably be a fix for 3.11.1: https://github.com/python/cpython/pull/99902
 
** Is it worth us making changes in swift to avoid the segfault? https://review.opendev.org/c/openstack/swift/+/866051 seems to cover it, but if it only impacts one cpython release...
 
 
* ring v2
 
* ring v2
 
** https://review.opendev.org/c/openstack/swift/+/865066 | WIP: Rings as zipfiles
 
** https://review.opendev.org/c/openstack/swift/+/865066 | WIP: Rings as zipfiles

Revision as of 21:01, 14 December 2022

2100 UTC Meeting
Next meeting: Dec 14th, 2022
Location: #openstack-swift on OFTC
Chair: timburke
Meeting Logs http://eavesdrop.openstack.org/meetings/swift/2022/
Useful Commands #link #info #agreed #topic and #startmeeting

When adding an item, please include your IRC nickname with it.