1. 26 4月, 2017 1 次提交
    • bug fix: `BytesSent` in peers' ledgers now updates · 0514504d
      When sending data to another user, the number of bytes sent to that user (saved
      by the corresponding Bitswap ledger) was not updated (it was always 0). This
      also meant that the debt ratio was also always 0.
      
      The function that updates the `BytesSent` value in the ledger, `MessageSent()`,
      was already implemented, however it was not called when the peer was sent data.
      To fix this, a call to `MessageSent()` was made in the `taskWorker()` function,
      which is where both the message in question and the Bitswap engine were
      available to make the call. `MessageSent()` requires the peer's ID and
      `BitSwapMessage` as its arguments, the latter of which had to be created by
      making a new `BitSwapMessage`, then the block being sent was added to the new
      message.
      
      Note that, similar to the analagous call to `MessageReceived()`, records *all*
      of the bytes sent to a particular user. At some point, both of these should be
      updated to only record the numbers of *useful* bytes sent and received between
      peers.
      
      License: MIT
      Signed-off-by: 's avatarDavid Grisham <dgrisham@mines.edu>
      dgrisham 提交于
  2. 24 4月, 2017 3 次提交
  3. 21 4月, 2017 1 次提交
  4. 20 4月, 2017 5 次提交
  5. 19 4月, 2017 1 次提交
  6. 18 4月, 2017 1 次提交
  7. 17 4月, 2017 3 次提交
  8. 15 4月, 2017 2 次提交
  9. 05 4月, 2017 1 次提交
  10. 31 3月, 2017 2 次提交
  11. 30 3月, 2017 7 次提交
  12. 29 3月, 2017 2 次提交
  13. 28 3月, 2017 1 次提交
  14. 27 3月, 2017 1 次提交
  15. 25 3月, 2017 2 次提交
  16. 24 3月, 2017 7 次提交