of the connection who assures me
they are seeing no problems on their end.
Thanks,
Nikolaj
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine/-/YTlYBIVuXnwJ.
To post
folks if this is even remotely
possible or if None would definitely be returned instead?
Thanks,
Nikolaj
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google
Steve, I thought I had gotten everything out of that talk but clearly
I was sleeping in class!
The memcache fork join queue looks very interesting - I'm definitely
giving that a try.
Nikolaj
On Sep 23, 1:00 am, Steve Sherrie st...@wasteofpaper.com wrote:
Definitely checkout Brett Slatkin's
that exist?
Any suggestions or experiences on how I can work around this would be
appreciated.
Many thanks,
Nikolaj
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to google-appengine@googlegroups.com
Hi there,
I was wondering if it is possible to configure or modify the NoseGAE
plugin to automatically update the index.yaml file when queries are
run in tests. I have 100% test coverage so this would be quite useful.
Has anybody had any luck with such a testing suite setup?
Nikolaj
--
You
It seems the web app at google sometimes gets confused, when you are logged
in to more than one (google) account at a time.
You log in OK (authentication), but when you are trying to access the GAE
page (authorization) I think the webapp somehow does that with the wrong
cookie.
For me it
