Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 272131

Summary: net-p2p/bittorrent-5.0.9-r1 "Message parsing failed" errors
Product: Gentoo Linux Reporter: Pierre-Yves Rofes (RETIRED) <py>
Component: Current packagesAssignee: Gentoo net-p2p team <net-p2p>
Status: RESOLVED TEST-REQUEST    
Severity: minor    
Priority: High    
Version: unspecified   
Hardware: All   
OS: Linux   
URL: https://qa.mandriva.com/show_bug.cgi?id=45620
Whiteboard:
Package list:
Runtime testing required: ---
Bug Depends on:    
Bug Blocks: 336166    
Attachments: Patch for suppressing message parsing failed errors

Description Pierre-Yves Rofes (RETIRED) gentoo-dev 2009-06-01 19:40:23 UTC
Every time I download a torrent, I get tons of these:

Message parsing failed
 <type 'exceptions.KeyError'>: 'dropped'
   File "/usr/lib/python2.5/site-packages/BitTorrent/Connector.py", line 987, in data_came_in
    self._next_len = self._reader.next()

   File "/usr/lib/python2.5/site-packages/BitTorrent/Connector.py", line 664, in _read_messages
    self._got_message(self._message)

   File "/usr/lib/python2.5/site-packages/BitTorrent/Connector.py", line 730, in _got_message
    self._got_utorrent_msg(msg_type, d)

   File "/usr/lib/python2.5/site-packages/BitTorrent/Connector.py", line 693, in _got_utorrent_msg
    dropped_gen = IPTools.uncompact_sequence(d['dropped'])

Downloading and seeding the torrent will still work, but this is cluttering logs. Like $URL says, this is not a 32/64 bit problem, as this happens on x86 and sparc64.

I made a patch to remove the message, but I guess this is more a cheap hack than a real solution.


Reproducible: Always

Steps to Reproduce:
1. Start bittorrent-console
2. watch output
Comment 1 Pierre-Yves Rofes (RETIRED) gentoo-dev 2009-06-01 19:42:11 UTC
Created attachment 193175 [details, diff]
Patch for suppressing message parsing failed errors

Proposed patch.
Comment 2 Ryan Hill (RETIRED) gentoo-dev 2011-03-16 02:42:08 UTC
Please reopen if this is still an issue with 4.4.0-r1/r2.