GitLab

Bump github.com/libp2p/go-buffer-pool from 0.0.1 to 0.0.2

Bumps [github.com/libp2p/go-buffer-pool](https://github.com/libp2p/go-buffer-pool) from 0.0.1 to 0.0.2.
- [Release notes](https://github.com/libp2p/go-buffer-pool/releases)
- [Commits](https://github.com/libp2p/go-buffer-pool/compare/v0.0.1...v0.0.2)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

make the maximum message size configurable

combine writes and avoid a few more allocations

This will help secio send fewer packets when negotiating. it _does_ cost us a
copy, but there's not much we can do about that.

Also, drop the channel lock optimization. Uncontested locks are generally pretty
fast anyways (and we don't even use this code).

avoid allocating unless we need to

fix: never claim to read more than read

Not sure if this is the _right_ thing to do but it's better than reporting the
wrong length.

Add gomod, update travis

Improve test coverage

extract buffer pool (and simplify interface)

don't hold the lock when closing

In libp2p, Close is assumed to be threadsafe and we'd like to interrupt
in-progress reads/writes.

As a matter of fact, we're lucky this hasn't caused close to hang. If we had
tried to close the reader before closing the writer, we would have blocked on a
concurrent read call.

Part of ipfs/go-ipfs#2823

Update Travis CI to use standard test script.

This also: removes old go versions; disables sudo; turns off email
notifications and caches gx directories; disables "Non-standard
signatures" check in "go vet" (otherwise "go vet" will complain about
the signature for ReadFrom and WriteTo methods for Chan).