-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
get_metric_statistics returns error in library but not on cli #18
Comments
I will say that
works everytime |
I'd like to see the raw response back from aws. Is this accessible via ExAws? Any thoughts @benwilson512 Appreciated |
@brpandey sorry for the late reply, I am currently on holiday :). I can take a look at this in a couple of days, and let you know! Thanks for reporting the issue. |
@cammellos Enjoy your vacation! In the meantime, I will see if I can figure this out |
Update -- Looking at the ExAws docs you can easily override the default http client behaviour with your own. So I've added these entries
and (basically wrapping the default hackney call with an IO.inspect)
Which when triggered and for my specific usecase produces:
Now to see what SweetXml is trying to do... |
The error happens in this block of code where xml is the body string value from above
|
Xpath values in the x_sigill which are floats (f) that are not found in the xml body will error, thus instead of putting f an optional f should be used and it will parse correctly, e.g. of https://hexdocs.pm/sweet_xml/SweetXml.html#sigil_x/2 like such:
|
I ran into the same issue and it looks like the PR #19 still works. |
I ran into the same issue getting this error
I added some logging to sweet_xml and found that it was expecting all statistics in opts. I was only passing through Maximum. I updated my code to the below and the error went away.
This seems like the same bug that should have been fixed in the previous PRs. I'm using what seems to be the latest version, 2.0.4. Is this fix going to be updated or is there a newer version? |
Not sure where this goes - ex_aws or ex_aws_cloudwatch
The aws CLI tools works fine when I run get-metric_statistics -- I always get data
However when I run using ExAws/ExAws.Cloudwatch, I get the SweetXML(v0.6.6) error below
Its not clear what is actually happening and what the aws response was?
The text was updated successfully, but these errors were encountered: