html_url,issue_url,id,node_id,user,created_at,updated_at,author_association,body,reactions,performed_via_github_app,issue
https://github.com/pydata/xarray/issues/2927#issuecomment-506486503,https://api.github.com/repos/pydata/xarray/issues/2927,506486503,MDEyOklzc3VlQ29tbWVudDUwNjQ4NjUwMw==,1312546,2019-06-27T19:51:58Z,2019-06-27T19:51:58Z,MEMBER,Spoke with @martindurant about this today. The mapping should probably strip the protocol from the `root` provided by the user. Tracking in https://github.com/intake/filesystem_spec/issues/56 (this issue can probably be closed).,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,438166604
https://github.com/pydata/xarray/issues/2927#issuecomment-489659358,https://api.github.com/repos/pydata/xarray/issues/2927,489659358,MDEyOklzc3VlQ29tbWVudDQ4OTY1OTM1OA==,1217238,2019-05-06T15:17:55Z,2019-05-06T15:17:55Z,MEMBER,All xarray does is directly pass the `store` object on to `zarr.open_group()` or `zarr.open_consolidated()`. So this must be an issue with s3fs or zarr -- we have literally no logic related to parsing s3 filenames in xarray.,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,438166604
https://github.com/pydata/xarray/issues/2927#issuecomment-489142071,https://api.github.com/repos/pydata/xarray/issues/2927,489142071,MDEyOklzc3VlQ29tbWVudDQ4OTE0MjA3MQ==,9658781,2019-05-03T15:46:41Z,2019-05-03T15:46:41Z,CONTRIBUTOR,"I am seeing the same behaviour. 
For me, writing with a prepended s3:// is no issue though (even appending to zarr works when using the related PR). 
Only opening cannot cope with the prepended s3://.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,438166604