Skip to content
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

Don't create transactions that have no operations. #27

Merged
merged 1 commit into from
Apr 11, 2017

Conversation

jameinel
Copy link
Member

@jameinel jameinel commented Apr 9, 2017

This may fix: https://bugs.launchpad.net/juju/+bug/1680786
It doesn't let us know who is creating no-op transactions,
but it does feel like it isn't worth committing them to
the database.

We did already have ErrNoOperations to signal something similar, but it seems to me that we should either treat no-operations as either the same thing, or we should actually treat it as an error. If you'd prefer an error, I can do that, but we then need to track down the places that are creating these, so we don't have production failures.

(Review request: http://reviews.vapour.ws/r/6508/)

this may fix: https://bugs.launchpad.net/juju/+bug/1680786
It doesn't let us know who is creating no-op transactions,
but it does feel like it isn't worth committing them to
the database.
Copy link

@mjs mjs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm happy with this approach as is. It seems risky to start generating errors and then not being able to find the source.

@jameinel
Copy link
Member Author

$$merge$$
(not sure if curtis got the bot set up, if not, I'll merge directly)

@jameinel jameinel merged commit 88827c2 into juju:master Apr 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants