)]}'
{"swift/container/sharder.py":[{"author":{"_account_id":7233,"name":"Matthew Oliver","email":"matt@oliver.net.au","username":"mattoliverau"},"change_message_id":"1cf895b62dd7d80742e98e1a72ca8e0a2c77a0ba","unresolved":true,"context_lines":[{"line_number":264,"context_line":"        if (index \u003d\u003d len(shard_ranges) and"},{"line_number":265,"context_line":"                len(shard_ranges) \u003d\u003d len(sequence) and"},{"line_number":266,"context_line":"                not sequence_complete(sequence) and"},{"line_number":267,"context_line":"                sequence.includes(own_shard_range)):"},{"line_number":268,"context_line":"            # special case: only one sequence has been found, which consumes"},{"line_number":269,"context_line":"            # all shard ranges, encompasses the entire namespace, has no more"},{"line_number":270,"context_line":"            # than merge_size records and whose shard ranges are all"}],"source_content_type":"text/x-python","patch_set":1,"id":"0aa8d389_d5e0d0dc","line":267,"updated":"2021-03-01 02:17:34.000000000","message":"Yeah, that seems safer, I\u0027d rather have things not collapsed even if the active states \"should\" fit if there are other shardranges in other states that may confuse things, esp if we go ahead an collapse.\n\nGiven enough time, other states should fix themselves, things in FOUND and CREATED states would get ACTIVE And then SHRINK away. SHARDING will get deleted once sharded. And SHARDED should get deleted too. So things shouldn\u0027t get stuck in a non-collaible state.. I think. But maybe a warning could be useful, or maybe something to add to audit (collecting these \"could\" be interesting state warnings.","commit_id":"01dec1240e58c9f94094ffa9a9675e908d57a049"}]}