A nice invariant for bitswap sessions:
Senders and receivers can trust that messages do not contain
duplicate blocks or duplicate keys. Backing the message with a
map enforces this invariant.
This comes at the cost of O(n) getters.
@whyrusleeping noticed this a couple days ago
potential long-term fix: prevent duplicate entries in the wantlist by
using a map/set and iterating over this data structure on export
- if equinox says there is a new update, but the version number IS NOT
larger, we interpret that as no update (you may have gotten a newer
version by building it yourself).
- Also export ErrNoUpdateAvailable so clients don't also need to
import the equinox library to check the error.
cc @cryptix comments?
You can use it like this to launch all the
test scripts in order:
$ cd test
$ make
rm -r test-results
*** t0010-basic-commands.sh ***
ok 1 - current dir is writable
ok 2 - ipfs version succeeds
ok 3 - ipfs version output looks good
ok 4 - ipfs help succeeds
ok 5 - ipfs help output looks good
# passed all 5 test(s)
1..5
./test-aggregate-results.sh
fixed 0
success 5
failed 0
broken 0
total 5
Or you can just run one test like this:
$ make t0010-basic-commands.sh
*** t0010-basic-commands.sh ***
ok 1 - current dir is writable
ok 2 - ipfs version succeeds
ok 3 - ipfs version output looks good
ok 4 - ipfs help succeeds
ok 5 - ipfs help output looks good
# passed all 5 test(s)
1..5
This checks a little bit the installation and some
basic commands.
You can run it like that:
$ cd test
$ ./t0010-basic-commands.sh
ok 1 - current dir is writable
ok 2 - ipfs version succeeds
ok 3 - ipfs version output looks good
ok 4 - ipfs help succeeds
ok 5 - ipfs help output looks good
# passed all 5 test(s)
1..5
