we did the upgrade and are running latest web2py release + GAE latest
SDK. we pulled forward 2 patches - one for using custom tables with
auth (so if you use standard auth tables you don't need that patch), and
one for handling JSON lists as post data for restful requests.
we also had to update our cache.ram.flush_all() to just
catch.ram.flush() (i think that was the change....the details are foggy
right now).
everything else just worked for us.
cfh
On 7/5/13 23:54 , Aravindan Rs wrote:
hi cfh,
did you complete the move to the recent web2py version? does it solve the
issue and work well with GAE version 1.8.1? i want to move now and any
notes from you would be helpful.
thanks,
aravind.
On Saturday, 15 June 2013 06:18:06 UTC+5:30, Christian Foster Howes wrote:
Yup, that change is why i'm upgrading web2py now. Other GAE users have
reported issues with the recent web2py versions, and i think i found an
issue in the auth module when using custom table names. I'll let you
know my results as i do my testing....
cfh
On 6/14/13 17:33 , Aravindan Rs wrote:
Thanks - I assume you are talking about the change from "class
Reference(int)" to "class Reference(long)". Should work I think.
Btw: This fix was done quite some time ago (on Jan 1st 2013 -
https://github.com/web2py/web2py/commit/dd3055836a3f8fbc5b06763710c369cab3f3fc40)
- so patch might not be necessary. I'll move to latest web2py and check.
Thanks again,
Aravind.
On Friday, 14 June 2013 20:16:41 UTC+5:30, Christian Foster Howes wrote:
Aravind,
I see that in trunk (and perhaps the latest web2py release) i think
that
this has been fixed. Please make sure you are using the latest web2py
version. I'm working on upgrading to the latest web2py version and
then
the latest GAE SDK to get things working for me. There may be some
patches
coming, hopefully later today....
cfh
On Thursday, June 13, 2013 2:15:46 AM UTC-7, Aravindan Rs wrote:
Hi,
I get the following error stack on login / logout when session object
is
attempted to be written to the database:
Traceback (most recent call last):
File
"/base/data/home/apps/s~nittio-live/24.368055561930403768/gluon/main.py",
line 551, in wsgibase
session._try_store_in_db(request, response)
File
"/base/data/home/apps/s~nittio-live/24.368055561930403768/gluon/globals.py",
line 728, in _try_store_in_db
record_id = table.insert(**dd)
File
"/base/data/home/apps/s~nittio-live/24.368055561930403768/gluon/dal.py",
line 7806, in insert
ret = self._db._adapter.insert(self,self._listify(fields))
File
"/base/data/home/apps/s~nittio-live/24.368055561930403768/gluon/dal.py",
line 4618, in insert
rid = Reference(tmp.key().id())
OverflowError: Python int too large to convert to C long
I'm using Google App Engine - with python 2.7 and web2py.
I have one version of application which was deployed yesterday - this
is
still working (i.e. no such errors during login/logout). I deploy the
same
code today and it does not work. This morning google sent a release
announcement for google app engine 1.8.1. The change was related to
scattered auto ID (64 bits). I'm guessing my problem could be due app
engine change.
Are others facing similar problem? Any known solutions?
Warm Regards,
Aravind.
--
---
You received this message because you are subscribed to the Google Groups "web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
