- 05 Jul, 2015 2 commits
-
-
rht authored
License: MIT Signed-off-by: rht <rhtbot@gmail.com>
-
rht authored
License: MIT Signed-off-by: rht <rhtbot@gmail.com>
-
- 04 Jul, 2015 2 commits
-
-
rht authored
License: MIT Signed-off-by: rht <rhtbot@gmail.com>
-
rht authored
License: MIT Signed-off-by: rht <rhtbot@gmail.com>
-
- 18 Jun, 2015 2 commits
-
-
rht authored
And substitute the lines using Notice{,f} with Info{,f} License: MIT Signed-off-by: rht <rhtbot@gmail.com>
-
rht authored
Except when there is an explicit os.Exit(1) after the Critical line, then replace with Fatal{,f}. golang's log and logrus already call os.Exit(1) by default with Fatal. License: MIT Signed-off-by: rht <rhtbot@gmail.com>
-
- 03 Jun, 2015 1 commit
-
-
Jeromy authored
WIP: object creator command better docs move patch command into object namespace dont ignore cancel funcs addressing comment from CR add two new subcommands to object patch and clean up main Run func cancel contexts in early returns switch to util.Key
-
- 02 Jun, 2015 1 commit
-
-
Jeromy authored
address comments from CR use map and array combo for better perf
-
- 01 Jun, 2015 1 commit
-
-
Jeromy authored
-
- 18 May, 2015 1 commit
-
-
rht authored
-
- 28 Apr, 2015 1 commit
-
-
Henry authored
-
- 20 Apr, 2015 1 commit
-
-
Juan Batiz-Benet authored
We now consider debugerrors harmful: we've run into cases where debugerror.Wrap() hid valuable error information (err == io.EOF?). I've removed them from the main code, but left them in some tests. Go errors are lacking, but unfortunately, this isn't the solution. It is possible that debugerros.New or debugerrors.Errorf should remain still (i.e. only remove debugerrors.Wrap) but we don't use these errors often enough to keep.
-
- 14 Apr, 2015 1 commit
-
-
Jeromy authored
-
- 02 Apr, 2015 1 commit
-
-
Juan Batiz-Benet authored
-
- 01 Apr, 2015 2 commits
- 31 Mar, 2015 1 commit
-
-
Ho-Sheng Hsiao authored
- Modified Godeps/Godeps.json by hand - [TEST] Updated welcome docs hash to sharness - [TEST] Updated contact doc - [TEST] disabled breaking test (t0080-repo refs local)
-
- 30 Mar, 2015 1 commit
-
-
Jeromy authored
Signed-off-by: Jeromy <jeromyj@gmail.com>
-
- 19 Mar, 2015 1 commit
-
-
Juan Batiz-Benet authored
move to a less aggressive period. 5m instead of 20s
-
- 18 Mar, 2015 1 commit
-
-
Jeromy authored
-
- 07 Mar, 2015 4 commits
-
-
Juan Batiz-Benet authored
-
Henry authored
-
Juan Batiz-Benet authored
this time just move to goprocess
-
Juan Batiz-Benet authored
-
- 04 Mar, 2015 1 commit
-
-
Juan Batiz-Benet authored
closes #836
-
- 27 Feb, 2015 4 commits
- 25 Feb, 2015 1 commit
-
-
Henry authored
- updated go-ctxgroup and goprocess ctxgroup: AddChildGroup was changed to AddChild. Used in two files: - p2p/net/mock/mock_net.go - routing/dht/dht.go - updated context from hg repo to git prev. commit in hg was ad01a6fcc8a19d3a4478c836895ffe883bd2ceab. (context: make parentCancelCtx iterative) represents commit 84f8955a887232b6308d79c68b8db44f64df455c in git repo - updated context to master (b6fdb7d8a4ccefede406f8fe0f017fb58265054c) Aaron Jacobs (2): net/context: Don't accept a context in the DoSomethingSlow example. context: Be clear that users must cancel the result of WithCancel. Andrew Gerrand (1): go.net: use golang.org/x/... import paths Bryan C. Mills (1): net/context: Don't leak goroutines in Done example. Damien Neil (1): context: fix removal of cancelled timer contexts from parent David Symonds (2): context: Fix WithValue example code. net: add import comments. Sameer Ajmani (1): context: fix TestAllocs to account for ints in interfaces
-
- 24 Feb, 2015 3 commits
- 15 Feb, 2015 7 commits
-
-
Brian Tiger Chow authored
-
Brian Tiger Chow authored
-
Brian Tiger Chow authored
-
Brian Tiger Chow authored
-
Brian Tiger Chow authored
-
Brian Tiger Chow authored
fix
-
Juan Batiz-Benet authored
Note: the dht-specific part of the bootstrap function was only there to make sure to call `dht.Update(ctx, npeer)`. This already happens on all new connections made by the network, as the dht is signed up for notifications.
-