Skip to content

GitLab

Switch branch/tag
  1. 17 Aug, 2017 1 commit
  3. 31 Jul, 2017 1 commit
  5. 28 Jul, 2017 2 commits
  7. 16 Jul, 2017 2 commits
  9. 12 Jul, 2017 1 commit
  11. 11 Jul, 2017 1 commit
  13. 07 Jul, 2017 2 commits
  15. 06 Jul, 2017 2 commits
  17. 05 Jul, 2017 6 commits
  19. 04 Jul, 2017 1 commit
  21. 03 Jul, 2017 1 commit
  23. 29 Jun, 2017 3 commits
  25. 01 Jun, 2017 1 commit
  27. 31 May, 2017 1 commit
  29. 30 May, 2017 1 commit
  31. 23 May, 2017 1 commit
  33. 20 May, 2017 2 commits
  35. 26 Apr, 2017 3 commits
    • dgrisham's avatar
      tests: bitswap ledger tests modified · b649f755
      dgrisham authored 
      Updated the `TestBitswapLedger*` tests and added assertions to check concrete
values for ledgers (rather than just checking that two peers' ledgers match).
The names for these tests were also changed from the previous commit, according
to 's/BytesSent/Ledger/'.

License: MIT
Signed-off-by: default avatarDavid Grisham <dgrisham@mines.edu>
      b649f755
    • dgrisham's avatar
      tests + data dependency fix: `BytesSent` bug now completely fixed · ca0df116
      dgrisham authored 
      Tests were added to ensure that the bug fix in commit 000fbd25 was correct.
The tests caught an error where a peer's ledger was not properly locked when
updating it in the `MessageSent()` function. The appropriate calls to lock the
ledger were made, and the tests successfully passed.

License: MIT
Signed-off-by: default avatarDavid Grisham <dgrisham@mines.edu>
      ca0df116
    • dgrisham's avatar
      bug fix: `BytesSent` in peers' ledgers now updates · bc9342bf
      dgrisham authored 
      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: default avatarDavid Grisham <dgrisham@mines.edu>
      bc9342bf
  37. 20 Apr, 2017 1 commit
  39. 29 Mar, 2017 1 commit
  41. 24 Mar, 2017 1 commit
  43. 06 Mar, 2017 3 commits
  45. 02 Mar, 2017 2 commits