Sorry for the times in the log, my computer is set to UTC+11.
02:44 +proppy hey there
02:48 sec_ good holiday proppy :)
02:48 +proppy I'm visiting london :)
02:48 +proppy not really in holiday
02:49 * sec_ have read all GAE thing related (but slow)
02:54 +proppy how many people are there for
The datastore admin job does not use cron.
Have you checked the cron tab in the admin-console to see if there are any
cron tasks enabled in your app?
Have you recently performed a migration from Master/Slave to High
Replication and had cron enabled on the application? If so, you will need
to
Can you please add the full stack trace?
And if it is repeatable either a code snippet or an explanation of
what your program was doing when the exception occured.
On 14 November 2011 18:29, someone1 someo...@gmail.com wrote:
I am continunously getting the following error for a segment of code
Have you specified 'runtime: python' or 'runtime: python27'?
If you are using 'runtime: python', then setting 'threadsafe: true' is
not supported.
On 14 October 2011 00:59, Emlyn emlynore...@gmail.com wrote:
I am using the builtin handler in app.yaml
On Oct 14, 2011 12:25 AM, Greg Darke
with the same datastore.
Regards,
Hans Then
On Sep 27, 5:53 am, Greg Darke (Google) darke+goo...@google.com
wrote:
Yes it is quite easy to do. The easiest way is to create a separate
directory containing the code for the backend, then just upload the
backend (be sure to not accidentally
This should never occur.
A cron task should only run on one instance. If you have specified the
'target' parameter then it should execute on that version/backend otherwise
it will execute on the default version of your application.
What is your app id so I can look into this?
On 25 September
Yes it is quite easy to do. The easiest way is to create a separate
directory containing the code for the backend, then just upload the
backend (be sure to not accidentally upload the code over your default
version).
Though be careful with configuration that is not scoped to a specific
version:
If you would like this feature, please file feature request on the
issue tracker: http://code.google.com/p/googleappengine/issues/list.
You can currently get the same details by looking at the admin
console: https://appengine.google.com/
On 22 September 2011 05:26, Jason Collins
What happens when you start an RPC, but not wait for it to finish is
not really defined. As you have may have noticed, it also works
differently in production and in the dev appserver.
Also note that since it is not defined, the behaviour may change at anytime.
I would suggest that you should
It is undefined, and thus you should not do it.
On 23 September 2011 14:35, Albert albertpa...@gmail.com wrote:
Thanks!
How about in the Production environment? What's the behavior there?
On Sep 22, 10:52 pm, keakon lolicon kea...@gmail.com wrote:
The SDK will automatically create a RPC
Rishi: This sounds like an excellent idea. Even with concurrent
requests in python 2.7, using the asynchronous apis like this will
make you application perform much better.
On 9 September 2011 06:18, Rishi Arora rishi.ar...@ship-rack.com wrote:
Actually I thought using RPCs is a good way to
Do you have the full useragent?
App engine applications state that they are running on google app
engine in their user agent. They also state the application id that is
making the request. If the user agent does not contain google app
engine, then it is not an app engine application making the
On 5 August 2011 10:13, johnP j...@thinkwave.com wrote:
can you clarify: You need to persist re-read the Entities and persist
them as keys.
If your entities are stored as a String, or a list of strings, you
will need to read the entities, and change their type to be either a
Key (or reference
Chat log from today's App Engine office hours. All times are in AEST (UTC+10).
12:01 -!- Irssi: #appengine: Total of 115 nicks [0 ops, 0 halfops, 2
voices, 113 normal]
12:01 jwbnyc Thanks for joining, us Wesley!
12:01 Wesley_Google who? where?
12:01 robertk Wesley_Google: there -
12:01
If you are interested in this feature (blocking for new pull queue
tasks), please file an feature request in the issue tracker (or if one
already exists, star it).
We use the issue tracker to see what features user's are asking for
and also to gauge how popular a specific request is.
Hi Gerad,
The following code will work (at least in the current version of the
dev_appserver). I would like to point out that this is accessing a
private variable and may break in the future without any notice.
from google.appengine.tools import dev_appserver
RealFileClass =
Are you using the taskqueue labs api?
The taskqueue labs api (google.appengine.api.labs.taskqueue) was
deprecated in 1.4.0, and thus new features will no longer be added to
the old api.
To use new features such as pull queues and the target parameter you
will need to change your import statement
Check the value of Task Queue API Calls on the Task Queues page in
admin console.
Are you exceeding this limit?
If not, what is the app id so that I can check why you are getting this error.
On 1 June 2011 11:29, working coro...@gmail.com wrote:
Dear All,
I started getting this error today.
On 1 June 2011 14:54, Bart Thate bth...@gmail.com wrote:
snip
Once memory is billable, you gonna be sure that people actually try to make
good use of it. If you do instance price only who cares ?
As for debugging you might have point maybe google could provide the an app
stats API where the
:-(
Please, tell me what i'm doing wrong here (if you can figure it out,
of course)
On 13 mayo, 14:16, Greg Darke (Google) darke+goo...@google.com
wrote:
This sounds like a excellent use of backends.
I believe that there is currently a limitation that a channel created
in a frontend (ie, your
\remote_api\remote_api_stub.py, line 197, in _MakeRealSyncCall
raise pickle.loads(response_pb.exception())
CallNotFoundError
On May 17, 12:44 am, Greg Darke (Google) darke+goo...@google.com
wrote:
In the dev-appserver you need to pass the '--backends' parameter.
On 15 May 2011 11:07, uri twig
In the dev-appserver you need to pass the '--backends' parameter.
On 15 May 2011 11:07, uri twig uri.t...@gmail.com wrote:
Hi I'm tring to work with the new backends api, I downloaded the
sample code form http://backends-io.appspot.com/
and I run it on a few machines with the new appengine
To upload this backend to App Engine, you need to perform a backends up:
appcfg.py backends update path/to/application/
On 12 May 2011 10:04, Sergey tvoys...@gmail.com wrote:
I want to test new feature - backends.
As I understand it's enough to create backends.yaml and describe there
.
Thanks!
Aaron
On May 14, 7:19 pm, Greg Darke (Google) darke+goo...@google.com
wrote:
Since backends and frontends are updated separately, the code in each
may be different. Updating a frontend does not change the code that is
running in a backend/vice versa.
As for the syntax, I believe
to
and I could not get it to work on the dev server at all.
-Richard
On May 16, 2:46 pm, Greg Darke (Google) darke+goo...@google.com
wrote:
To upload this backend to App Engine, you need to perform a backends up:
appcfg.py backends update path/to/application/
On 12 May 2011 10:04, Sergey
You should be able to send a deferred task to a backend.
Some points to remember though:
* You should ensure that any classes/etc you reference from the
frontend must exist in the backend.
* The deferred function should pass the 'target' parameter on to taskqueue
* You must enable the deferred
That is correct, all tasks get the same host header as the request
that created them. This means that if you access the url
http://0.backend-name.app-id.appspot.com/ and it inserts a task, the
task will execute against instance 0 of 'backend-name'.
If you access the url
should be sure that the backend has the
same classes and configurations as the frontend? As far as I have
read, the frontend and backend are using the same code base, so is
this implied already, or is there something extra I am missing?
Best,
Aaron
On May 14, 5:56 pm, Greg Darke (Google
Please see the Backends talk from Google IO
(http://www.youtube.com/watch?v=-kepYfCBg6w).
It is mentioned in this talk that a single thread is only able to use
2.4Ghz of cpu. This is why a B4 and B8 appear the to have the same
amount of cpu time in your example. To take full advantage of the cpu
This sounds like a excellent use of backends.
I believe that there is currently a limitation that a channel created
in a frontend (ie, your default version) is not able to be used to
send messages from a backend.
As noted in the Google IO talk, we are currently working on removing
this
The currently recommended way of deleting all entities of a particular
kind is to use datastore admin
(http://code.google.com/appengine/docs/adminconsole/datastoreadmin.html#Deleting_Entities_in_Bulk).
If the primary version of your code is not in python, you can upload a
simple application to an
I would suggest having a look at the example code in
http://backends-io.appspot.com/static/counter_demo.zip.
The code gives examples of how to use urlfetch to communicate between
a fronend and a backend. The backend (counter.py) also keeps the value
in memory, and writes out changes either within
This does indeed sound like a bug.
Can you please file a bug about this on the bug tracker?
http://code.google.com/p/googleappengine/issues/entry?template=Other%20defect
If you include the issue number in this thread I can ensure it get
triaged correctly.
On 12 May 2011 13:32, Loren
Yes.
The taskqueue.add function may only add 100 tasks at a time.
On 12 May 2011 15:35, Jeff Schnitzer j...@infohazard.org wrote:
With appengine frontends, each request is limited to 100 inserts into
the task queue.
Do long-running backend requests have the same limitation?
Jeff
--
You
of tasks to be created in the context
of that long-running request.
Is this just not an option?
Thanks,
Jeff
On Thu, May 12, 2011 at 5:01 PM, Greg Darke (Google)
darke+goo...@google.com wrote:
Yes.
The taskqueue.add function may only add 100 tasks at a time.
On 12 May 2011 15:35, Jeff
per notification to send to a user, but when
you are sending them (in your 'reduce' phase) you could lease multiple
tasks at once and send them all at the same time.
On 12 May 2011 20:20, Greg Darke (Google) darke+goo...@google.com wrote:
By 'at a time' I mean per call to taskqueue.Queue.add
We are looking into this issue.
On 4 May 2011 10:01, Anders anders.ny...@gmail.com wrote:
Same problem here, also getting:
DeadlineExceededError: The API call taskqueue.BulkAdd() took too long
to respond and was cancelled.
Have been going on all day with about the same frequency (mostly
On 31 March 2011 09:21, Robert Kluin robert.kl...@gmail.com wrote:
Cool; quite a few bug fixes.
To specify a version for a task queue, do you use set a 'target' in
queue.yaml?
Yes, that is correct.
You also use the same parameter for cron tasks.
--
You received this message because you
Hi Nathanael,
You should also put the following in your appengine_config.py file:
webapp_django_version = '1.2'
This will make webapp.template use the specified version of django.
This is needed since the dev admin-console, appstats and the
map-reduce framework all use webapp.template to render
Hi Daniel,
This will work, though you will need to put a '/' character at the
start of the url.
On 13 March 2011 07:30, Daniel danielkra...@gmail.com wrote:
I want to do something like this.. will it work?
cron:
- description: Resign Games
url: rgame?daysOld=5
schedule: every 2 hours
Hi Justin,
I checked the code to confirm this issue.
If you would like this functionality in the development appserver,
please create a bug on the issue tracker.
On 17 February 2011 00:44, Justin justin.worr...@gmail.com wrote:
Ok thanks - does it say this in the docs somewhere ? or are you
41 matches
Mail list logo
