Hi, team.
My application was running fine for years.
But from 2013/3/30, I got a Internal error, "the id allocated for a new
entity was already in use, please try again".
Initially this error did't always happen, but now all put()s to one kind
return this error.
The details are as follow:
1. Th
I'm using cloud endpoints with authentication on python environment.
And I have two registered apps, one is native, other is web, on Cloud
Console.
In native app, I can use my apis after authentication. But in web app,
below error is happened.
> Oauth framework user didn't match oauth token use
Thank you for your comment.
On Wednesday, November 27, 2013 4:24:51 PM UTC+9, Vinny P wrote:
>
> On Tue, Nov 26, 2013 at 10:35 AM, Koji Matsui
> > wrote:
>
>> I don't have any idea how to investigate about this error with this short
>> log message.
>>
info from get_current_user().
In the document, Cloud Endpoints project is created through Cloud Console,
but my application is created through AppEngine Console before.
thanks,
On Wednesday, November 27, 2013 6:00:40 PM UTC+9, Koji Matsui wrote:
>
> Thank you for your comment.
>
> On Wednesday, Nov
> ==
>
> You forget the "comparison operator" in your filter statements.
>
>
> 2008/12/13 paptimus :
>
>> query = models.Ownership.all().filter('user', user),filter('deleted',
>> False).order('-created_on').fetch(offset, a
er quota warning and vacuumed
>> these indeces.
>> Vacuume_index was completed and there is no index of that model.
>>
>> But the warging of over quota ramains over 24 hours and the status of
>> a new index remains "building".
>>
>> I hope you ch