Details

    • Type: Bug
    • Status: Resolved
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: 1.1.6
    • Fix Version/s: 1.3.2
    • Component/s: docs
    • Labels:
      None

      Description

      Given the comments on this page: http://www.couchbase.com/docs/couchbase-sdk-net-1.1/couchbase-sdk-net-retrieve-set.html

      Perhaps there can be a section on the possible return codes/values, what they mean, when they might happen, and how to deal with them?

        Issue Links

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

          Hide
          mnunberg Mark Nunberg added a comment -

          This is a must-have for SDK testing. It is very difficult to determine failure types and severities without knowing what types of errors, exception classes, or such to expect.

          At the very least, there should be standard return codes (in a well-defined location) for memcached error codes.

          Show
          mnunberg Mark Nunberg added a comment - This is a must-have for SDK testing. It is very difficult to determine failure types and severities without knowing what types of errors, exception classes, or such to expect. At the very least, there should be standard return codes (in a well-defined location) for memcached error codes.
          Show
          jmorris Jeff Morris added a comment - Possible dupe: http://www.couchbase.com/issues/browse/NCBC-249#comment-77768
          Hide
          jmorris Jeff Morris added a comment -

          Proposed amendment to documentation. Please review and provide feedback.

          Show
          jmorris Jeff Morris added a comment - Proposed amendment to documentation. Please review and provide feedback.
          Hide
          perry Perry Krug added a comment -

          Thanks Jeff, this is a great start and well explained. I think it fits very nicely into our documentation, and just needs to be linked to from a variety of places in order to help people find it.

          I think it would also be helpful to see some examples of handling of some of the more common error codes

          Show
          perry Perry Krug added a comment - Thanks Jeff, this is a great start and well explained. I think it fits very nicely into our documentation, and just needs to be linked to from a variety of places in order to help people find it. I think it would also be helpful to see some examples of handling of some of the more common error codes
          Hide
          jmorris Jeff Morris added a comment -

          Great. I think we should consider this a "work in progress" and do a bit each month. Probably the best way to approach this is to create separate, specific tickets addressing documentation that we are lacking and ad them to the backlog. I'll pull one or two into each monthly "sprint" that I do for a release. From a workflow perspective, I like jira tickets to have a short lifespan...makes me feel more productive

          Show
          jmorris Jeff Morris added a comment - Great. I think we should consider this a "work in progress" and do a bit each month. Probably the best way to approach this is to create separate, specific tickets addressing documentation that we are lacking and ad them to the backlog. I'll pull one or two into each monthly "sprint" that I do for a release. From a workflow perspective, I like jira tickets to have a short lifespan...makes me feel more productive
          Hide
          jmorris Jeff Morris added a comment -

          This will sit underneath: http://docs.couchbase.com/couchbase-sdk-net-1.3/#appendix-working-with-operation-results

          Note that it's no longer listed as an "appendix" but as a section: "Working with Operation Results and Error Codes"

          Will be published with release notes for 1.3.2 on Tuesday.

          Show
          jmorris Jeff Morris added a comment - This will sit underneath: http://docs.couchbase.com/couchbase-sdk-net-1.3/#appendix-working-with-operation-results Note that it's no longer listed as an "appendix" but as a section: "Working with Operation Results and Error Codes" Will be published with release notes for 1.3.2 on Tuesday.

            People

            • Assignee:
              jmorris Jeff Morris
              Reporter:
              perry Perry Krug
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Gerrit Reviews

                There are no open Gerrit changes