> Do you think these tests are enough? I deployment similar code yesterday and
> it seemed to me reserve() wasn't respecting the settings.PRIVATE_ONLY
> variable, and I couldn't find any logs (gunicorn issue, I think). Is there
> anything else I need to do besides setting that on unit_config? Tests are
> passing now but maybe I'm not testing this as I should.
is it possible you failed to restart django after changing your unit-config and/or settings.py?
> Do you think these tests are enough? I deployment similar code yesterday and PRIVATE_ ONLY
> it seemed to me reserve() wasn't respecting the settings.
> variable, and I couldn't find any logs (gunicorn issue, I think). Is there
> anything else I need to do besides setting that on unit_config? Tests are
> passing now but maybe I'm not testing this as I should.
is it possible you failed to restart django after changing your unit-config and/or settings.py?
139 - qs = PPA.objects. select_ for_update( ).filter( state=PPA. AVAILABLE) select_ for_update( ).filter( AVAILABLE, private= settings. PRIVATE_ ONLY)
140 + qs = PPA.objects.
141 + state=PPA.
That looks pretty cut-and-dry to me. I don't think that could do the wrong thing, and:
190 + def testReservePriv ateOnly( self):
seems to verify that block