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

bug fix: cleanup logs in case of noop updates. #71

Merged
merged 1 commit into from Nov 21, 2013

Conversation

Projects
None yet
2 participants
@tmorgan
Contributor

tmorgan commented Nov 20, 2013

Ensure that we don't try and perform no-op updates, these can occur when at minimum provisioned reads and writes. These are harmless but clutter up the logs and make analysing them harder, as the information (that an update isn't happening) is split across multiple lines.

Ensure that we don't try and perform no-op updates, these can occur w…
…hen at minimum provisioned reads and writes. These are harmless but clutter up the logs and make analysing them harder, as the information (that an update isn't happening) is split across multiple lines.
@sebdah

This comment has been minimized.

Owner

sebdah commented Nov 20, 2013

Thanks for the PR @tmorgan. I'll review it tomorrow!

@ghost ghost assigned sebdah Nov 20, 2013

@sebdah sebdah merged commit b21b4aa into sebdah:master Nov 21, 2013

@sebdah

This comment has been minimized.

Owner

sebdah commented Nov 21, 2013

Thanks @tmorgan. This fix is included in the 1.6.0 release, which I just pushed to PyPI!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment