#572367 Unsnubbing doesn't seem to work

Package:
rtorrent
Source:
rtorrent
Description:
ncurses BitTorrent client based on LibTorrent from rakshasa
Submitter:
Date:
2015-10-28 16:15:04 UTC
Severity:
normal
#572367#5
Date:
2010-03-03 19:00:54 UTC
From:
To:
Toggling peer snubbing off with * seems to leave that peer permanently
choked, even when it wakes up and starts feeding me data.

The only way I can find to bring the connection back to life is to kick
off the peer and let it reconnect.


libtorrent11 0.12.6-2, BTW.

Thank you!

#572367#12
Date:
2010-03-16 19:47:26 UTC
From:
To:
We believe that the bug you reported is fixed in the latest version of
haskell-non-negative, which is due to be installed in the Debian FTP archive:

haskell-non-negative_0.0.5.1-1.diff.gz
  to main/h/haskell-non-negative/haskell-non-negative_0.0.5.1-1.diff.gz
haskell-non-negative_0.0.5.1-1.dsc
  to main/h/haskell-non-negative/haskell-non-negative_0.0.5.1-1.dsc
haskell-non-negative_0.0.5.1.orig.tar.gz
  to main/h/haskell-non-negative/haskell-non-negative_0.0.5.1.orig.tar.gz
libghc6-non-negative-dev_0.0.5.1-1_amd64.deb
  to main/h/haskell-non-negative/libghc6-non-negative-dev_0.0.5.1-1_amd64.deb
libghc6-non-negative-doc_0.0.5.1-1_all.deb
  to main/h/haskell-non-negative/libghc6-non-negative-doc_0.0.5.1-1_all.deb
libghc6-non-negative-prof_0.0.5.1-1_amd64.deb
  to main/h/haskell-non-negative/libghc6-non-negative-prof_0.0.5.1-1_amd64.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 572367@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Marco Túlio Gontijo e Silva <marcot@debian.org> (supplier of updated haskell-non-negative package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)
Format: 1.8
Date: Fri, 05 Mar 2010 09:57:52 -0300
Source: haskell-non-negative
Binary: libghc6-non-negative-dev libghc6-non-negative-prof libghc6-non-negative-doc
Architecture: source all amd64
Version: 0.0.5.1-1
Distribution: unstable
Urgency: low
Maintainer: Debian Haskell Group <pkg-haskell-maintainers@lists.debian.org>
Changed-By: Marco Túlio Gontijo e Silva <marcot@debian.org>
Description:
 libghc6-non-negative-dev - Non-negative numbers for Haskell
 libghc6-non-negative-doc - Non-negative numbers for Haskell; profiling librarie; documentati
 libghc6-non-negative-prof - Non-negative numbers for Haskell; profiling libraries
Closes: 572367
Changes:
 haskell-non-negative (0.0.5.1-1) unstable; urgency=low
 .
   [ Ernesto Hernández-Novich (USB) ]
   * Initial release (Closes: 572367).
 .
   [ Marco Túlio Gontijo e Silva ]
   * debian/copyright: Correct License Name.
   * debian/copyright: Include year in upstream copyright.
Checksums-Sha1:
 c0c4a8df5bd2decfabdd3d320c13d97ddc202ddb 1549 haskell-non-negative_0.0.5.1-1.dsc
 bdf5f551a7ddd767490b9dc438ce40652318c41c 18638 haskell-non-negative_0.0.5.1.orig.tar.gz
 1524e1c012d88030a6b287e140c036ea852b6188 1564 haskell-non-negative_0.0.5.1-1.diff.gz
 16d5e30113bc43377628a22d2e7fcd5145340160 20676 libghc6-non-negative-doc_0.0.5.1-1_all.deb
 a035ce929ee8f02df54a52009bd68112530f4177 66594 libghc6-non-negative-dev_0.0.5.1-1_amd64.deb
 ced03888b18a69188e40660a4e7170dac260a0de 71128 libghc6-non-negative-prof_0.0.5.1-1_amd64.deb
Checksums-Sha256:
 0ca5bf88c25cac2cf9ba418ba436517de3eb81e1652d5d9168573e498fd52f4e 1549 haskell-non-negative_0.0.5.1-1.dsc
 1fd0657dbe45b3bfe58b2ceaedb1e29084eed950c95a8e7b364b295375d6e87c 18638 haskell-non-negative_0.0.5.1.orig.tar.gz
 14b896d31aa89a1aef516136a155304678e50d774caa49c6446bcd3391b3d57e 1564 haskell-non-negative_0.0.5.1-1.diff.gz
 0c1f5d171773b54e0d9d6ecf0fb660f7702311038159d24873ef4cb37e3f2494 20676 libghc6-non-negative-doc_0.0.5.1-1_all.deb
 c882062a333642e445c56e15c7ea49d857630e7f91a4b5cde59b271df17b9841 66594 libghc6-non-negative-dev_0.0.5.1-1_amd64.deb
 250466ccbe186c6eca292a1cb43fb850a413d437ac90ba7f14a1048f6ede9c36 71128 libghc6-non-negative-prof_0.0.5.1-1_amd64.deb
Files:
 e55f3100b5182c5d4e833a75e78d31d4 1549 haskell extra haskell-non-negative_0.0.5.1-1.dsc
 51661a317ada0bb784ca24f76572640b 18638 haskell extra haskell-non-negative_0.0.5.1.orig.tar.gz
 e5ae044cedfd78695f9d670a0530958e 1564 haskell extra haskell-non-negative_0.0.5.1-1.diff.gz
 cd12e1045a24bf1126bff752512cab6e 20676 doc extra libghc6-non-negative-doc_0.0.5.1-1_all.deb
 56f004578151808b22b9221911304dad 66594 haskell extra libghc6-non-negative-dev_0.0.5.1-1_amd64.deb
 becdd866c93a55a5791d998f65ec0e79 71128 haskell extra libghc6-non-negative-prof_0.0.5.1-1_amd64.deb
iEYEARECAAYFAkuRA38ACgkQhAwOmkV1TkTk0wCgnQrKm8T47PqWjAsNFdnCB+NK
Of0AnjZ6P2euLYNItikluztb7OtC1ldQ
=fV0j
-----END PGP SIGNATURE-----

#572367#19
Date:
2010-03-17 11:10:51 UTC
From:
To:
Sorry to bother you, but are you *quite* sure you closed the right bug?
I don't see how a change to a library package I don't have installed
can have any effect on an application that doesn't use that library.

And isn't even written in Haskell.

Perhaps you meant bug #572637 (and not -367)?
Compare
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=572637
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=572367

Thanks!

#572367#24
Date:
2010-03-17 11:36:01 UTC
From:
To:
Hi.

Excerpts from sacrificial-spam-address's message of Qua Mar 17 08:10:51 -0300 2010:
(...)
(...)

Torsten Werner noticed that the bug was wrong, so I already reopened this one.
I should have sent the message to the bug report to keep the record though.

Sorry for the trouble.
(...)

#572367#29
Date:
2012-03-04 17:27:42 UTC
From:
To:
tags 572367 moreinfo
thanks

Hi,

sacrificial-spam-address@horizon.com wrote:

Could you please try version 0.8.9 in wheezy and see if this bug is
still present?

Cheers,

#572367#34
Date:
2012-03-04 17:27:42 UTC
From:
To:
tags 572367 moreinfo
thanks

Hi,

sacrificial-spam-address@horizon.com wrote:

Could you please try version 0.8.9 in wheezy and see if this bug is
still present?

Cheers,

#572367#39
Date:
2012-03-04 18:09:46 UTC
From:
To:
(I'm running sid rather than wheezy; I figure for this purpose that's not
a problem.)

4 peers, each receiving 20 k/s, were snubbed for a second, then
immediately unsnubbed, and their rates have gone to 0 and stayed there.
If I kick them off, they reconnect and start transferring again.
Thank you!

#572367#44
Date:
2012-03-05 09:46:56 UTC
From:
To:
forwarded 572367 https://github.com/rakshasa/rtorrent/issues/37
thanks

sacrificial-spam-address@horizon.com wrote:

Thanks a lot for checking this. I've forwarded it upstream, let's see
what they say.

Cheers,

#572367#53
Date:
2012-03-05 10:12:53 UTC
From:
To:
Benoît Knecht wrote:

In case you're not following the upstream ticket:

Would you be able to build libtorrent [1] and rtorrent [2] from source,
in their latest revision from github, and see if the issue is still
there?

[1] git://github.com/rakshasa/libtorrent.git
[2] git://github.com/rakshasa/rtorrent.git

Cheers,

#572367#58
Date:
2012-03-05 11:20:41 UTC
From:
To:
I'm not; I don't even know where their bug tracker is.
libtorrent ff60f659e3270b995c1df7cec991aec43b62b29f
rtorrent   d25c4b25aec09d19ae10941f7e22b97b00a94bfc

I've only let the connection sit choked for 5 minutes or so, but here:
  IP                       UP     DOWN   PEER   CT/RE/LO  QS    DONE  REQ   SNUB  FAILED
* 78.180.99.43             0.0    0.0    75.1   r /cn/ci  0/0    16                      uTorrent 3.0.0.0
  203.161.79.192           0.0    0.0    163.8  r /Cn/cn  0/0   100                      uTorrent 1.8.5.0
  24.142.56.27             0.0    0.0    163.8  r /Cn/cn  0/0   100                      uTorrent 1.8.5.0
  68.60.53.4               0.0    0.0    163.8  r /Cn/cn  0/0   100                      uTorrent 1.8.5.0
  95.34.190.185            0.0    0.0    163.8  r /Cn/cn  0/0   100                      uTorrent 3.1.2.0
  68.231.118.97            0.0    0.0    163.8  r /cn/ci  0/0   100                      uTorrent 3.0.0.0
  14.201.139.177           0.0    0.0    163.8  r /Cn/cn  0/0   100                      uTorrent 3.0.0.0
  71.127.1.172             0.0    0.0    0.0    R /Cn/cn  0/0    98                      uTorrent 3.1.2.0
  80.202.31.147            0.0    0.0    0.0    R /Cn/cn  0/0   100                      uTorrent 2.2.0.0
  109.224.133.220          0.0    0.0    163.8  r /Cn/cn  0/0   100                      uTorrent 3.1.2.0
  68.114.141.45            0.0    0.0    163.8  r /Cn/cn  0/0   100                      uTorrent 1.8.2.0

That first peer was receiving data at a good clip before I briefly choked it with "*".
If I kick, it'll reconnect in a few seconds and start downloading...

* 78.180.99.43             11.8   0.0    68.3   r /ci/ui  13/0   16                      uTorrent 3.0.0.0

#572367#63
Date:
2012-03-05 11:28:02 UTC
From:
To:
sacrificial-spam-address@horizon.com wrote:

Oh sorry, the link was in a previous mail; here it is again, if you're
interested: https://github.com/rakshasa/rtorrent/issues/37

Wow, that was fast! Thanks again for your great feedback, I'll let
upstream know.

Cheers,

#572367#68
Date:
2015-10-28 16:13:03 UTC
From:
To:
You have received a new fax.



You can find your fax document in the attachment.



Pages sent:        3

Quality:           300 DPI

Fax name:          scan-000153983.doc

Processed in:      42 seconds

Scanned:           Tue, 27 Oct 2015 23:49:15 +0300

File size:         121 Kb

Scanned by:        Juan Carr



Thank you for using Interfax!