Permalink
Commits on Oct 29, 2015
  1. @indykish

    Merge pull request #66 from mrb/more_comments

    Fix function name in comment
    indykish committed Oct 29, 2015
Commits on Oct 27, 2015
  1. Merge pull request #67 from megamsys/master

    The code.google.com repo isn't valid any more. Changed the protobuf to golang.org
    committed Oct 27, 2015
Commits on Oct 18, 2015
  1. @indykish

    Merge pull request #2 from indykish/master

    Latest updates from the upstream.
    indykish committed Oct 18, 2015
  2. @indykish
Commits on Sep 15, 2015
  1. Update README.md

    committed Sep 15, 2015
Commits on Aug 25, 2015
  1. Update README.md

    committed Aug 25, 2015
Commits on Aug 6, 2015
  1. Fix function name in comment

    committed Aug 6, 2015
  2. Merge pull request #65 from mrb/cc_test

    Add comments
    committed Aug 6, 2015
  3. Add comments

    committed Aug 6, 2015
Commits on Jun 19, 2015
  1. Exclude tests and generate pb files

    committed Jun 19, 2015
  2. Add ratings

    committed Jun 19, 2015
  3. codeclimate.yml

    committed Jun 19, 2015
Commits on May 12, 2015
  1. @rajthilakmca

    Merge pull request #1 from rajthilakmca/master

    change protobuf location
    rajthilakmca committed May 12, 2015
  2. @rajthilakmca

    change protobuf location

    rajthilakmca committed May 12, 2015
Commits on Nov 8, 2014
  1. Merge pull request #58 from jcoene/master

    Fix null pointer dereference when server goes away
    committed Nov 8, 2014
Commits on Aug 29, 2014
  1. Update README.md

    committed Aug 29, 2014
Commits on Feb 11, 2014
  1. @jcoene
Commits on Dec 8, 2013
  1. Merge pull request #56 from jjmalina/master

    Fix for #54
    committed Dec 8, 2013
Commits on Dec 5, 2013
  1. Merge pull request #57 from hectcastro/hc-error-logging

    Swapped Print/Println statements with Fatalf in example code
    committed Dec 5, 2013
  2. @hectcastro

    Swapped a few Print/Println statements with Fatalf, which is

    equivalent to Printf() followed by a call to os.Exit(1).
    hectcastro committed Dec 4, 2013
Commits on Dec 4, 2013
  1. @jjmalina

    Fix for #54

    jjmalina committed Dec 4, 2013
Commits on Nov 29, 2013
  1. @quirkey

    Merge pull request #55 from paperlesspost/fix_background_ping

    Potential fix for background ping #54
    
    After a couple of days in production, this seemed to do the trick
    quirkey committed Nov 29, 2013
Commits on Nov 26, 2013
  1. @quirkey

    Attempted fix for #54

    When a node returns an error in ReqResp _before_ actually pulling the
    response off the wire, close the tcp connection so that subsequent
    requests dont try pulling the earlier response. Additionally, this
    requires a change to try to re-dialing in the begining of ReqResp if
    the node is not already connected
    quirkey committed Nov 26, 2013
Commits on Nov 24, 2013
  1. @quirkey
Commits on Nov 19, 2013
  1. @boj

    Merge pull request #53 from MattFenelon/master

    Stop the background ping when the client has been closed.
    boj committed Nov 19, 2013
Commits on Nov 15, 2013
  1. @quirkey

    Potential fix for client crash when node returns bad data

    It's possible that a riak node can return a poorly formated response in a
    PING, in this case, the client was crashing because resp was not nil
    but also wasnt something that could be stringified.
    quirkey committed Nov 15, 2013
Commits on Nov 12, 2013
  1. @MattFenelon

    Simplified the closing of the client by removing the boolean flag and…

    … signalling to ping by closing the channel.
    
    time.Ticker was a better fit for what's happening in BackgroundNodePing. I've also removed a possible memory leak by closing the ticker when the client is closed.
    MattFenelon committed Nov 12, 2013
Commits on Nov 6, 2013
  1. @MattFenelon

    Raise an error when calling Close multiple times.

    A non-breaking way of informing informed clients that the client has already been closed.
    MattFenelon committed Nov 6, 2013
Commits on Nov 1, 2013
  1. @MattFenelon

    Switched to using channels rather than locks.

    Suggestion by @mrb.
    MattFenelon committed Nov 1, 2013
  2. @MattFenelon

    Stop the background ping when the client has been closed.

    The for-loop in BackgroundPing continued to run even after Close was called on the client. With a closed client the ping would cause Go to panic. The panic occurs because the node.conn field is set to nil when the node is closed and ping tries to use the field.
    MattFenelon committed Nov 1, 2013
Commits on Oct 4, 2013
  1. @boj

    Update README.md

    boj committed Oct 4, 2013
Commits on Aug 28, 2013
Commits on Aug 27, 2013
Commits on Aug 23, 2013