GitHub PushEvent at 2014-07-09 16:47:29
Repository: swift
Actor: notmyname
Payload: {"shas":[["fb5a0f21ddfde12f503c4a7048d8b8ca1c2724ef","5908cf536e9267f3c74e45326928d92a7461a903@gmail.com","Fix KeyError on Storage Policy Container Sync\n\nIn the proxy, container_info can return a 'storage_policy' of None.  When\nyou set a header value on a swob.Request to None that effectively just\ndelete's the key.  One path through the proxy during container sync was\ncounting on the the 'X-Backend-Storage-Policy-Index' being set which isn't\nthe case if the cached container_info if for a pre-policies container.\n\nAlso clean up some test cruft, tighten up the interface on FakeConn, and add\nsome object controller tests to exercise more interesting failure and handoff\ncode paths.\n\nChange-Id: I643e08c208efdc5a39e840d9e96710ddad54236b","Clay Gerrard",true],["7dbf8324569d45897f2b4f05cd97299366eff23d","5908cf536e9267f3c74e45326928d92a7461a903@gmail.com","Fix pop_queue for move object twice\n\nWith the two vector timestamp change some resolution was lost in the queue\nentries that could lead to the reconciler being unable to successfully remove\na processed item from the queue in pop_queue.  To ensure the queue entries\nwith a significant offset can be successfully removed while still handling\nthe re-enqueued object case issue the DELETE with the timestamp slightly later\nthan the maximum of the queue entries last modified time (q_record) and\nmisplaced objects timestamp (q_ts).\n\nChange-Id: I87b1e4b4256af3f71defb58c8137c303d1ae63be","Clay Gerrard",true],["bfa9139649c0ac7f75e8c9503cb04d06f7bae0b9","406c10c87a7387f3d87f3c8a56f16d3548de329c@intel.com","Fix potential missing key error in container_info\n\nIf upgrading from a non-storage policy enabled version of\nswift to a storage policy enabled version its possible that\nmemcached will have an info structure that does not contain\nthe 'storage_policy\" key resulting in an unhandled exception\nduring the lookup.  The fix is to simply make sure we never\nreturn the dict without a storage_policy key defined; if it\ndoesn't exist its safe to make it '0' as this means you're\nin the update scenario and there's xno other possibility.\n\nChange-Id: If8c88f67ba7a3180ad06b586372fe35c65807aac","Paul Luse",true],["0582db728fa5931cae143014a9b3ac1205a23855","3404eea32e9177bb048b952e9c5ff377a6f62085@brim.net","This setting should've been set to False back ...\n\n...with commit 9eb797b09916574c2a4e0f5f9ea61fe120879075\n\nWith this setting to True in the code, any tools anyone writes will\nautomatically start preallocating, which is almost always bad these days\nwith SSDs. So, if you write a tool that just scan dbs for stats, it'll\ncommit any pending info triggering preallocation and bam, your SSDs\nstart to fill up. :/\n\nAnyway, back when I wrote 9eb797b09916574c2a4e0f5f9ea61fe120879075 it\nwas my intention to have this off by default, everywhere; I changed all\nthe settings points but I failed to change the dang constant itself.\nThis corrects that.\n\nChange-Id: Iada0a3f1ecfabda4a96f574903d8e2eed1f69064","gholt",true],["b7def1c5c3a31f9b1b5e2bb6c14e3a4920246a15","d95b56ce41a2e1ac4cecdd398defd7414407cc08@review.openstack.org","Merge \"This setting should've been set to False back ...\"","Jenkins",true],["03a40b514a43142fa57f194f8793122ef4643378","b1c1d8736f20db3fb6c1c66bb1455ed43909f0d8@not.mn","Merge tag '2.0.0'\n\nSwift 2.0.0 release\n\nChange-Id: I5fdc1e7434bdf6d88c4b260798791ee59f0832c0","John Dickinson",true]],"size":6,"ref":"refs/heads/master","head":"03a40b514a43142fa57f194f8793122ef4643378"}