@ndb.toplevel solves ndb related async issues I've recently started using Task().add_async() and immediately discovered that async calls are disregarded if you don't manually wait for the response - on SDK *WARNING 2013-09-11 16:17:18,006 recording.py:653] Found 1 RPC request(s) without matching response (presumably due to timeouts or other errors)* You see the above message - and no results
I've tested the same call on production, it works, the task executes I've modified recording.py to manually wait for those RPC's - it works great - it forces the async calls to execute on SDK, if anyone wants I can share the modification However the question is, are those calls 100% safe of production, can you just add a Task with add_async and not worry about the task not executing? For example if you add 500 tasks with Task add_async, and just complete the request without waiting or anything, is the execution rate 500/500 - assuming no task exceptions? -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
