Hi,
I've got it in my logs:
File /base/data/home/apps/contact-birthdays/1.336002949603692439/
birthdaysapp/views.py, line 123, in index_view
read_only = not(capabilities.CapabilitySet('datastore_v3',
['write']).is_enabled())
File
This quota bug was fixed yesterday, before the rollover. My apologies for
not reporting it fixed sooner (it was outside my work hours in Dublin).
-Nick
On Tue, Sep 1, 2009 at 9:49 PM, GregF g.fawc...@gmail.com wrote:
On Sep 1, 6:50 am, tijer troels...@gmail.com wrote:
HOWEVER, there is a
Hi tijer,
What is your App ID, and what is the exact quota error you were seeing?
-Nick
On Mon, Aug 31, 2009 at 7:50 PM, tijer troels...@gmail.com wrote:
12 hours from now everything will revert to read-only and memcache
will fail. So, what to do? Well, x from Google provided a very useful
On Sep 1, 6:50 am, tijer troels...@gmail.com wrote:
HOWEVER, there is a huge problem. I just did something similar for my
app, with the result that it immediately gave me massive quota-fails.
As soon as 100 of the capabilities.CapabilitySet('datastore_v3',
['write']).is_enabled() had been
On Sep 2, 8:49 am, GregF g.fawc...@gmail.com wrote:
I am using CapabilitySet and am not seeing the same problem -
currently it has been called 250 times. But thanks for your warning -
I'll be watching it like a hawk.
It's now well over a thousand calls with quota warnings, so it seems I
don't
A correction to the above, it should have been == True (or the loop
switched around).
On Aug 31, 8:50 pm, tijer troels...@gmail.com wrote:
12 hours from now everything will revert to read-only and memcache
will fail. So, what to do? Well, x from Google provided a very useful
option on how to
