Wow, that is really interesting and extremely insightful Indeed I am mixing sync with async as usual, however, I'm not using tasklet's
Basically I have a handler decorated with @ndb.toplevel I'm firing several ndb.transaction_async's - there might be ndb.transaction's in between, it's generally mixed, in the end I'm waiting for all the async's I've re-tested the same scenario once more, it didn't produce the same error this time, didn't try once more yet Does your answer apply to this scenario? Thanks in Advance On Saturday, October 26, 2013 4:54:54 AM UTC+3, Vinny P wrote: > > On Fri, Oct 25, 2013 at 2:15 PM, Kaan Soral <[email protected]<javascript:> > > wrote: > >> However, are the following logs caused by the sdk, or is there an >> infinite recursion bug in my code that I'm now aware of? >> >> WARNING 2013-10-25 18:58:28,660 tasklets.py:409] suspended generator >> _get_tasklet(context.py:266) raised RuntimeError(maximum recursion depth >> exceeded while calling a Python object) >> > > > Are you mixing async calls with synchronous calls in your tasklet? You > need to change all the calls into async (or use *yield [async call here]*). > Otherwise, the sync call goes too deep in recursion and gets shut down. > > > ----------------- > -Vinny P > Technology & Media Advisor > Chicago, IL > > App Engine Code Samples: http://www.learntogoogleit.com > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
