Dear Massimo ,

i will try it now , but what is the difference  between the
stable version and the nightly build ?

Best Regards,
Hassan Alnatour



On Fri, Sep 28, 2012 at 7:10 PM, Massimo Di Pierro <
[email protected]> wrote:

> Can you try the web2py nightly build?
>
>
> On Friday, 28 September 2012 10:12:25 UTC-5, Hassan Alnatour wrote:
>
>> Dear Massimo ,
>>
>> i tested on early version of web2py and it works  just fine , can you
>> help me with this please ?
>>
>> Best Regards,
>>
>>
>>
>> On Friday, September 28, 2012 3:44:45 PM UTC+3, Hassan Alnatour wrote:
>>
>>> Dear Massimo ,
>>>
>>> i am getting this not in just on of my apps  , and am not storing
>>> anything in the session , the only thing using it is the login  and i keep
>>> getting this error  when  the user tries to login ..
>>>
>>> Best Regards,
>>> Hassan Alnatour
>>>
>>>
>>>
>>> On Fri, Sep 28, 2012 at 7:39 AM, Massimo Di Pierro <
>>> [email protected]> wrote:
>>>
>>>> You are storing in session something that cannot be properly serialized.
>>>>
>>>>
>>>> On Friday, 28 September 2012 05:47:52 UTC-5, Hassan Alnatour wrote:
>>>>
>>>>> Dear ALL ,
>>>>>
>>>>> i am having some trouble with the new web2py , i have a window server
>>>>> 2008  that i am using apache in to host my sites , now everything was
>>>>> working fine but when i updated web2py , it was okey but every once and
>>>>> while the login stops , i open the server and i do the same thing locally
>>>>> and i dont get any errors and i use the error trace back id and i dont get
>>>>> anything in the trace back , and it only works when i restart apache ?
>>>>>
>>>>> ALL the errors am getting are this :
>>>>>
>>>>> TICKET ID
>>>>>
>>>>> 37.44.32.9.2012-09-28.05-51-**54**.25cc4409-0578-4835-bfaa-**5a51e**
>>>>> 416766d
>>>>>  VERSION web2py™ (2, 0, 9, datetime.datetime(2012, 9, 13, 23, 51,
>>>>> 30), 'stable') TRACEBACK
>>>>>
>>>>> 1.
>>>>> 2.
>>>>> 3.
>>>>> 4.
>>>>> 5.
>>>>> 6.
>>>>> 7.
>>>>> 8.
>>>>> 9.
>>>>> 10.
>>>>> 11.
>>>>> 12.
>>>>> 13.
>>>>> 14.
>>>>> 15.
>>>>> 16.
>>>>> 17.
>>>>> 18.
>>>>> 19.
>>>>> 20.
>>>>> 21.
>>>>> 22.
>>>>> 23.
>>>>> 24.
>>>>> 25.
>>>>> 26.
>>>>> 27.
>>>>>
>>>>> Traceback (most recent call last):
>>>>>
>>>>>
>>>>>   File "C:\web2py\gluon\main.py", line 547, in wsgibase
>>>>>
>>>>>
>>>>>     session._try_store_on_disk(req****uest, response)
>>>>>
>>>>>
>>>>>   File "C:\web2py\gluon\globals.py", line 686, in _try_store_on_disk
>>>>>
>>>>>
>>>>>     cPickle.dump(dict(self), response.session_file)
>>>>>
>>>>>
>>>>>   File "C:\Python27\Lib\copy_reg.py", line 74, in _reduce_ex
>>>>>
>>>>>
>>>>>     getstate = self.__getstate__
>>>>>
>>>>>   File "C:\web2py\gluon\dal.py", line 7344, in __getattr__
>>>>>
>>>>>
>>>>>     self.__allocate()
>>>>>
>>>>>   File "C:\web2py\gluon\dal.py", line 7337, in __allocate
>>>>>
>>>>>
>>>>>     self._record = self._table[int(self)]
>>>>>
>>>>>
>>>>>   File "C:\web2py\gluon\dal.py", line 7624, in __getitem__
>>>>>
>>>>>
>>>>>     return self._db(self._id == key).select(limitby=(0,1)).fir****st()
>>>>>
>>>>>
>>>>>   File "C:\web2py\gluon\dal.py", line 8766, in select
>>>>>
>>>>>
>>>>>     return adapter.select(self.query,fiel****ds,attributes)
>>>>>
>>>>>
>>>>>   File "C:\web2py\gluon\dal.py", line 2094, in select
>>>>>
>>>>>
>>>>>     return super(SQLiteAdapter, self).select(query, fields, attributes)
>>>>>
>>>>>
>>>>>   File "C:\web2py\gluon\dal.py", line 1594, in select
>>>>>
>>>>>
>>>>>     return self._select_aux(sql,fields,at****tributes)
>>>>>
>>>>>
>>>>>   File "C:\web2py\gluon\dal.py", line 1559, in _select_aux
>>>>>
>>>>>
>>>>>     self.execute(sql)
>>>>>
>>>>>   File "C:\web2py\gluon\dal.py", line 1671, in execute
>>>>>
>>>>>
>>>>>     return self.log_execute(*a, **b)
>>>>>
>>>>>
>>>>>   File "C:\web2py\gluon\dal.py", line 1665, in log_execute
>>>>>
>>>>>
>>>>>     ret = self.cursor.execute(*a, **b)
>>>>>
>>>>> ProgrammingError: Cannot operate on a closed database.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> What do you think is the problem ? and how can i solve this ?
>>>>>
>>>>> Best Regards,
>>>>>
>>>>  --
>>>>
>>>>
>>>>
>>>>
>>>
>>>  --
>
>
>
>

-- 



Reply via email to