On Sep 3, 7:33 pm, "Nikita V. Youshchenko" <[EMAIL PROTECTED]> wrote:
> > It's third alpha of PyICQt 0.8.1
> > Changes in usability. Yeah, representation x-status -> mood/activity
> > works now :)
>
> Hi,
>
> You may be interested in the following information: today something wired
> happened and pyicqt stopped working for single user here, while continued
> to work for others.
>
> By "stopped working" I mean that it suddenly logged the user out, and on
> attempt to re-login ansered with a message
>
> Undefined condition.
> The error condition is not one of those defined by the other conditions in
> this list.
> ------
> ICQ connection lost! Reason: [Failure instance: Traceback (failure with no
> frames):
> twisted.internet.error.ConnectionLost: Connection to the other side was
> lost in a non-clean fashion.]
>
> This message arrived not immediately after login attempt, but after a
> minute or so.
> During that time, transport status in user's roster was "offline"
>
> The following was logged to pyicqt log file:
>
> [2008-09-03 13:11:53] Traceback (most recent call last):
> File "/usr/local/share/pyicqt/pyicqt-0.8.1a3/src/tlib/oscar.py",
> line 694, in dataReceived
> state=func(flap)
> File "/usr/local/share/pyicqt/pyicqt-0.8.1a3/src/tlib/oscar.py",
> line 805, in oscar_Data
> d.errback(snac)
>
> File "/usr/lib/python2.4/site-packages/twisted/internet/defer.py", line
> 251, in errback
> self._startRunCallbacks(fail)
>
> File "/usr/lib/python2.4/site-packages/twisted/internet/defer.py", line
> 294, in _startRunCallbacks
> self._runCallbacks()
> --- <exception caught here> ---
>
> File "/usr/lib/python2.4/site-packages/twisted/internet/defer.py", line
> 307, in _runCallbacks
> self.result = callback(self.result, *args, **kw)
> File "/usr/local/share/pyicqt/pyicqt-0.8.1a3/src/tlib/oscar.py",
> line 1970, in _cbRequestSSI
> if snac[1] == 0x0f: # same SSI as we have
> exceptions.TypeError: unsubscriptable object
>
> I've tried several things to fix it, including trying the latest version
> (0.8.1a3), and that did not help - I got the same behaviour and the same
> traceback with 0.8.1a3 as well.
>
> However, after an hour or so the problem suddenly disappeared and pyicqt
> started to work correctly for the affected user again.
>
> Since nothing changed at my side, I guess this could be caused by icq
> server
> sending something wired and then stopping doing so. However, maybe it is
> possible to "fix" pyicqt to stop getting TypeError on "strange" input from
> server?
I read today about this problems on ICQ servers. Usual clients like
Pidgin also has it: user can't get contact-list from server. PyICQt
uses server-side contact list and without it can't works in any case.
I think, checking for every packet from server it's bad idea. Of
course, possible fix this current traceback, but it was temporary
problem and may be it don't will repeats in future. And we don't knows
what will after next update on ICQ servers
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"py-transports" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/py-transports?hl=en
-~----------~----~----~----~------~----~------~--~---
