{"action":"created","issue":{"url":"https://api.github.com/repos/ex-aws/ex_aws/issues/572","repository_url":"https://api.github.com/repos/ex-aws/ex_aws","labels_url":"https://api.github.com/repos/ex-aws/ex_aws/issues/572/labels{/name}","comments_url":"https://api.github.com/repos/ex-aws/ex_aws/issues/572/comments","events_url":"https://api.github.com/repos/ex-aws/ex_aws/issues/572/events","html_url":"https://github.com/ex-aws/ex_aws/issues/572","id":337245115,"node_id":"MDU6SXNzdWUzMzcyNDUxMTU=","number":572,"title":"ExAws.Error message returns a string of the hackney error, add function to access actual error tuple.","user":{"login":"GrandathePanda","id":6426407,"node_id":"MDQ6VXNlcjY0MjY0MDc=","avatar_url":"https://avatars0.githubusercontent.com/u/6426407?v=4","gravatar_id":"","url":"https://api.github.com/users/GrandathePanda","html_url":"https://github.com/GrandathePanda","followers_url":"https://api.github.com/users/GrandathePanda/followers","following_url":"https://api.github.com/users/GrandathePanda/following{/other_user}","gists_url":"https://api.github.com/users/GrandathePanda/gists{/gist_id}","starred_url":"https://api.github.com/users/GrandathePanda/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/GrandathePanda/subscriptions","organizations_url":"https://api.github.com/users/GrandathePanda/orgs","repos_url":"https://api.github.com/users/GrandathePanda/repos","events_url":"https://api.github.com/users/GrandathePanda/events{/privacy}","received_events_url":"https://api.github.com/users/GrandathePanda/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2018-06-30T21:47:36Z","updated_at":"2018-06-30T22:54:29Z","closed_at":null,"author_association":"NONE","body":"### Current behavior\r\n\r\nNot a bug really but, I question the usefulness of the current error implementation. Right now when ExAws.Error is raised the message is the string,\r\n\r\n`ExAws Request Error!\\n\\n{:error, {:http_error, 404, %{body: \\\"<?xml version=\\\\\\\"1.0\\\\\\\" encoding=\\\\\\\"UTF-8\\\\\\\"?>\\\\n<Error><Code>NoSuchBucket</Code><Message>The specified bucket does not exist</Message><BucketName>***********</BucketName><RequestId>48E92B0AA558EB3C</RequestId><HostId>**********</HostId></Error>\\\", headers: [{*************************}]\\\"}, {\\\"Content-Type\\\", \\\"application/xml\\\"}, {\\\"Transfer-Encoding\\\", \\\"chunked\\\"}, {\\\"Date\\\", \\\"Sat, 30 Jun 2018 21:35:54 GMT\\\"}, {\\\"Connection\\\", \\\"close\\\"}, {\\\"Server\\\", \\\"AmazonS3\\\"}], status_code: 404}}}\\n\"`\r\n\r\nThis is super not useful for me personally, I'd really rather have access to what looks like the Hackney error tuple that is interpolated in there for things like its status code and response body. I checked the docs for the error module and there doesn't seem to be something like that already.\r\n\r\n### Feature Request\r\n\r\nAdd a function to ExAws.Error to return the underlying Hackney error tuple\r\n\r\nI'd be happy to take a crack at implementing this and submitting a PR."},"comment":{"url":"https://api.github.com/repos/ex-aws/ex_aws/issues/comments/401571278","html_url":"https://github.com/ex-aws/ex_aws/issues/572#issuecomment-401571278","issue_url":"https://api.github.com/repos/ex-aws/ex_aws/issues/572","id":401571278,"node_id":"MDEyOklzc3VlQ29tbWVudDQwMTU3MTI3OA==","user":{"login":"benwilson512","id":247817,"node_id":"MDQ6VXNlcjI0NzgxNw==","avatar_url":"https://avatars1.githubusercontent.com/u/247817?v=4","gravatar_id":"","url":"https://api.github.com/users/benwilson512","html_url":"https://github.com/benwilson512","followers_url":"https://api.github.com/users/benwilson512/followers","following_url":"https://api.github.com/users/benwilson512/following{/other_user}","gists_url":"https://api.github.com/users/benwilson512/gists{/gist_id}","starred_url":"https://api.github.com/users/benwilson512/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/benwilson512/subscriptions","organizations_url":"https://api.github.com/users/benwilson512/orgs","repos_url":"https://api.github.com/users/benwilson512/repos","events_url":"https://api.github.com/users/benwilson512/events{/privacy}","received_events_url":"https://api.github.com/users/benwilson512/received_events","type":"User","site_admin":false},"created_at":"2018-06-30T22:54:29Z","updated_at":"2018-06-30T22:54:29Z","author_association":"CONTRIBUTOR","body":"Well that package is also me. Regardless though, neither `put_object` nor any of the other S3 functions actually call `ExAws.request`, they all just build operation structs which you pass to one of the request functions. Can you show the exact code you're running to produce the error?"}}
{"actor":{"display_login":"benwilson512"}}