)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":1179,"name":"Clay Gerrard","email":"clay.gerrard@gmail.com","username":"clay-gerrard"},"change_message_id":"82ca066cfdbc1b7b183cc9b39379446cd3715410","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"bb9e080d_fb0cd81d","updated":"2026-07-31 17:05:34.000000000","message":"I\u0027m not REALLY sure this is a good solution, we might want to at LEAST log the TypeError - I\u0027m not sure I understand why the ValueError doesn\u0027t log, I think either case should be exceptional\n\n```\n  Unhandled exception while dumping progress: CleavingContext.__init__() got an\n  unexpected keyword argument \u0027replication_count\u0027, path:\n  .shards_AUTH_\u003cACCOUNT\u003e/\u003cCONTAINER\u003e, db:\n  /srv/node/\u003cDEVICE\u003e/containers/45732/966/b2a49389bdfe3fc28d93a69c4180d966/\n  b2a49389bdfe3fc28d93a69c4180d966_1767733522.28590.db:\n  Traceback (most recent call last):\n    File \"/opt/ss/lib/python3.10/site-packages/swift/container/sharder.py\",\n    line 2590, in _one_shard_cycle\n      self._record_sharding_progress(broker, node, error,\n    File \"/opt/ss/lib/python3.10/site-packages/swift/container/sharder.py\",\n    line 1024, in _record_sharding_progress\n      contexts \u003d CleavingContext.load_all(broker)\n    File \"/opt/ss/lib/python3.10/site-packages/swift/container/sharder.py\",\n    line 697, in load_all\n      contexts.append((cls(**json.loads(val)), timestamp))\n  TypeError: CleavingContext.__init__() got an unexpected keyword argument\n  \u0027replication_count\u0027\n```\n\nI\u0027m sure we can\u0027t just quarantine the whole database for invalid/unexpected/upgraded metadata - but I hear that it\u0027s reasonable to \"ignore\" them from load_all since one of it\u0027s callers is responsible for reclaim?","commit_id":"36a1081c43f63d11da1307cc756ef21b7a32aa18"}]}