durusmail: durus-users: apparently random bug in durus
apparently random bug in durus
2010-06-21
2010-06-21
2010-06-21
2010-06-22
2010-06-22
2010-06-25
2010-06-25
2010-06-25
2010-06-25
2010-06-28
2010-06-28
2010-06-29
Python 2.7+ (Re: apparently random bug in durus)
2010-06-29
2010-06-28
2010-06-29
2010-06-29
2010-06-29
2010-06-29
2010-06-29
2010-06-30
2010-06-30
2010-06-30
2010-06-30
2010-06-30
2010-07-01
apparently random bug in durus
Alex Hall
2010-06-30
Oh, I see. I am not seeing a double installation, though, at least not
as far as I can tell; I only have one durus directory.

On 6/30/10, Binger David  wrote:
>
> On Jun 29, 2010, at 10:17 PM, Alex Hall wrote:
>
>> I am not sure. Would posting this output make any sense on the Qwitter
>> list? That is, would one of the devs be able to help? Q (or maybe it
>> was HLLF) says he found the solution, but you said that what he found
>> is not causing the problem...
>
>
> What I said is that there are *two* problems.
> 1) The double-installation one is one of them, and I think
> that is what causes the durus.durus pickle trouble that you
> have seen.  I don't know what might cause the double
> installation, but Q reports seeing it.
> 2) The other problem, which Q was incorrectly attributing
> to the double-installation problem, was that record in the
> database was corrupted (I think) so that it could not be
> decompressed.  I don't know the reason for the corrupt record.
> I think qwitter might be using one connection from multiple threads,
> and if so, I think that could be the reason.
>
>
>> On Jun 25, 2010, at 6:06 PM, Q wrote:
>>
>>> This issue is actually caused by something a bit more insidious.
>>
>> That's not correct. There are two different problems.
>> One is you have not installed durus properly.  How are you installing it?
>>
>> The other is that the record would not decompress because
>> it is somehow corrupted.
>


--
Have a great day,
Alex (msg sent from GMail website)
mehgcap@gmail.com; http://www.facebook.com/mehgcap
reply