Can others reproduce this problem? Is the problem isolated to linkedin? Can you show some code?
On Friday, 12 April 2013 08:44:50 UTC-5, Carl wrote: > > I placed a clean copy of the latest web2py release and added my > application to it (init) and linkedin library plus a couple of yaml files. > > If I run web2py all is fine. But when I run dev_appserver I can the > following error when I try to login using LinkedIn. > The error doesn't look like a valid route as the contrib\memdb.py > shouldn't be used by dev_appserver. > > Any idea what I've done to pull in the wrong version of MemcacheClient? > > ERROR 2013-04-12 13:37:22,867 restricted.py:161] Traceback (most recent > call last): > File "F:\tmp\web2py\gluon\main.py", line 555, in wsgibase > session._try_store_in_db(request, response) > File "F:\tmp\web2py\gluon\globals.py", line 747, in _try_store_in_db > record_id = table.insert(**dd) > File "F:\tmp\web2py\gluon\contrib\memdb.py", line 256, in insert > id = self._create_id() > File "F:\tmp\web2py\gluon\contrib\memdb.py", line 291, in _create_id > id = self._tableobj.incr(shard_id) > AttributeError: 'MemcacheClient' object has no attribute 'incr' > > INFO 2013-04-12 13:37:22,868 gaehandler.py:69] **** Request: > 1547.00ms/1546.63ms (real time/cputime) > INFO 2013-04-12 14:37:22,869 server.py:561] default: "GET > /init/default/user/login?agent=linkedin HTTP/1.1" 500 719 > INFO 2013-04-12 13:37:22,927 gaehandler.py:69] **** Request: > 0.00ms/0.21ms (real time/cpu time) > INFO 2013-04-12 14:37:22,930 server.py:561] default: "GET /favicon.ico > HTTP/1.1" 400 50 > -- --- 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.
