1.3.1

tujikawa
2009-04-08
2012-09-28
  • tujikawa
    tujikawa
    2009-04-08

    I plan to release 1.3.1 in this weekend.
    This release fixes 2 bugs in BitTorrent download.
    These bugs were introduced in 1.3.0 when caching download statistics data for optimization.

    aria2 1.3.1

    Release Note

    This release fixes the bug that aria2 wrongly determines that
    specified share ratio is reached because of miscalculation of upload
    bytes and the bug that upload limit exceeds the value specified in
    --seed-ratio option depending on the timing of the execution of
    SeedCheckCommand.

    Changes

    • Updated README

    • Fixed the bug that upload limit exceeds the value specified in
      --seed-ratio option depending on the timing of the execution of
      SeedCheckCommand.

    • Fixed the bug that removed peer's session upload/download length are
      counted twice in _cachedTransferStat before it is re-calculated.
      This affected the calculation of shara ratio, resulting aria2
      wrongly determines that specified share ratio is reached.

     
    • tujikawa
      tujikawa
      2009-04-09

      I like to improve software quality and release the most updated source code as often as possible.

      I found the bugs by myself. I saw aria2 stopped when share ratio was 0.7 while --share-ratio option is 1.0(default).
      The reproduce step was very easy in my local test environment:running 2 aria2 instance(one for seeder, one for leecher). Stop seeder and re-run it then after leecher finished downloads and disconnected from seeder, I could see that seeder exited with less then 1.0 share ratio.

       
    • Ant Bryan
      Ant Bryan
      2009-04-08

      >I plan to release 1.3.1 in this weekend.
      >This release fixes 2 bugs in BitTorrent download.
      >These bugs were introduced in 1.3.0 when caching download statistics data for optimization.

      awesome, you're always so on top of these tiny bugs that pop up after a release. thanks for taking time to work on such a cool app for us all!

      did you discover them yourself, or were they reported elsewhere? (I didn't see them on SF)