stable_karma and unstable_karma values in API data should not be allowed to be 'None' #274
Labels
API
Issues related to Bodhi's REST API
Discussion
Issues that may be controversial and warrant a discussion
Migration
Issues or pull requests that involve a database migration
At the time I'm writing this, there are updates whose API data includes 'None' for the
stable_karma
andunstable_karma
values. The example I hit is bash-4.3.42-1.fc21 but at least the updates for bash in other releases show the same issue in api data.The updates submitted after the bodhi2 upgrade seem to have
stable_karma
(the updates for the latest gnome megaupdate and python-django amongst others do) where the updates that were submitted before the upgrade and migrated over to the new bodhi2 instance don't.stable_karma
is an important piece of data which should always be an integer. If the old updates are left as is (assuming I'm right about old updates not havestable_karma
) they should at least return 0, a sane default (assuming thatNone
means that nothing was changed from the default of 3) or some obvious filler data (-9999999).The text was updated successfully, but these errors were encountered: