Updating the xml parsing error reporting and adding additional logging statements #34
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…riables not being set.
…utput to help with troubleshooting.
…or message with the new ds3_log utility instead of logging to stderr.
robertgrimm
added a commit
that referenced
this pull request
Feb 19, 2015
Updating the xml parsing error reporting and adding additional logging statements
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request updates all the xml parsing code to report unrecognized xml elements to our new internal logging utility instead of logging to stderr. Additionally we are also logging the string to sign for the signature calculation to help with troubleshooting on the client side when there are signature mismatches.