1. 26 Apr, 2017 7 commits
    • kpcyrd's avatar
      dist_get: handle 404 correctly · 49b90a07
      kpcyrd authored
      This prevents a 404 page getting piped into tar.
      
      It's also adding the openbsd http(s) client `ftp`.
      
      License: MIT
      Signed-off-by: default avatarkpcyrd <git@rxv.cc>
      49b90a07
    • Jeromy Johnson's avatar
      Merge pull request #3876 from dgrisham/master · 213358b1
      Jeromy Johnson authored
      bug fix: Bitswap now records 'BytesSent' in ledger
      213358b1
    • Jeromy Johnson's avatar
      Merge pull request #3877 from ipfs/feat/update-cbor · a34c5eac
      Jeromy Johnson authored
      deps: bubble up cbor update
      a34c5eac
    • Lars Gierth's avatar
      deps: bubble up cbor update · 126d249d
      Lars Gierth authored
      License: MIT
      Signed-off-by: default avatarLars Gierth <larsg@systemli.org>
      126d249d
    • dgrisham's avatar
      tests: bitswap ledger tests modified · 4789a622
      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>
      4789a622
    • dgrisham's avatar
      tests + data dependency fix: `BytesSent` bug now completely fixed · 74e19eae
      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>
      74e19eae
    • dgrisham's avatar
      bug fix: `BytesSent` in peers' ledgers now updates · 0514504d
      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>
      0514504d
  2. 24 Apr, 2017 3 commits
  3. 21 Apr, 2017 1 commit
  4. 20 Apr, 2017 5 commits
  5. 19 Apr, 2017 1 commit
  6. 18 Apr, 2017 1 commit
  7. 17 Apr, 2017 3 commits
  8. 15 Apr, 2017 2 commits
  9. 05 Apr, 2017 1 commit
  10. 31 Mar, 2017 2 commits
  11. 30 Mar, 2017 7 commits
  12. 29 Mar, 2017 2 commits
  13. 28 Mar, 2017 1 commit
  14. 27 Mar, 2017 1 commit
  15. 25 Mar, 2017 2 commits
  16. 24 Mar, 2017 1 commit