{"push_id":946010858,"size":14,"distinct_size":7,"ref":"refs/heads/feature/python35","head":"c1ba582f2ab2e091f250406586ddeef6eca2c4ef","before":"30f8317838a2e984e54fe22042fd3ffff10f82e6","commits":[{"sha":"4c9cf9efe0ac76912f372d771c3fe6deaec29863","author":{"email":"a87bd3f83b957b5cd3f29a1a2c102fe50c2bf8df@gmail.com","name":"Chris Seto"},"message":"Merge branch 'hotfix/0.14.3'","distinct":false,"url":"https://api.github.com/repos/TomBaxter/waterbutler/commits/4c9cf9efe0ac76912f372d771c3fe6deaec29863"},{"sha":"fe7d33dd429deeae9ca5263c7a7063d6da1cf06c","author":{"email":"3ca23a7ddfc3de21c7d8437663fcac27d7618d41@cos.io","name":"Fitz Elliott"},"message":"s3: support periods in bucketnames for all regions\n\nA bogus error message in the OSF S3 addon revealed some shenanigans\nin how we handle bucket names outside the US (N. Virginia) region.\nAmazon permits bucket names that follow subdomain-naming conventions\n(labels separated by periods).  WB had been accessing buckets using\nthe subdomain calling format, which would access a bucket named 'foo'\nat `https://foo.s3.amazonaws.com/`.  However, wildcard nested\nsubdomain certificates are deprecated, and Pythons newer than 2.7.9\nwill throw a certificate checking error if you try to access them.\nIOW a bucket named 'foo' will still work, but a bucket named 'foo.bar'\nwill try to connect to `https://**foo.bar**.s3.amazonaws.com/` and\nwill fail validation.\n\n`boto`, the library WB uses to communicate with S3, supports another\ncalling format that avoids this issue, the `OrdinaryCallingFormat`.\nUnder OCF, a call to a bucket named `foo.bar` is directed to\n`https://s3.amazonaws.com/foo.bar/`, and so the certificate will pass\nvalidation.  The catch is that buckets in regions outside US\n(N. Virginia) require the request to be sent to a region-specific URL.\nThe OSF doesn't currently track the bucket's region, so WB has to\nlook it up via the S3 API.  Once we have the region, we can update the\nhost, and all S3 actions should succeed.\n\nFixes: [#OSF-5509]\n\nReferences:\n----\n\n* [S3 naming conventions](http://docs.aws.amazon.com/AmazonS3/latest/dev/BucketRestrictions.html#bucketnamingrules)\n* [S3 bucket region lookup](http://docs.aws.amazon.com/AmazonS3/latest/API/RESTBucketGETlocation.html)","distinct":false,"url":"https://api.github.com/repos/TomBaxter/waterbutler/commits/fe7d33dd429deeae9ca5263c7a7063d6da1cf06c"},{"sha":"c762dc5a607c700c2aa9d39e5dcf15ee0e7731ed","author":{"email":"3ca23a7ddfc3de21c7d8437663fcac27d7618d41@cos.io","name":"Fitz Elliott"},"message":"fix modified timestamps from filesystem provider\n\nWhen running a local dev copy of WB, the modified timestamp returned\nfrom file metadata was for the local time, and lacked an explicit\ntimezone attachment.  When the file metadata is stored in mongo, mongo\nassumes it is Zulu time.  This was causing erroneous and mismatched\nmodified and created times for osfstorage.\n\nThis branch updates filesystem to return a utc datetime with an active\ntimezone object.  It also updates two tests that weren't being explicit\nabout their timezone.  Those tests worked fine without the tzinfo, but\nwe need to start being more disciplined about this.","distinct":false,"url":"https://api.github.com/repos/TomBaxter/waterbutler/commits/c762dc5a607c700c2aa9d39e5dcf15ee0e7731ed"},{"sha":"8553accb65b494231ae351c4aaccf3efa96d9dd1","author":{"email":"3ca23a7ddfc3de21c7d8437663fcac27d7618d41@cos.io","name":"Fitz Elliott"},"message":"Merge branch 'hotfix/0.14.4'\n\n * v1 move/copy actions were swapping source and destination log targets\n * minor doc fixes\n * temporarily depend on forked freezegun to avoid suprious test failures","distinct":false,"url":"https://api.github.com/repos/TomBaxter/waterbutler/commits/8553accb65b494231ae351c4aaccf3efa96d9dd1"},{"sha":"72544c0c652d50d139a3cc6e1d81a4d16cb97c6f","author":{"email":"3ca23a7ddfc3de21c7d8437663fcac27d7618d41@cos.io","name":"Fitz Elliott"},"message":"update changelog & bump version","distinct":false,"url":"https://api.github.com/repos/TomBaxter/waterbutler/commits/72544c0c652d50d139a3cc6e1d81a4d16cb97c6f"},{"sha":"f1788a5a4a7cffe90c87fb02a13551db71b2c2cd","author":{"email":"3ca23a7ddfc3de21c7d8437663fcac27d7618d41@cos.io","name":"Fitz Elliott"},"message":"Merge branch 'release/0.15.0'\n\nYeah, so 0.14.4 hotfix was a lot more ambitious than I realized.  So\nlet's pretend like I actually meant to drop a release.","distinct":false,"url":"https://api.github.com/repos/TomBaxter/waterbutler/commits/f1788a5a4a7cffe90c87fb02a13551db71b2c2cd"},{"sha":"7a31ab6eaede0739e1afc81611734a513bfeb2fb","author":{"email":"3ca23a7ddfc3de21c7d8437663fcac27d7618d41@cos.io","name":"Fitz Elliott"},"message":"Merge remote-tracking branch 'cos/master' into develop","distinct":false,"url":"https://api.github.com/repos/TomBaxter/waterbutler/commits/7a31ab6eaede0739e1afc81611734a513bfeb2fb"},{"sha":"d1c8d57decafe3c38b171c11723d7c70bd515fbf","author":{"email":"3ca23a7ddfc3de21c7d8437663fcac27d7618d41@cos.io","name":"Fitz Elliott"},"message":"fix 'path' attr in v0 move/copy logs\n\nv0 and the move/copy tasks were sending back incorrectly-formatted logs\nto the OSF logging callback.  The 'path' attribute of the source was\nset to the file name of the source file, rather than an actual valid\nWaterButler path.  ID-using providers like Box and osfstorage should be\nsending back '/92b3e4ef912'-style paths, while others should be\nprefixing their paths with a slash.","distinct":true,"url":"https://api.github.com/repos/TomBaxter/waterbutler/commits/d1c8d57decafe3c38b171c11723d7c70bd515fbf"},{"sha":"906e8f3eea2a9212ebdd0393bc43f0b15c3b04a2","author":{"email":"3ca23a7ddfc3de21c7d8437663fcac27d7618d41@cos.io","name":"Fitz Elliott"},"message":"fix v0 delete to log correct path\n\nthe v0 delete action was also not setting the correct path in the logging\npayload","distinct":true,"url":"https://api.github.com/repos/TomBaxter/waterbutler/commits/906e8f3eea2a9212ebdd0393bc43f0b15c3b04a2"},{"sha":"33fd88bacc890cf04af0065d5df4eecd9e435005","author":{"email":"1e5b0fd79cf0fdc019b55266ce63f6fec5494fdf@fiskur.org","name":"Fitz Elliott"},"message":"Merge pull request #112 from felliott/feature/fix-v0-log-paths\n\n[CR] fix v0 log paths","distinct":true,"url":"https://api.github.com/repos/TomBaxter/waterbutler/commits/33fd88bacc890cf04af0065d5df4eecd9e435005"},{"sha":"64fbb63bb44e2b7a4ead208e274bf95b77f9327b","author":{"email":"3ca23a7ddfc3de21c7d8437663fcac27d7618d41@cos.io","name":"Fitz Elliott"},"message":"fix cross-resource dropbox move metadata error\n\n * For intra_move and intra_copy, dropbox metadata figures out the relative path\n   of the file by stripping the parent folder from the full path.  When\n   moving a file from one node's dropbox to another's, we were\n   inadvertantly passing the source's parent folder to the destination's\n   meta object, causing nothing to be stripped and the full path to be\n   returned.  Now we pass the destination's parent folder to the meta,\n   and the file is properly made relative.","distinct":true,"url":"https://api.github.com/repos/TomBaxter/waterbutler/commits/64fbb63bb44e2b7a4ead208e274bf95b77f9327b"},{"sha":"d11c7c8ba32fc51aff87c7af66a5114379e2652d","author":{"email":"3ca23a7ddfc3de21c7d8437663fcac27d7618d41@cos.io","name":"Fitz Elliott"},"message":"don't overwrite destination path in task.move\n\n * The grandparent commit had an uncaught bug in it.","distinct":true,"url":"https://api.github.com/repos/TomBaxter/waterbutler/commits/d11c7c8ba32fc51aff87c7af66a5114379e2652d"},{"sha":"d5fc53b4489357fc8d1931f20b2359465498422b","author":{"email":"3ca23a7ddfc3de21c7d8437663fcac27d7618d41@cos.io","name":"Fitz Elliott"},"message":"encode gdrive path in log payloads\n\ngdrive paths are supposed to be percent-encoded e.g. \"/a file\" becomes\n\"/a%20file\".  The logging code was providing source path by calling .path() on\nWaterButlerPath objects.  .path() returns the unencoded (human-readable)\npath.  Update this code to call .raw_path(), which passes the path\nthrough an encoding function.","distinct":true,"url":"https://api.github.com/repos/TomBaxter/waterbutler/commits/d5fc53b4489357fc8d1931f20b2359465498422b"},{"sha":"c1ba582f2ab2e091f250406586ddeef6eca2c4ef","author":{"email":"07bf5272b7ebc53d6ba4131d9444e517116e597b@gmail.com","name":"TomBaxter"},"message":"Merge remote-tracking branch 'upstream/develop' into feature/python35\nand update for python 3.5 tornado 4.3 async\n\nConflicts:\n\ttests/providers/s3/test_provider.py\n\twaterbutler/providers/dropbox/provider.py\n\twaterbutler/providers/s3/provider.py\n\twaterbutler/server/api/v0/core.py","distinct":true,"url":"https://api.github.com/repos/TomBaxter/waterbutler/commits/c1ba582f2ab2e091f250406586ddeef6eca2c4ef"}]}