On Fri, Oct 25, 2013 at 9:04 PM, Kaan Soral <[email protected]> wrote:
> 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? > > I'm not sure to be honest. I know I've had a similar error when doing Python tasklets, but I don't know if it's the same for handlers linked to ndb. As for the error not reoccurring, this issue usually only pops under heavy load or when App Engine is slow. If you don't expect heavy load, it might be more time-efficient to simply ignore the problem and deal with it manually if it ever pops again. ----------------- -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.
