GitLab

License: MIT
Signed-off-by: Brian Tiger Chow <brian@perfmode.com>

this is silly but whatever

License: MIT
Signed-off-by: Brian Tiger Chow <brian@perfmode.com>

@jbenet

License: MIT
Signed-off-by: Brian Tiger Chow <brian@perfmode.com>

@jbenet @whyrusleeping @mappum

very helpful for tracking down errors. the stack traces are only
shown when debug mode is visible. They function best when caught at the
source.

I propose we use this errors package as a drop-in replacement for
fmt.Errorf and errors.New in all of our code, and use errors.Wrap for
external errors as they emerge from others' libraries.

License: MIT
Signed-off-by: Brian Tiger Chow <brian@perfmode.com>
Signed-off-by: Brian Tiger Chow <brian.holderchow@gmail.com>

@jbenet

License: MIT
Signed-off-by: Brian Tiger Chow <brian@perfmode.com>

@jbenet @whyrusleeping @mappum

If we permit initialization in `ipfs daemon`, then we must ensure that
the node instantiated in `ipfs init` (to create the welcome file) shuts
down and releases resources.

Kept running into "resource temporarily unavailable". Discovered that it
was our cousins Jeff and Sanjay over at LevelDB Ave.

go-datastore doesn't expose Close() so I extended the TsDs interface and
submitted a patch.

License: MIT
Signed-off-by: Brian Tiger Chow <brian@perfmode.com>
Signed-off-by: Brian Tiger Chow <brian.holderchow@gmail.com>

to aid in testing

This commit adds a Mount abstraction (which is really just
a wrapped context closer). It makes sure to bind the mount
to the fate of the Node (i.e. close it if the node ends).
This fixes #350

@jbenet

because this method doesn't check actual network status

discovered by @mappum and applied at https://github.com/jbenet/go-ipfs/commit/414e20b71e50b65e40883f3ac85f91aa81c1e486

fixing here to address #233

https://github.com/jbenet/go-ipfs/issues/233

- less floating variables

- distinguish log.Error and log.Errorf functions
- Initialize structs with field names
- A bit of unreachable code (defers)

Changed lots of peer use, and changed the peerstore to ensure
there is only ever one peer in use.

Fixed #174

![](http://m.memegen.com/77n7dk.jpg)

Now, all peers should be retrieved from the Peerstore, which will
construct the peers accordingly. This ensures there's only one peer
object per peer (opposite would be bad: things get out sync)

cc @whyrusleeping

new Service interface

and other logging switches. I kept the u.PErr and u.POut in cli
commands, as those do need to write raw output directly.

    type NameSystem interface {
      Resolver
      Publisher
    }

should say it all.

cc @whyrusleeping