Uploaded image for project: 'Couchbase Python Client Library'
  1. Couchbase Python Client Library
  2. PYCBC-890

Examine timeout behavior in collection.lookup_in

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Major
    • .backlog3.x
    • 3.0.0-rc
    • library
    • None
    • 1
    • SDK22: Docs,Publish,Pipeline, SDK24: Txnλ+Func,TxnFormer,CoC, SDK26: TxnFunc2,TxnFormer,KS, SDK30: Connect,Txns

    Description

      There is a test, that passes, that sets a 1 microsecond timeout then looks at the result. No timeout. Even on the integration tests.

      So - that can't be. I'm guessing that the timeout isn't being actually used down in the bindings, and so lets take a look. The test in question is in couchbase/tests_v3/cases/collection_t.py - test_lookup_in_timeout. In fact, it is pretty difficult to test timeouts - probably even after fixing we could have some difficulty testing reliably.

      Another approach is to do the work to mock out lcb and check what gets called. If we just had to mock the bindings (_libcouchbase), no problem. But here we would want to actually test the bindings, and whether or not they are calling the timeout correctly. That would be tougher - gotta mock in C. However that is a thing - we could do it.

      But for this ticket, look at the subdoc calls, and surely we will discover the timeout isn't being correctly set, in the bindings, or passed in to the bindings.

      Attachments

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

        Activity

          People

            reilbert Richard Eilbert
            david.kelly David Kelly (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty