Bug 22721

Summary:	Logon fails with large contact list
Product:	Telepathy	Reporter:	Mads Chr. Olesen <shiyee>
Component:	butterfly	Assignee:	Telepathy bugs list <telepathy-bugs>
Status:	RESOLVED NOTABUG	QA Contact:	Telepathy bugs list <telepathy-bugs>
Severity:	normal
Priority:	medium	CC:	lfrb
Version:	unspecified
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Mads Chr. Olesen 2009-07-11 04:33:21 UTC

Logging on with a large contact list fails with "Network error".
I have a complete log from butterfly, but would like to only provide it in private, since it is from a friend of mine.

The relevant lines seem to be:
DEBUG:Transport:>>> BLP 7 BL
DEBUG:Transport:<<< BLP 7 BL
...
DEBUG:Transport:>>> ADL 8 7499
	[payload]
DEBUG:Transport:>>> ADL 9 696
	[payload]
...
DEBUG:Transport:<<< 240 8
ERROR:protocol:Notification got error :240 8
INFO:Butterfly.ConnectionManager:Connection manager quitting

Looking a bit at the code in msnp/notification.py (_address_book_state_changed_cb) reveals that the message seems to be hitting the 7500 byte limit to the size of an ADL message.

I quickly browsed the libpurple source, and in protocols/msn/notification.c there is a comment that "each ADL command may contain up to 150 contacts" - maybe this is useful?

Any further information I can provide?

Comment 1 Louis-Francis Ratté-Boulianne 2009-07-29 20:21:30 UTC

Could you please send me the full log so I can have a look at the error.

Thanks

Comment 2 Louis-Francis Ratté-Boulianne 2010-11-16 14:45:51 UTC

There is no such limit as 150 contacts. I tested it out with 300 contacts in one ADL command and it works fine. There is probably another problem with the contact list.

I think one of the contact might have been on Allow and Block list and that's what caused the error. The bug has been fixed in papyon recently. Anyway, there is no problem with large contact lists.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.