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-07-01
Oh... Probably worth mentioning on the Qwitter list, if you do not
mind; I would, but I am not experienced enough at programming,
especially in Python, to explain things right. It is odd that only
some people experience this when running from source.

On 6/30/10, Binger David  wrote:
>
>>> 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.
>
> A quick look at the qwitter source code makes me think that they
> are using Durus instances from the same Connection in multiple
> threads.  Durus does not support that usage pattern.
>
>


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