I just discovered a related issue: With session in memcache: Accessing a page repeatedly without being logged in leads to a changing session_id on every request. This destroys the purpose of a session_id completely... As far as I can see this is caused by _try_store_in_db() which fails to lookup the session
Am Montag, 14. April 2014 08:02:11 UTC+2 schrieb pallav: > > deleting memcache causes a separate issue ( > https://code.google.com/p/web2py/issues/detail?id=1919) that you may be > seeing. > > Basically, your browser now refers to a session that is not in memory > anymore. Web2py looks for the missing key in memdb and crashes. Try > clearing out your browser's sessions and cookies, this will disassociate > your browser from the web2py session, and force the creation of a new > session when you log in. You can also try using incognito mode in chrome to > get a new session. > > On Friday, April 11, 2014 10:04:49 AM UTC-4, David Manns wrote: >> >> Tried this - didn't help >> >> On Thursday, April 10, 2014 5:17:38 PM UTC-4, Sebastian Cambeo wrote: >>> >>> Try deleting memcache and browser cache >>> >>> Am Donnerstag, 10. April 2014 21:13:39 UTC+2 schrieb David Manns: >>>> >>>> I am still seeing this in released version 2.9.5?? >>>> >>>> On Sunday, March 9, 2014 9:04:49 PM UTC-4, Massimo Di Pierro wrote: >>>>> >>>>> This is fixed in trunk. >>>>> >>>>> On Friday, 7 March 2014 21:11:08 UTC-6, Leonardo Pires Felix wrote: >>>>>> >>>>>> Looks like that this is happening with the REDIS too, Upgraded from >>>>>> 2.8.3 to 2.9.4 And the error persist. >>>>>> >>>>>> Traceback (most recent call last): >>>>>> File >>>>>> "/home/leonardo/domains/cef03.com/arquivos/web2py/gluon/restricted.py", >>>>>> line 217, in restricted >>>>>> exec ccode in environment >>>>>> File >>>>>> "/home/leonardo/domains/cef03.com/arquivos/web2py/applications/cef03/models/db.py" >>>>>> <https://cef03.com/admin/default/edit/cef03/models/db.py>, line 62, in >>>>>> <module> >>>>>> session.connect(request, response, db = sessiondb) >>>>>> File >>>>>> "/home/leonardo/domains/cef03.com/arquivos/web2py/gluon/globals.py", >>>>>> line 883, in connect >>>>>> row = table(record_id, unique_key=unique_key) >>>>>> TypeError: __call__() got an unexpected keyword argument 'unique_key' >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> Em terça-feira, 4 de março de 2014 19h37min17s UTC-3, Sebastian >>>>>> Cambeo escreveu: >>>>>>> >>>>>>> I can only provide assistance for the "unique key error": >>>>>>> line 883: >>>>>>> https://github.com/web2py/web2py/blame/master/gluon/globals.py: >>>>>>> dee4e6a9<https://github.com/web2py/web2py/commit/dee4e6a980713f0a3a5bbd350e4b367c4c410327> >>>>>>> >>>>>>> »<https://github.com/web2py/web2py/blame/dee4e6a980713f0a3a5bbd350e4b367c4c410327/gluon/globals.py> >>>>>>> >>>>>>> mdipierro <https://github.com/mdipierro> >>>>>>> 2013-08-20 new session logic >>>>>>> >>>>>>> >>>>>>> I don't know how the "int64 too big" error was introduced >>>>>>> >>>>>>> >>>>>>> >>>>>>> Am Dienstag, 4. März 2014 22:29:56 UTC+1 schrieb Massimo Di Pierro: >>>>>>>> >>>>>>>> can you provide a patch or a revision number that broke it? >>>>>>>> >>>>>>>> On Saturday, 1 March 2014 12:25:14 UTC-6, Bas Ti wrote: >>>>>>>>> >>>>>>>>> The current trunk does not support using memcache as session store >>>>>>>>> on GAE: >>>>>>>>> session.connect calls memdb.Table.__call__(recordid, >>>>>>>>> unique_key=unique_key) >>>>>>>>> >>>>>>>>> however unique_key is not supported by memdb.Table, it is only >>>>>>>>> supported by dal.Table >>>>>>>>> >>>>>>>> -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- 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 web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
