updates to disqus_export to make it more robust and informative #14
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
add -j options to skip past the first comment stored (to get around broken data) add -c option to continue on errors rename a variable to avoid conflict with model name give more informative output including progress report give more informative error reproting give more informative output on http errors
add option to specify a log file to which all errors will be output --dry-run now will do full data processing but stop short of uploading data
Author
|
hey - have you any interest in this change? If so I can test it against HEAD. |
|
@tomscytale ok! |
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.
I had to upload an crufty dataset to disqus with many comment records that had become corrupt. I made several changes to enable disqus_export deal more gracefully with bad data and output useful information.
details:
add option to specify a log file to which all errors will be output
--dry-run now will do full data processing but stop short of uploading data
add -j options to skip past the first comment stored (to get around broken data)
add -c option to continue on errors
rename a variable to avoid conflict with model name
give more informative output including progress report
give more informative error reporting including details of models which are corrupt
give more informative output on http errors