Skip to content

GitLab

Switch branch/tag
  1. 27 Jul, 2018 1 commit
  3. 16 Jul, 2018 1 commit
  5. 27 Jun, 2018 1 commit
    • Steven Allen's avatar
      gx update · b468efbc
      Steven Allen authored 
      Updates:

* go-kad-dht: Query performance improvements, DHT client fixes, validates
  records on *local* put.
* go-libp2p-swarm/go-libp2p-transport: Timeout improvements.
* go-multiaddr-net: Exposes useful Conn methods (CloseWrite, CloseRead, etc.)
* go-log: fixes possible panic when enabling/disabling events.
* go-multiaddr: fixes possible panic when stringifying malformed multiaddrs,
  adds support for consuming /p2p/ multiaddrs.

fixes #5113
unblocks #4895

License: MIT
Signed-off-by: default avatarSteven Allen <steven@stebalien.com>
      b468efbc
  7. 09 Jun, 2018 1 commit
  9. 01 Jun, 2018 1 commit
  11. 01 Feb, 2018 1 commit
  13. 24 Jan, 2018 1 commit
  15. 29 Dec, 2017 1 commit
  17. 14 Dec, 2017 1 commit
  19. 02 Sep, 2017 1 commit
  21. 12 Jul, 2017 1 commit
  23. 06 Jul, 2017 1 commit
  25. 05 Jul, 2017 1 commit
  27. 04 Jul, 2017 1 commit
  29. 29 Jun, 2017 1 commit
  31. 26 Apr, 2017 1 commit
    • 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
  33. 20 Apr, 2017 1 commit
  35. 06 Mar, 2017 2 commits
  37. 12 Feb, 2017 1 commit
  39. 29 Nov, 2016 1 commit
  41. 22 Nov, 2016 1 commit
  43. 16 Nov, 2016 1 commit
  45. 25 Oct, 2016 1 commit
  47. 12 Oct, 2016 1 commit
    • Jeromy's avatar
      merkledag: change 'Node' to be an interface · abfdac9a
      Jeromy authored 
      Also change existing 'Node' type to 'ProtoNode' and use that most
everywhere for now. As we move forward with the integration we will try
and use the Node interface in more places that we're currently using
ProtoNode.

License: MIT
Signed-off-by: default avatarJeromy <why@ipfs.io>
      abfdac9a
  49. 10 Oct, 2016 1 commit
    • Jeromy's avatar
      bitswap: protocol extension to handle cids · 591491b1
      Jeromy authored 
      This change adds the /ipfs/bitswap/1.1.0 protocol. The new protocol
adds a 'payload' field to the protobuf message and deprecates the
existing 'blocks' field. The 'payload' field is an array of pairs of cid
prefixes and block data. The cid prefixes are used to ensure the correct
codecs and hash functions are used to handle the block on the receiving
end.

License: MIT
Signed-off-by: default avatarJeromy <why@ipfs.io>
      591491b1
  51. 08 Oct, 2016 1 commit
  53. 06 Oct, 2016 1 commit
  55. 29 Sep, 2016 1 commit
  57. 26 Sep, 2016 1 commit
  59. 10 Sep, 2016 1 commit
  61. 09 Sep, 2016 1 commit
  63. 06 Sep, 2016 1 commit
  65. 04 Sep, 2016 1 commit
  67. 03 Sep, 2016 1 commit
  69. 02 Sep, 2016 1 commit
  71. 26 Aug, 2016 1 commit
  73. 24 Aug, 2016 1 commit
  75. 04 Aug, 2016 1 commit
    • Jeromy's avatar
      bitswap: fix a minor data race · 3fbf157a
      Jeromy authored 
      race detector picked up a minor race condition, Since loop iteration
reuses the same local variable, its not safe to take its address and use
it concurrently. The fix is to rebind the variable into a controlled
scope (creating a new variable) and taking the address of that to pass
outwards.

License: MIT
Signed-off-by: default avatarJeromy <why@ipfs.io>
      3fbf157a
  77. 24 Jun, 2016 1 commit