GitLab

Add Stat to mock net conns and streams

add options for disabling the default listen address/transports

remove some packages from the package table

License: MIT
Signed-off-by: Raúl Kripalani <raul@protocol.ai>

* go-libp2p-coral-dht is currently being written and shouldn't go in this list
  until it's reasonable usable (unless I'm missing the point of this list).
* go-libp2p-ping is an unmaintained extraction of go-libp2p/p2p/ping
* go-libp2p-pubsub is slated to be removed.
* go-libpp2-dummy-conn was implemented to test go-libp2p-pnet. (1)
  go-libp2p-pnet can now be tested with normal `io.ReadWriteCloser`s so it
  doesn't need this package and (2) I didn't bother updating this package when I
  did the libp2p transport refactor.

README: fix go-libp2p-blankhost row

License: MIT
Signed-off-by: Raúl Kripalani <raul@protocol.ai>

feat: use package-table

enhance package list with new items.

License: MIT
Signed-off-by: Raúl Kripalani <raul.kripalani@gmail.com>

License: MIT
Signed-off-by: Henrique Dias <hacdias@gmail.com>

License: MIT
Signed-off-by: Henrique Dias <hacdias@gmail.com>

License: MIT
Signed-off-by: Henrique Dias <hacdias@gmail.com>

License: MIT
Signed-off-by: Henrique Dias <hacdias@gmail.com>

License: MIT
Signed-off-by: Henrique Dias <hacdias@gmail.com>

So, in go-ipfs at least, we *don't* pass the listen addresses into the libp2p
constructor. Instead, we specify them later.

This option allows us to tell libp2p to not listen by default.

Ensure duplicate transports are filtered

always reset ping streams when done

Similar to secure transports in config, if we don't add the transport to
the set, we'll never identify duplicates.

Without adding the transport to the set, we'll never identify if there
are duplicates in the slice of secure transports provided by the config.

mock stream fixes

reset when we fail in identify

Revert "Merge pull request #386 from libp2p/fix/correct-external-addr"

Fix a typo in doc

This reverts commit aca83b9b, reversing
changes made to 86b8929d.

This was is not the correct fix. We already expose these addresses via the
host's AllAddrs method. The real problem is probably that we just don't ever
tell anyone about them (unless we disconnect and reconnect to our nearby DHT
nodes).

We need an address gossip protocol.