[NCBC-204] JSON extension methods not listed in API references Created: 15/Jan/13  Updated: 18/May/13

Status: Reopened
Project: Couchbase .NET client library
Component/s: docs
Affects Version/s: 1.2.0
Fix Version/s: 1.2.7

Type: Bug Priority: Major
Reporter: Perry Krug Assignee: John Zablocki
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Couldn't find docs around the JSON extension methods listed here:
https://www.couchbase.com/docs/couchbase-sdk-net-1.2/jsonextensions.html

 Comments   
Comment by John Zablocki [ 15/Jan/13 ]
Are you asking for these methods to be included in the API methods along with ExecuteStore, ExecuteGet, etc? Extension methods technically aren't API methods and aren't part of the ICouchbaseClient interface.
Comment by Perry Krug [ 15/Jan/13 ]
Yes, that was what I was asking for. I'm not sure I understand why there are so many different methods for store/get, but since we are recommending customers to store their data as JSON I would assume that these are "first class citizens" and should be documented along with the other methods we support...no?
Comment by John Zablocki [ 15/Jan/13 ]
The JSON extension methods are "opinionated" in that they force you to use JSON.NET for serialization and the default serializer settings that I've included. I don't know that we should recommend these extensions as the "best" option, but rather "an" option. If a user is content to rely on these basic methods, then they would be sufficient. However, there are many users who will prefer other JSON serializers or other class-to-document mapping rules. So rather than attempt to address all JSON concerns with the API, these are convenience methods, which is why they're extension methods. Extension methods in .NET allow a user to treat method like a class method, even though it's not defined in an object's interface.
Comment by Perry Krug [ 15/Jan/13 ]
Thanks for the clarification John.

Can we provide guidance or examples on how to use JSON more generically?
Comment by John Zablocki [ 15/Jan/13 ]
I think that's reasonable. When I update the jsonextensions.html page, I'll try to add "Here's what to do if you don't want to use JSON extensions..."
Comment by Perry Krug [ 15/Jan/13 ]
Thanks John, and will that then link to a piece of our "formal" documentation and API reference?
Comment by John Zablocki [ 17/May/13 ]
http://www.couchbase.com/docs/couchbase-sdk-net-1.2/couchbase-sdk-net-json.html
Comment by Perry Krug [ 18/May/13 ]
Just as a quick re-open...could we link this from the home page of /develop/net/current as well?



[NCBC-188] Provide file based caching of config for stateless .NET apps Created: 21/Dec/12  Updated: 17/May/13

Status: Open
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: None
Fix Version/s: 1.3

Type: New Feature Priority: Major
Reporter: John Zablocki Assignee: John Zablocki
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
With stateless apps, such as WCF, it's not possible to create a static client variable that is used across the lifetime of the app. An alternate approach would be to write config to a file and update it periodically instead of bootstrapping with each object creation.



[NCBC-175] Authenticated view tests should use app.config Created: 07/Dec/12  Updated: 17/May/13

Status: Open
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: 1.2 Beta-3, 1.2.0
Fix Version/s: 1.3

Type: Bug Priority: Major
Reporter: John Zablocki Assignee: John Zablocki
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified




[NCBC-173] Use Couchbase.Management API to create buckets and views for unit tests requiring custom setups Created: 07/Dec/12  Updated: 17/May/13

Status: Open
Project: Couchbase .NET client library
Component/s: library
Affects Version/s: 1.2.0
Fix Version/s: 1.2.8

Type: Improvement Priority: Major
Reporter: John Zablocki Assignee: John Zablocki
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified




[NCBC-153] InvalidOperationException in views during server restart Created: 12/Nov/12  Updated: 17/May/13

Status: In Progress
Project: Couchbase .NET client library
Component/s: library
Affects Version/s: 1.2 Beta
Fix Version/s: 1.2.8

Type: Bug Priority: Major
Reporter: Mark Nunberg Assignee: John Zablocki
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
'service couchbase-server restart' on the (only) node.

While it's easy to understand the reason for these errors, they should be wrapped a bit nicer. This is with doing GetItem() on each view request (and running them all inside a tight loop).

[Couchbase.MessageStreamListener|Warn] Current node 'http://10.0.0.99:8091/pools/default/bucketsStreaming/default?bucket
_uuid=e0a080ddc9d74fa3adbcbb9385f2ceae' has failed.
[Couchbase.MessageStreamListener|Warn] Could not found a working node.
[Couchbase.MessageStreamListener|Warn] All nodes are dead, sleeping for a while.
[Enyim.Caching.Memcached.MemcachedNode|Error] System.IO.IOException: Failed to read from the socket '10.0.0.99:11210'. E
rror: ConnectionReset
   at Enyim.Caching.Memcached.PooledSocket.BasicNetworkStream.Read(Byte[] buffer, Int32 offset, Int32 count) in F:\couch
base-net-client\lib\EnyimMemcached\Enyim.Caching\Memcached\BasicNetworkStream.cs:line 92
   at System.IO.BufferedStream.Read(Byte[] array, Int32 offset, Int32 count)
   at Enyim.Caching.Memcached.PooledSocket.Read(Byte[] buffer, Int32 offset, Int32 count) in F:\couchbase-net-client\lib
\EnyimMemcached\Enyim.Caching\Memcached\PooledSocket.cs:line 222
   at Enyim.Caching.Memcached.Protocol.Binary.BinaryResponse.Read(PooledSocket socket) in F:\couchbase-net-client\lib\En
yimMemcached\Enyim.Caching\Memcached\Protocol\Binary\BinaryResponse.cs:line 57
   at Enyim.Caching.Memcached.Protocol.Binary.BinarySingleItemOperation.ReadResponse(PooledSocket socket) in F:\couchbas
e-net-client\lib\EnyimMemcached\Enyim.Caching\Memcached\Protocol\Binary\BinarySingleItemOperation.cs:line 24
   at Enyim.Caching.Memcached.Protocol.Operation.Enyim.Caching.Memcached.IOperation.ReadResponse(PooledSocket socket) in
 F:\couchbase-net-client\lib\EnyimMemcached\Enyim.Caching\Memcached\Protocol\Operation.cs:line 27
   at Enyim.Caching.Memcached.MemcachedNode.ExecuteOperation(IOperation op) in F:\couchbase-net-client\lib\EnyimMemcache
d\Enyim.Caching\Memcached\MemcachedNode.cs:line 550
[Enyim.Caching.Memcached.MemcachedNode|Error] System.IO.IOException: Failed to read from the socket '10.0.0.99:11210'. E
rror: ConnectionReset
   at Enyim.Caching.Memcached.PooledSocket.BasicNetworkStream.Read(Byte[] buffer, Int32 offset, Int32 count) in F:\couch
base-net-client\lib\EnyimMemcached\Enyim.Caching\Memcached\BasicNetworkStream.cs:line 92
   at System.IO.BufferedStream.Read(Byte[] array, Int32 offset, Int32 count)
   at Enyim.Caching.Memcached.PooledSocket.Read(Byte[] buffer, Int32 offset, Int32 count) in F:\couchbase-net-client\lib
\EnyimMemcached\Enyim.Caching\Memcached\PooledSocket.cs:line 222
   at Enyim.Caching.Memcached.Protocol.Binary.BinaryResponse.Read(PooledSocket socket) in F:\couchbase-net-client\lib\En
yimMemcached\Enyim.Caching\Memcached\Protocol\Binary\BinaryResponse.cs:line 57
   at Enyim.Caching.Memcached.Protocol.Binary.BinarySingleItemOperation.ReadResponse(PooledSocket socket) in F:\couchbas
e-net-client\lib\EnyimMemcached\Enyim.Caching\Memcached\Protocol\Binary\BinarySingleItemOperation.cs:line 24
   at Enyim.Caching.Memcached.Protocol.Operation.Enyim.Caching.Memcached.IOperation.ReadResponse(PooledSocket socket) in
 F:\couchbase-net-client\lib\EnyimMemcached\Enyim.Caching\Memcached\Protocol\Operation.cs:line 27
   at Enyim.Caching.Memcached.MemcachedNode.ExecuteOperation(IOperation op) in F:\couchbase-net-client\lib\EnyimMemcache
d\Enyim.Caching\Memcached\MemcachedNode.cs:line 550
[Couchbase.CouchbaseView|Warn] View Couchbase.CouchbaseView was mapped to a dead node, failing.
[Couchbase.CouchbaseView|Warn] View Couchbase.CouchbaseView was mapped to a dead node, failing.
[Couchbase.CouchbaseView|Warn] View Couchbase.CouchbaseView was mapped to a dead node, failing.


Unhandled Exception:Unhandled Exception: [Couchbase.CouchbaseView|Warn] View Couchbase.CouchbaseView was mapped to a dea
d node, failing.

[Couchbase.CouchbaseView|Warn] View Couchbase.CouchbaseView was mapped to a dead node, failing.
Unhandled Exception:[Couchbase.CouchbaseView|Warn] View Couchbase.CouchbaseView was mapped to a dead node, failing.


[Couchbase.CouchbaseView|Warn] View Couchbase.CouchbaseView was mapped to a dead node, failing.
System.InvalidOperationException: Operation is not valid due to the current state of the object.
   at Couchbase.CouchbaseViewBase`1.GetResponse() in F:\couchbase-net-client\src\Couchbase\CouchbaseViewBase.cs:line 209

   at Couchbase.CouchbaseViewBase`1.<TransformResults>d__0`1.MoveNext() in F:\couchbase-net-client\src\Couchbase\Couchba
seViewBase.cs:line 95
   at Sdkd.Views.ViewCommand.Run() in F:\sdkd-net\src\Sdkd\Views\ViewCommand.cs:line 219
   at SdkdConsole.Daemon.Handle.dispatchCommand(Request req) in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 177
   at SdkdConsole.Daemon.Handle.Run() in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 110
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, B
oolean ignoreSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()
Unhandled Exception:Unhandled Exception:[Couchbase.CouchbaseView|Warn] View Couchbase.CouchbaseView was mapped to a dead
 node, failing.


System.InvalidOperationException: Operation is not valid due to the current state of the object.
   at Couchbase.CouchbaseViewBase`1.GetResponse() in F:\couchbase-net-client\src\Couchbase\CouchbaseViewBase.cs:line 209

   at Couchbase.CouchbaseViewBase`1.<TransformResults>d__0`1.MoveNext() in F:\couchbase-net-client\src\Couchbase\Couchba
seViewBase.cs:line 95
   at Sdkd.Views.ViewCommand.Run() in F:\sdkd-net\src\Sdkd\Views\ViewCommand.cs:line 219
   at SdkdConsole.Daemon.Handle.dispatchCommand(Request req) in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 177
   at SdkdConsole.Daemon.Handle.Run() in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 110
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, B
oolean ignoreSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart() System.InvalidOperationException: Operation is not valid due to the cu
rrent state of the object.
   at Couchbase.CouchbaseViewBase`1.GetResponse() in F:\couchbase-net-client\src\Couchbase\CouchbaseViewBase.cs:line 209

   at Couchbase.CouchbaseViewBase`1.<TransformResults>d__0`1.MoveNext() in F:\couchbase-net-client\src\Couchbase\Couchba
seViewBase.cs:line 95
   at Sdkd.Views.ViewCommand.Run() in F:\sdkd-net\src\Sdkd\Views\ViewCommand.cs:line 219
   at SdkdConsole.Daemon.Handle.dispatchCommand(Request req) in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 177
   at SdkdConsole.Daemon.Handle.Run() in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 110
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, B
oolean ignoreSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart() [Couchbase.CouchbaseView|Warn] View Couchbase.CouchbaseView was mapped
 to a dead node, failing.

Unhandled Exception:

[Couchbase.CouchbaseView|Warn] View Couchbase.CouchbaseView was mapped to a dead node, failing.
Unhandled Exception:
[Couchbase.CouchbaseView|Warn] View Couchbase.CouchbaseView was mapped to a dead node, failing.

 Unhandled Exception:System.InvalidOperationException: Operation is not valid due to the current state of the object.
   at Couchbase.CouchbaseViewBase`1.GetResponse() in F:\couchbase-net-client\src\Couchbase\CouchbaseViewBase.cs:line 209

   at Couchbase.CouchbaseViewBase`1.<TransformResults>d__0`1.MoveNext() in F:\couchbase-net-client\src\Couchbase\Couchba
seViewBase.cs:line 95
   at Sdkd.Views.ViewCommand.Run() in F:\sdkd-net\src\Sdkd\Views\ViewCommand.cs:line 219
   at SdkdConsole.Daemon.Handle.dispatchCommand(Request req) in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 177
   at SdkdConsole.Daemon.Handle.Run() in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 110
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, B
oolean ignoreSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()System.InvalidOperationException: Operation is not valid due to the cur
rent state of the object.
   at Couchbase.CouchbaseViewBase`1.GetResponse() in F:\couchbase-net-client\src\Couchbase\CouchbaseViewBase.cs:line 209

   at Couchbase.CouchbaseViewBase`1.<TransformResults>d__0`1.MoveNext() in F:\couchbase-net-client\src\Couchbase\Couchba
seViewBase.cs:line 95
   at Sdkd.Views.ViewCommand.Run() in F:\sdkd-net\src\Sdkd\Views\ViewCommand.cs:line 219
   at SdkdConsole.Daemon.Handle.dispatchCommand(Request req) in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 177
   at SdkdConsole.Daemon.Handle.Run() in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 110
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, B
oolean ignoreSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()[Couchbase.CouchbaseView|Warn] View Couchbase.CouchbaseView was mapped
to a dead node, failing.


Unhandled Exception:
Unhandled Exception:[Couchbase.CouchbaseView|Warn] View Couchbase.CouchbaseView was mapped to a dead node, failing.

 System.InvalidOperationException: Operation is not valid due to the current state of the object.
   at Couchbase.CouchbaseViewBase`1.GetResponse() in F:\couchbase-net-client\src\Couchbase\CouchbaseViewBase.cs:line 209

   at Couchbase.CouchbaseViewBase`1.<TransformResults>d__0`1.MoveNext() in F:\couchbase-net-client\src\Couchbase\Couchba
seViewBase.cs:line 95
   at Sdkd.Views.ViewCommand.Run() in F:\sdkd-net\src\Sdkd\Views\ViewCommand.cs:line 219
   at SdkdConsole.Daemon.Handle.dispatchCommand(Request req) in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 177
   at SdkdConsole.Daemon.Handle.Run() in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 110
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, B
oolean ignoreSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart() [Couchbase.CouchbaseView|Warn] View Couchbase.CouchbaseView was mapped
 to a dead node, failing.

Unhandled Exception:System.InvalidOperationException: Operation is not valid due to the current state of the object.
   at Couchbase.CouchbaseViewBase`1.GetResponse() in F:\couchbase-net-client\src\Couchbase\CouchbaseViewBase.cs:line 209

   at Couchbase.CouchbaseViewBase`1.<TransformResults>d__0`1.MoveNext() in F:\couchbase-net-client\src\Couchbase\Couchba
seViewBase.cs:line 95
   at Sdkd.Views.ViewCommand.Run() in F:\sdkd-net\src\Sdkd\Views\ViewCommand.cs:line 219
   at SdkdConsole.Daemon.Handle.dispatchCommand(Request req) in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 177
   at SdkdConsole.Daemon.Handle.Run() in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 110
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, B
oolean ignoreSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()
[Couchbase.CouchbaseView|Warn] View Couchbase.CouchbaseView was mapped to a dead node, failing.
Unhandled Exception:
 System.InvalidOperationException: Operation is not valid due to the current state of the object.
   at Couchbase.CouchbaseViewBase`1.GetResponse() in F:\couchbase-net-client\src\Couchbase\CouchbaseViewBase.cs:line 209

   at Couchbase.CouchbaseViewBase`1.<TransformResults>d__0`1.MoveNext() in F:\couchbase-net-client\src\Couchbase\Couchba
seViewBase.cs:line 95
   at Sdkd.Views.ViewCommand.Run() in F:\sdkd-net\src\Sdkd\Views\ViewCommand.cs:line 219
   at SdkdConsole.Daemon.Handle.dispatchCommand(Request req) in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 177
   at SdkdConsole.Daemon.Handle.Run() in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 110
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, B
oolean ignoreSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()
[Couchbase.CouchbaseView|Warn] View Couchbase.CouchbaseView was mapped to a dead node, failing.

 Unhandled Exception:System.InvalidOperationException: Operation is not valid due to the current state of the object.
   at Couchbase.CouchbaseViewBase`1.GetResponse() in F:\couchbase-net-client\src\Couchbase\CouchbaseViewBase.cs:line 209

   at Couchbase.CouchbaseViewBase`1.<TransformResults>d__0`1.MoveNext() in F:\couchbase-net-client\src\Couchbase\Couchba
seViewBase.cs:line 95
   at Sdkd.Views.ViewCommand.Run() in F:\sdkd-net\src\Sdkd\Views\ViewCommand.cs:line 219
   at SdkdConsole.Daemon.Handle.dispatchCommand(Request req) in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 177
   at SdkdConsole.Daemon.Handle.Run() in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 110
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, B
oolean ignoreSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()
System.InvalidOperationException: Operation is not valid due to the current state of the object.
   at Couchbase.CouchbaseViewBase`1.GetResponse() in F:\couchbase-net-client\src\Couchbase\CouchbaseViewBase.cs:line 209

   at Couchbase.CouchbaseViewBase`1.<TransformResults>d__0`1.MoveNext() in F:\couchbase-net-client\src\Couchbase\Couchba
seViewBase.cs:line 95
   at Sdkd.Views.ViewCommand.Run() in F:\sdkd-net\src\Sdkd\Views\ViewCommand.cs:line 219
   at SdkdConsole.Daemon.Handle.dispatchCommand(Request req) in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 177
   at SdkdConsole.Daemon.Handle.Run() in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 110
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, B
oolean ignoreSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()[Couchbase.CouchbaseView|Warn] View Couchbase.CouchbaseView was mapped
to a dead node, failing.

Unhandled Exception:

[Couchbase.CouchbaseView|Warn] View Couchbase.CouchbaseView was mapped to a dead node, failing.

Unhandled Exception: System.InvalidOperationException: Operation is not valid due to the current state of the object.
   at Couchbase.CouchbaseViewBase`1.GetResponse() in F:\couchbase-net-client\src\Couchbase\CouchbaseViewBase.cs:line 209

   at Couchbase.CouchbaseViewBase`1.<TransformResults>d__0`1.MoveNext() in F:\couchbase-net-client\src\Couchbase\Couchba
seViewBase.cs:line 95
   at Sdkd.Views.ViewCommand.Run() in F:\sdkd-net\src\Sdkd\Views\ViewCommand.cs:line 219
   at SdkdConsole.Daemon.Handle.dispatchCommand(Request req) in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 177
   at SdkdConsole.Daemon.Handle.Run() in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 110
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, B
oolean ignoreSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()[Couchbase.CouchbaseView|Warn] View Couchbase.CouchbaseView was mapped
to a dead node, failing.

 Unhandled Exception:
System.InvalidOperationException: Operation is not valid due to the current state of the object.
   at Couchbase.CouchbaseViewBase`1.GetResponse() in F:\couchbase-net-client\src\Couchbase\CouchbaseViewBase.cs:line 209

   at Couchbase.CouchbaseViewBase`1.<TransformResults>d__0`1.MoveNext() in F:\couchbase-net-client\src\Couchbase\Couchba
seViewBase.cs:line 95
   at Sdkd.Views.ViewCommand.Run() in F:\sdkd-net\src\Sdkd\Views\ViewCommand.cs:line 219
   at SdkdConsole.Daemon.Handle.dispatchCommand(Request req) in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 177
   at SdkdConsole.Daemon.Handle.Run() in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 110
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, B
oolean ignoreSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()Unhandled Exception:[Couchbase.CouchbaseView|Warn] View Couchbase.Couch
baseView was mapped to a dead node, failing.


System.InvalidOperationException: Operation is not valid due to the current state of the object.
   at Couchbase.CouchbaseViewBase`1.GetResponse() in F:\couchbase-net-client\src\Couchbase\CouchbaseViewBase.cs:line 209

   at Couchbase.CouchbaseViewBase`1.<TransformResults>d__0`1.MoveNext() in F:\couchbase-net-client\src\Couchbase\Couchba
seViewBase.cs:line 95
   at Sdkd.Views.ViewCommand.Run() in F:\sdkd-net\src\Sdkd\Views\ViewCommand.cs:line 219
   at SdkdConsole.Daemon.Handle.dispatchCommand(Request req) in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 177
   at SdkdConsole.Daemon.Handle.Run() in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 110
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, B
oolean ignoreSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()
Unhandled Exception:System.InvalidOperationException: Operation is not valid due to the current state of the object.
   at Couchbase.CouchbaseViewBase`1.GetResponse() in F:\couchbase-net-client\src\Couchbase\CouchbaseViewBase.cs:line 209

   at Couchbase.CouchbaseViewBase`1.<TransformResults>d__0`1.MoveNext() in F:\couchbase-net-client\src\Couchbase\Couchba
seViewBase.cs:line 95
   at Sdkd.Views.ViewCommand.Run() in F:\sdkd-net\src\Sdkd\Views\ViewCommand.cs:line 219
   at SdkdConsole.Daemon.Handle.dispatchCommand(Request req) in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 177
   at SdkdConsole.Daemon.Handle.Run() in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 110
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, B
oolean ignoreSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()
Unhandled Exception:System.InvalidOperationException: Operation is not valid due to the current state of the object.
   at Couchbase.CouchbaseViewBase`1.GetResponse() in F:\couchbase-net-client\src\Couchbase\CouchbaseViewBase.cs:line 209

   at Couchbase.CouchbaseViewBase`1.<TransformResults>d__0`1.MoveNext() in F:\couchbase-net-client\src\Couchbase\Couchba
seViewBase.cs:line 95
   at Sdkd.Views.ViewCommand.Run() in F:\sdkd-net\src\Sdkd\Views\ViewCommand.cs:line 219
   at SdkdConsole.Daemon.Handle.dispatchCommand(Request req) in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 177
   at SdkdConsole.Daemon.Handle.Run() in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 110
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, B
oolean ignoreSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()
 Unhandled Exception:
System.InvalidOperationException: Operation is not valid due to the current state of the object.
   at Couchbase.CouchbaseViewBase`1.GetResponse() in F:\couchbase-net-client\src\Couchbase\CouchbaseViewBase.cs:line 209

   at Couchbase.CouchbaseViewBase`1.<TransformResults>d__0`1.MoveNext() in F:\couchbase-net-client\src\Couchbase\Couchba
seViewBase.cs:line 95
   at Sdkd.Views.ViewCommand.Run() in F:\sdkd-net\src\Sdkd\Views\ViewCommand.cs:line 219
   at SdkdConsole.Daemon.Handle.dispatchCommand(Request req) in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 177
   at SdkdConsole.Daemon.Handle.Run() in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 110
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, B
oolean ignoreSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart() System.InvalidOperationException: Operation is not valid due to the cu
rrent state of the object.
   at Couchbase.CouchbaseViewBase`1.GetResponse() in F:\couchbase-net-client\src\Couchbase\CouchbaseViewBase.cs:line 209

   at Couchbase.CouchbaseViewBase`1.<TransformResults>d__0`1.MoveNext() in F:\couchbase-net-client\src\Couchbase\Couchba
seViewBase.cs:line 95
   at Sdkd.Views.ViewCommand.Run() in F:\sdkd-net\src\Sdkd\Views\ViewCommand.cs:line 219
   at SdkdConsole.Daemon.Handle.dispatchCommand(Request req) in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 177
   at SdkdConsole.Daemon.Handle.Run() in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 110
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, B
oolean ignoreSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()

System.InvalidOperationException: Operation is not valid due to the current state of the object.
   at Couchbase.CouchbaseViewBase`1.GetResponse() in F:\couchbase-net-client\src\Couchbase\CouchbaseViewBase.cs:line 209

   at Couchbase.CouchbaseViewBase`1.<TransformResults>d__0`1.MoveNext() in F:\couchbase-net-client\src\Couchbase\Couchba
seViewBase.cs:line 95
   at Sdkd.Views.ViewCommand.Run() in F:\sdkd-net\src\Sdkd\Views\ViewCommand.cs:line 219
   at SdkdConsole.Daemon.Handle.dispatchCommand(Request req) in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 177
   at SdkdConsole.Daemon.Handle.Run() in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 110
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, B
oolean ignoreSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()System.InvalidOperationException: Operation is not valid due to the cur
rent state of the object.
   at Couchbase.CouchbaseViewBase`1.GetResponse() in F:\couchbase-net-client\src\Couchbase\CouchbaseViewBase.cs:line 209

   at Couchbase.CouchbaseViewBase`1.<TransformResults>d__0`1.MoveNext() in F:\couchbase-net-client\src\Couchbase\Couchba
seViewBase.cs:line 95
   at Sdkd.Views.ViewCommand.Run() in F:\sdkd-net\src\Sdkd\Views\ViewCommand.cs:line 219
   at SdkdConsole.Daemon.Handle.dispatchCommand(Request req) in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 177
   at SdkdConsole.Daemon.Handle.Run() in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 110
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, B
oolean ignoreSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()

System.InvalidOperationException: Operation is not valid due to the current state of the object.
   at Couchbase.CouchbaseViewBase`1.GetResponse() in F:\couchbase-net-client\src\Couchbase\CouchbaseViewBase.cs:line 209

   at Couchbase.CouchbaseViewBase`1.<TransformResults>d__0`1.MoveNext() in F:\couchbase-net-client\src\Couchbase\Couchba
seViewBase.cs:line 95
   at Sdkd.Views.ViewCommand.Run() in F:\sdkd-net\src\Sdkd\Views\ViewCommand.cs:line 219
   at SdkdConsole.Daemon.Handle.dispatchCommand(Request req) in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 177
   at SdkdConsole.Daemon.Handle.Run() in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 110
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, B
oolean ignoreSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()


 Comments   
Comment by Mark Nunberg [ 12/Nov/12 ]
Of course the code blatantly throws this exception. I would think perhaps a bit something less severe would do? Maybe a WebException with a code of 400 (standard code for client-side errors); and maybe with some kind of simple retry?



[NCBC-73] Need better explanation of usage and return values of increment operation (and likely others) Created: 26/Jun/12  Updated: 17/May/13

Status: Open
Project: Couchbase .NET client library
Component/s: docs
Affects Version/s: 1.1.6
Fix Version/s: 1.2.8

Type: Bug Priority: Major
Reporter: Perry Krug Assignee: John Zablocki
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
The current docs for incrememnt: http://www.couchbase.com/docs/couchbase-sdk-net-1.1/couchbase-sdk-net-update-increment.html

Can there be some attention paid to the above documentation (and will likely be needed across the board in similar areas):
-Some return values say: CasResult<ulong> (Cas result of bool). What is "Cas result of bool"?
-Other return values say: IMutateOperationResult (Mutate operation result). Is the same operation really expected to return drastically different object types?
-Some examples have "var casv = client.GetWithCas("inventory");" before performing the increment. Is it necessary to get the CAS id before performing this type of increment? Is it necessary to supply the CAS id for this type of increment?
-Some examples have very simply usage, others have more detail:
var getResult = client.ExecuteGet("inventory");

if (getResult.Success) {
var mutateResult client.ExecuteIncrement("inventory", 100, 1, getResult.Cas);

if (mutateResult.Success) {
logger.Debug("New value: " + mutateResult.Value);
}
}

-Can all of the examples be made consistent, and/or just have a single example at the top showing how to perform the incremement and work with the result. Then the various optional methods can be shown below?
-There seems to be a fair amount of duplication within the methods provided. For example, the last two are exactly the same (even have the same typo on "numvers") and there are other seemingly duplicates throughout.



[NCBC-68] Getting a thread abort (ocassionally) on store Created: 13/Jun/12  Updated: 17/May/13

Status: Open
Project: Couchbase .NET client library
Component/s: library
Affects Version/s: None
Fix Version/s: 1.2.8

Type: Bug Priority: Major
Reporter: Mike Wiederhold Assignee: John Zablocki
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
http://www.couchbase.com/forums/thread/getting-thread-abort-ocassionally-store

Please follow up with this user on the forums after resolving this issue.

We are using the c# client to hit a couchbase 1.8 membase bucket. Every once in while (enough were it's bad) we are getting thread aborts during the store call. Here is the full stack of the error.

2012-06-11 02:59:39,819 [10] ERROR Knotice.Caching [(null)] <(null)> - Failed to add object to L2 cache with key: 297of type:SimpleDatabase msg:Thread was being aborted.
System.Threading.ThreadAbortException: Thread was being aborted.
   at System.Net.UnsafeNclNativeMethods.OSSOCK.recv(IntPtr socketHandle, Byte* pinnedBuffer, Int32 len, SocketFlags socketFlags)
   at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags, SocketError& errorCode)
   at Enyim.Caching.Memcached.PooledSocket.BasicNetworkStream.Read(Byte[] buffer, Int32 offset, Int32 count)
   at System.IO.BufferedStream.Read(Byte[] array, Int32 offset, Int32 count)
   at Enyim.Caching.Memcached.PooledSocket.Read(Byte[] buffer, Int32 offset, Int32 count)
   at Enyim.Caching.Memcached.Protocol.Binary.BinaryResponse.Read(PooledSocket socket)
   at Enyim.Caching.Memcached.Protocol.Binary.BinarySingleItemOperation.ReadResponse(PooledSocket socket)
   at Enyim.Caching.Memcached.MemcachedNode.ExecuteOperation(IOperation op)
   at Couchbase.CouchbaseClient.ExecuteWithRedirect(IMemcachedNode startNode, ISingleItemOperation op)
   at Couchbase.CouchbaseClient.PerformStore(StoreMode mode, String key, Object value, UInt32 expires, UInt64& cas, Int32& statusCode)
   at Enyim.Caching.MemcachedClient.Store(StoreMode mode, String key, Object value, DateTime expiresAt)
   at Knotice.Caching.CacheManager.Store(Object key, Object item, Type type, Int32 tenantId, CacheSettings settings) in d:\Temp\Concentri\Dev - Full Build\Sources\Lib\Caching\Knotice.Caching\CacheManager.cs:line 109



[NCBC-29] programmatically set all the Couchbase configurations Created: 07/Mar/12  Updated: 17/May/13

Status: Open
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: None
Fix Version/s: 1.3

Type: New Feature Priority: Major
Reporter: James Mauss Assignee: John Zablocki
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
We can programmatically set some the Couchbase configurations, however we cannot set the SocketPool settings Programmatically.

These settings can be set in the config file, but it would be nice to be able to set these through the program.



[NCBC-4] default logging on Enyim should include INFO level logging on connections being dropped Created: 03/Aug/11  Updated: 17/May/13

Status: Open
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: None
Fix Version/s: 1.2.8

Type: Improvement Priority: Major
Reporter: Matt Ingenthron Assignee: John Zablocki
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Per an email discussion, at least when using the COM wrapper, if not when using .NET calls directly, there may not be logging by default about connection drops/reconnects.



[NCBC-111] Hangs after threads are aborted Created: 04/Sep/12  Updated: 17/May/13

Status: Open
Project: Couchbase .NET client library
Component/s: library
Affects Version/s: 1.1.6
Fix Version/s: 1.2.7

Type: Bug Priority: Major
Reporter: roy.jacobs Assignee: Saakshi Manocha
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Zip Archive HangRepro.zip    

 Description   
In our production system thread occasionally get aborted to prevent long-running tasks from using resources when the user is no longer interested in the results. We are seeing these kinds of errors in the log:

ERROR Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl - Could not init pool.
and
ERROR Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl - Failed to reset an acquired socket.

Also, we are seeing hangs in MessageStreamListener.cs, line 400:
while ((line = reader.ReadLine()) != null)

This will occasionally hang indefinitely waiting for data to come in to the stream when there is no more data coming in.
I have created a reproduction application that creates a bunch of threads in an "abortable" thread pool (which just allows you to abort the threads, instead of being a black box). Starting the application will print a "." for every thread started, a "!" for every thread stopped and an "x" for every thread aborted. The thread itself just does a simple set/get. It typically hangs after about 15-20 seconds, on this ReadLine statement.

You can find the repro attached to this ticket.

This happens with Couchbase server 1.8.1 and the latest client code from Github.

 Comments   
Comment by Matt Ingenthron [ 17/May/13 ]
Can you see if this is reproducible with current server/client?



[NCBC-232] Fix CBSE-426 - .Net Client fails silently if there is a wrong configuration Created: 25/Feb/13  Updated: 17/May/13

Status: Open
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: 1.2.1
Fix Version/s: 1.2.8

Type: Improvement Priority: Minor
Reporter: Saakshi Manocha Assignee: John Zablocki
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Dependency

 Description   
Fix issue CBSE-426



[NCBC-207] Could not find the pool '...' at http://host:8091/pools : password-less buckets make the other buckets unavailable Created: 17/Jan/13  Updated: 17/May/13

Status: Open
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: None
Fix Version/s: 1.3

Type: Bug Priority: Minor
Reporter: guillaume.pitel Assignee: John Zablocki
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment: Mono 2.10.8.1 (Debian 2.10.8.1-1ubuntu2.2) Ubuntu 12.04 / Couchbase server 2.0


 Description   
Hi, we stumbled on a minor bug.

After importing the beer bucket for testing purpose, we had this kind of errors : (Couchbase .Net 1.2 / mono client)

2013-01-17 11:13:28 [DEBUG] 1 Couchbase.MessageStreamListener - Starting the listener. Queue=True
2013-01-17 11:13:28 [DEBUG] 11 Couchbase.MessageStreamListener - Started working.
2013-01-17 11:13:28 [DEBUG] 11 Couchbase.MessageStreamListener - Looking for the first working node.
2013-01-17 11:13:29 [WARN] 11 Couchbase.ConfigHelper - Could not find the pool 'static' at http://10.1.44.1:8091/pools
2013-01-17 11:13:29 [WARN] 11 Couchbase.MessageStreamListener - Could not resolve url http://10.1.44.1:8091/pools; trying the next in the list
2013-01-17 11:13:29 [WARN] 11 Couchbase.ConfigHelper - Could not find the pool 'static' at http://10.1.44.2:8091/pools
2013-01-17 11:13:29 [WARN] 11 Couchbase.MessageStreamListener - Could not resolve url http://10.1.44.2:8091/pools; trying the next in the list
2013-01-17 11:13:29 [WARN] 11 Couchbase.MessageStreamListener - Could not found a working node.
2013-01-17 11:13:29 [WARN] 11 Couchbase.MessageStreamListener - All nodes are dead, sleeping for a while.
2013-01-17 11:13:29 [INFO] 11 Couchbase.CouchbasePool - Received new configuration.
2013-01-17 11:13:29 [INFO] 11 Couchbase.CouchbasePool - Config is empty, all nodes are down.
2013-01-17 11:13:29 [DEBUG] 11 Couchbase.MessageStreamListener - Processing message:

It appears that if a bucket with authentication is passwordless (like the beer sample bucket at creation), the client cannot find the other pools.


 Comments   
Comment by John Zablocki [ 18/Jan/13 ]
Hi Guillaume,

How did this affect the client's behavior? Did operations fail? Could you describe a bit more what you were seeing?

Thanks.

-- John
Comment by guillaume.pitel [ 19/Jan/13 ]
It's the connection creation that fails, so every subsequent operation fails.



[NCBC-202] add a keyStats feature Created: 12/Jan/13  Updated: 17/May/13

Status: Open
Project: Couchbase .NET client library
Component/s: library
Affects Version/s: 1.2.0
Fix Version/s: 1.3

Type: New Feature Priority: Minor
Reporter: Matt Ingenthron Assignee: John Zablocki
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
At times it's useful to get information about a key through underlying "stats key <key> <vbucket>", but using just the stats command is complex because the vbucket hashing isn't exposed. One better though is a keyStats() operation that would return a map of the return for "stats key".



[NCBC-199] Update tutorial beer sample to use geo.lng and geo.lat JSON properties Created: 09/Jan/13  Updated: 17/May/13  Resolved: 17/May/13

Status: Closed
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: None
Fix Version/s: 1.2.5

Type: Task Priority: Minor
Reporter: John Zablocki Assignee: John Zablocki
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified




[NCBC-135] Client not properly handling cluster_run server Created: 03/Oct/12  Updated: 17/May/13

Status: Open
Project: Couchbase .NET client library
Component/s: library
Affects Version/s: 1.2 Beta
Fix Version/s: 1.3

Type: Bug Priority: Minor
Reporter: Mark Nunberg Assignee: John Zablocki
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment: Using cluster_run from branch-2.0 xml


 Description   
I can't do simple things like get/set stuff..


PS C:\Users\Administrator\Documents\GitHub\cbc-net\src\CbcNet\bin\Debug> .\cbc-net.exe -c set -k foo -V bar -H 10.0.0.99
:8091; .\cbc-net.exe -c get -k foo -H 10.0.0.99:8091
URI: http://10.0.0.99:8091/pools
http://10.0.0.99:8091/pools
Created new client..
Arguments to ExecuteStore:
   0x00000003, 'foo', 'bar', 00:00:00, Zero, Zero
Operation Succeeded. Cas: 610018894666114
Duration was 3.07 Sec.
URI: http://10.0.0.99:8091/pools
http://10.0.0.99:8091/pools
Created new client..
Command OK
Value is bar
Cas is 610018894666114
Duration was 3.09 Sec.
PS C:\Users\Administrator\Documents\GitHub\cbc-net\src\CbcNet\bin\Debug> echo "hi" | C:\Users\Administrator\Documents\Gi
tHub\deps\bin\cbc.exe create -h 10.0.0.99 foo2
PS C:\Users\Administrator\Documents\GitHub\cbc-net\src\CbcNet\bin\Debug> # Now with the cluster_run cluster
PS C:\Users\Administrator\Documents\GitHub\cbc-net\src\CbcNet\bin\Debug> .\cbc-net.exe -c set -k foo -V bar -H 10.0.0.99
:9000; .\cbc-net.exe -c get -k foo -H 10.0.0.99:9000
URI: http://10.0.0.99:9000/pools
http://10.0.0.99:9000/pools
Created new client..
Arguments to ExecuteStore:
   0x00000003, 'foo', 'bar', 00:00:00, Zero, Zero
Initial command failed (Store operation failed, see InnerResult or StatusCode for details). Trying simple version..
.. Inner Message: Failed to execute operation
Command Failed
Code is 0
Message is Store operation failed, see InnerResult or StatusCode for details
Duration was 3.02 Sec.
URI: http://10.0.0.99:9000/pools
http://10.0.0.99:9000/pools
Created new client..
Command Failed
Code is
Message is Unable to locate node
Duration was 3.05 Sec.
PS C:\Users\Administrator\Documents\GitHub\cbc-net\src\CbcNet\bin\Debug>


## This works fine with libcouchbase:


PS C:\Users\Administrator\Documents\GitHub\cbc-net\src\CbcNet\bin\Debug>
PS C:\Users\Administrator\Documents\GitHub\cbc-net\src\CbcNet\bin\Debug>
PS C:\Users\Administrator\Documents\GitHub\cbc-net\src\CbcNet\bin\Debug> echo "hi" | C:\Users\Administrator\Documents\Gi
tHub\deps\bin\cbc.exe create -h 10.0.0.99:9000 foo2
Stored "foo2" CAS:911342e1e62a0200
PS C:\Users\Administrator\Documents\GitHub\cbc-net\src\CbcNet\bin\Debug> C:\Users\Administrator\Documents\GitHub\deps\bi
n\cbc.exe cat -h 10.0.0.99:9000 foo2
"foo2" Size:3 Flags:0 CAS:911342e1e62a0200
hi
PS C:\Users\Administrator\Documents\GitHub\cbc-net\src\CbcNet\bin\Debug>


 Comments   
Comment by Mark Nunberg [ 03/Oct/12 ]
Currently this forces me to run tests against a remote cluster with .net. It would be nice to have the ability to run these tests locally via 'cluster_run'
Comment by Mark Nunberg [ 03/Oct/12 ]
fyi, it seems from running tcpdump that it's connecting to the rest server and also connecting to some memcached port.. but the op still fails..



[NCBC-235] Provide more detail on "Unable to locate node" errors Created: 04/Mar/13  Updated: 17/May/13

Status: Open
Project: Couchbase .NET client library
Component/s: docs, library
Affects Version/s: 1.2.2
Fix Version/s: 1.2.8

Type: Improvement Priority: Major
Reporter: John Zablocki Assignee: John Zablocki
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Comments   
Comment by Tim Smith [ 12/Mar/13 ]
For clarity, the desired change is in the library itself, to provide info in the error message about what host lost the connection, whether there was a corrupt cluster map or just couldn't connect to any of the hosts, etc. Currently the error provides no insight into where the problem may lie. The developer can assume there may be some networking problem, but no pointer about which node is to blame, etc.



[NCBC-242] ExecuteGet-multi should return detailed status results for each key Created: 27/Mar/13  Updated: 17/May/13

Status: Open
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: 1.2.4
Fix Version/s: 1.3

Type: Task Priority: Major
Reporter: John Zablocki Assignee: John Zablocki
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified




[NCBC-170] evaluate socket pool reliability change Created: 30/Nov/12  Updated: 17/May/13

Status: Open
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: None
Fix Version/s: 1.2.8

Type: Bug Priority: Critical
Reporter: Matt Ingenthron Assignee: John Zablocki
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
A recent issue seems to be similar to a reported issue in EnyimMemcached. We should evaluate whether or not to include this in our release.

See https://github.com/enyim/EnyimMemcached/issues/94



[NCBC-236] JSON serialization tests for view params are broken Created: 04/Mar/13  Updated: 17/May/13

Status: Open
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: 1.2.1
Fix Version/s: 1.2.7

Type: Bug Priority: Major
Reporter: John Zablocki Assignee: John Zablocki
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified




[NCBC-222] When node is unavailable for a view query, don't throw an InvalidOperationException Created: 05/Feb/13  Updated: 17/May/13

Status: Open
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: 1.2.1
Fix Version/s: 1.2.7

Type: Improvement Priority: Major
Reporter: John Zablocki Assignee: John Zablocki
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified




[NCBC-219] Write the .NET/Windows Getting Started Section for the Essentials Guides Created: 04/Feb/13  Updated: 17/May/13

Status: Open
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: None
Fix Version/s: 1.3

Type: Task Priority: Major
Reporter: MC Brown Assignee: John Zablocki
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Write the .NET/Windows Getting Started section of the Essentials Guide

Needs to cover:

Basic Setup of the .NET environment
Adding the .NET Client library to a project
Writing your first (small) app using Couchbase and .NET

Submissions should be to MC, either through the couchbase/docs repo, or direct to MC in whatever format suits. Must include both the text and images.



[NCBC-215] BinaryOperation failues should include message Created: 31/Jan/13  Updated: 17/May/13

Status: Open
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: 1.2.0
Fix Version/s: 1.2.8

Type: Bug Priority: Major
Reporter: John Zablocki Assignee: John Zablocki
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
When the client is unable to process the response from the server, there should be some notification, probably via BinaryOperationResult.Message



[NCBC-196] Config updates seem to be occuring when vbucket configuration hasn't changed Created: 08/Jan/13  Updated: 17/May/13

Status: Open
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: 1.2.0
Fix Version/s: 1.2.8

Type: Bug Priority: Major
Reporter: John Zablocki Assignee: John Zablocki
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
The client appears to be updating its config when receiving config updates that shouldn't trigger a change in internal config (i.e., reodered nodes, fast forward maps).



[NCBC-198] When performing MultiGet, unloading AppDomain crashes the host Created: 08/Jan/13  Updated: 17/May/13

Status: Open
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: 1.2.6
Fix Version/s: 1.2.8

Type: Bug Priority: Major
Reporter: John Zablocki Assignee: John Zablocki
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
https://github.com/enyim/EnyimMemcached/issues/103



[NCBC-183] Docs should use Execute* methods with best practice error handling and logging in all examples Created: 14/Dec/12  Updated: 17/May/13

Status: Open
Project: Couchbase .NET client library
Component/s: docs
Affects Version/s: 1.2.0
Fix Version/s: 1.3

Type: Improvement Priority: Major
Reporter: Tim Smith Assignee: John Zablocki
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: 24h
Time Spent: Not Specified
Original Estimate: 24h
Environment: http://www.couchbase.com/docs/couchbase-sdk-net-1.2/crud.html


 Description   
While proper error handling may be application-specific (some apps may be fine treating any error as "not found", while others need to handle those as very distinct cases, for example), I think the documentation the docs provide, and especially the tutorials and examples that people are likely to copy from, should perform explicit and thorough error handling and logging. Docs should make it easy for people to do it the right way.

The current .NET docs have an OK example in the ASP.NET tutorial, where at least the return value is checked and exceptions are rethrown. So that's a good start, although there's no evidence of testing result.Success (which could be false, even if result.Exception is null). There's no mention, too, of what happens higher up when the result code is returned, and no logging of errors that folks can cut and paste.

http://www.couchbase.com/docs/couchbase-sdk-net-1.2/brewerycrud.html

One method uses this:
    return result.StatusCode.HasValue ? result.StatusCode.Value : 0;

While the others just return result.StatusCode.Value with no test. Why is that? Where is that documented?


Then this example uses the non-Execute versions which don't allow for proper error handling. That may be OK in a very basic tutorial, but there should be a very clear and explicit pointer anywhere these are used that goes to a "Error handling with the .NET client" page that details why you shouldn't use those in most production code, and that you'll have a very hard time writing correct code unless you use the Execute* methods, and that also provides succinct and complete example for cut-and-pastability of correct error handling.

Even so, I'd prefer that the basic "hello world" tutorial use Execute* methods in the first place, so people who only skim the docs only see the correct way to do things.

http://www.couchbase.com/docs/couchbase-sdk-net-1.2/crud.html


 Comments   
Comment by Matt Ingenthron [ 17/May/13 ]
This is probably not something we want to do as written. We want the simple approach to be, well, simple. Future API will hopefully make this better.



[NCBC-214] Docs don't mention InnerResult Created: 30/Jan/13  Updated: 17/May/13

Status: Open
Project: Couchbase .NET client library
Component/s: docs
Affects Version/s: 1.2.1
Fix Version/s: 1.2.7

Type: Improvement Priority: Major
Reporter: Tim Smith Assignee: John Zablocki
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment: http://www.couchbase.com/docs/couchbase-sdk-net-1.2/couchbase-sdk-net-operation-results.html


 Description   
The docs page on Working with Operation Results does not describe the InnerResult member at all. No mention of when it will be set, what it should contain, or how to display it.

My understanding is that this member may be important for understanding why something has failed. I'm not sure how to describe it or use it best, though, so I think this needs some clarification from SDK team.

 Comments   
Comment by John Zablocki [ 30/Jan/13 ]
Recent updates have made this property obsolete. I need to work on a plan for removal/obsolescence.



[NCBC-8] supply license information for documentation Created: 09/Sep/11  Updated: 17/May/13  Resolved: 17/May/13

Status: Resolved
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: None
Fix Version/s: 1.2.5

Type: Task Priority: Major
Reporter: Matt Ingenthron Assignee: John Zablocki
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
needed for all libs; just filing for tracking here

 Comments   
Comment by John Zablocki [ 05/Apr/12 ]
Moving to 1.2 to have an item for Hammock and Json.NET
Comment by Matt Ingenthron [ 17/May/13 ]
Done, in the move to NuGet. only JSON.net is a dependency as of 1.2.6.



[NCBC-15] running unit tests under CI Created: 12/Jan/12  Updated: 17/May/13

Status: Open
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: None
Fix Version/s: 1.3

Type: Task Priority: Major
Reporter: Matt Ingenthron Assignee: Saakshi Manocha
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Comments   
Comment by Matt Ingenthron [ 17/May/13 ]
Perhaps you have this one done?



[NCBC-201] add observe operation type to client Created: 12/Jan/13  Updated: 17/May/13  Resolved: 17/May/13

Status: Resolved
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: 1.2.0
Fix Version/s: 1.2.5

Type: New Feature Priority: Major
Reporter: Matt Ingenthron Assignee: John Zablocki
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
There are some times that one may like to do one's own observation on the state of a key/cas. To do so, the OBSERVE protocol operation needs a high level operation.

 Comments   
Comment by John Zablocki [ 14/Jan/13 ]
There already is a public Observe method, though it's not documented. It's the driver for the durability methods. I'll document it for 1.2.2.




[NCBC-152] Couchbase Client hangs during instantion of the Client if the request to http://xxx.xxx.xxx.xxx:8091/pools/default/bucketsStreaming/default is blocked or never returns Created: 09/Nov/12  Updated: 17/May/13

Status: Open
Project: Couchbase .NET client library
Component/s: library
Affects Version/s: 1.2 Beta
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Aaron Mell Assignee: Saakshi Manocha
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment: Windows 7
Windows Server 2008 VM
AVG 2012.0.2221
Coucbase C# Client Library 1.2


 Description   
During instantiation of the client, a MessageStreamListener is created. Inside of the listener is a call is made to the config url

Line 376 of MessageStreamListener

this.request = this.requestFactory.GetWebRequest(configUrl, configUrl.GetHashCode().ToString());
this.response = this.request.GetResponse();

If this call never completes, for example because AVG silently blocks the request and prevents the data from being returned, then the client will wait indefinitely instead of timing out.

 Comments   
Comment by Aaron Mell [ 09/Nov/12 ]
http://www.couchbase.com/forums/thread/net-client-hangs-client-create#comment-1007661
Comment by Matt Ingenthron [ 17/May/13 ]
Not a priority, but let's try to come up with a way to test if this does in fact hang forever. If so, we should fix it.



[NCBC-90] Updated screencast for /develop pages Created: 12/Jul/12  Updated: 17/May/13  Resolved: 17/May/13

Status: Resolved
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: None
Fix Version/s: 1.2.5

Type: Improvement Priority: Major
Reporter: Matt Ingenthron Assignee: John Zablocki
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Create an updated screencast to ship with the new 2.0 developer SDKs

 Comments   
Comment by Matt Ingenthron [ 17/May/13 ]
Not going to do this at the moment.



[NCBC-162] Handle "no active vbucket" view failure Created: 23/Nov/12  Updated: 17/May/13

Status: Open
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: None
Fix Version/s: 1.2.7

Type: Bug Priority: Major
Reporter: Mark Nunberg Assignee: John Zablocki
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment: Enyim master (rev: 6590b2643c62059e6f2418ccc5bea8c58326dfbc <- master at time of writing)
Couchbase master (rev: e3de5459bfc0b5efd1eb906a99e903990a3fc2ce <- master at time of writing)
Server 1941


 Description   
Presumably the client should try the view on another node..

In general we should have a unified exception class for view errors the client can understand.. InvalidOperationException is not very helpful or descriptive (nor is it very catchable.. though it was probably initially placed as a stub)..

[INFO 76.59 cbsdk.scenario failover.py:149] Ramp for 5 seconds..
[INFO 81.60 cbsdk.scenario failover.py:157] No service specified..
[ACTION 81.60 cbsdk.scenario failover.py:160] Failing over nodes [ip:10.3.121.207 ssh_username:root]
[ACTION 81.60 cbsdk.cluster.cluster cluster.py:695] Failing over node ip:10.3.121.207 ssh_username:root
[SDKD(INFO) 81.78 cbsdk.sdkd.remote remote.py:263] [Sdkd.Main|Fatal] Requested suppression of exception dialog box..
[SDKD(INFO) 81.78 cbsdk.sdkd.remote remote.py:263] [Sdkd.Main|Fatal] Unhandled Exception System.InvalidOperationException Server returned Found: Moved Temporarily, {"error":"no_active_vbuckets","reason":"Cannot execute view query since the node has no active vbuckets"} at Couchbase.HammockHttpClient.HammockResponseWrapper.ExecuteWith(RestClient client) in \\vboxsrv\src\couchbase-net-client\src\Couchbase\HammockHttpClient.cs:line 143
[SDKD(INFO) 81.78 cbsdk.sdkd.remote remote.py:263] at Couchbase.HammockHttpClient.HammockRequestWrapper.Couchbase.IHttpRequest.GetResponse() in \\vboxsrv\src\couchbase-net-client\src\Couchbase\HammockHttpClient.cs:line 112
[SDKD(INFO) 81.78 cbsdk.sdkd.remote remote.py:263] at Couchbase.CouchbaseViewHandler.GetResponse(IDictionary`2 viewParams) in \\vboxsrv\src\couchbase-net-client\src\Couchbase\CouchbaseViewHandler.cs:line 144
[SDKD(INFO) 81.78 cbsdk.sdkd.remote remote.py:263] at Couchbase.CouchbaseViewHandler.<TransformResults>d__0`1.MoveNext() in \\vboxsrv\src\couchbase-net-client\src\Couchbase\CouchbaseViewHandler.cs:line 38
[SDKD(INFO) 81.78 cbsdk.sdkd.remote remote.py:263] at Sdkd.Views.ViewCommand.Run() in \\vboxsrv\src\sdkd-net\src\Sdkd\Views\ViewCommand.cs:line 219
[SDKD(INFO) 81.78 cbsdk.sdkd.remote remote.py:263] at SdkdConsole.Daemon.Handle.dispatchCommand(Request req) in \\vboxsrv\src\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 177
[SDKD(INFO) 81.78 cbsdk.sdkd.remote remote.py:263] at SdkdConsole.Daemon.Handle.Run() in \\vboxsrv\src\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 110
[SDKD(INFO) 81.78 cbsdk.sdkd.remote remote.py:263] at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
[SDKD(INFO) 81.78 cbsdk.sdkd.remote remote.py:263] at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
[SDKD(INFO) 81.78 cbsdk.sdkd.remote remote.py:263] at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
[SDKD(INFO) 81.78 cbsdk.sdkd.remote remote.py:263] at System.Threading.ThreadHelper.ThreadStart()
[SDKD(INFO) 81.78 cbsdk.sdkd.remote remote.py:263] [Sdkd.Main|Fatal] Requested suppression of exception dialog box..
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] [Sdkd.Main|Fatal] Requested suppression of exception dialog box..
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] [Sdkd.Main|Fatal] Requested suppression of exception dialog box..
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] [Sdkd.Main|Fatal] Unhandled Exception System.InvalidOperationException Server returned Found: Moved Temporarily, {"error":"no_active_vbuckets","reason":"Cannot execute view query since the node has no active vbuckets"} at Couchbase.HammockHttpClient.HammockResponseWrapper.ExecuteWith(RestClient client) in \\vboxsrv\src\couchbase-net-client\src\Couchbase\HammockHttpClient.cs:line 143
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at Couchbase.HammockHttpClient.HammockRequestWrapper.Couchbase.IHttpRequest.GetResponse() in \\vboxsrv\src\couchbase-net-client\src\Couchbase\HammockHttpClient.cs:line 112
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at Couchbase.CouchbaseViewHandler.GetResponse(IDictionary`2 viewParams) in \\vboxsrv\src\couchbase-net-client\src\Couchbase\CouchbaseViewHandler.cs:line 144
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at Couchbase.CouchbaseViewHandler.<TransformResults>d__0`1.MoveNext() in \\vboxsrv\src\couchbase-net-client\src\Couchbase\CouchbaseViewHandler.cs:line 38
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at Sdkd.Views.ViewCommand.Run() in \\vboxsrv\src\sdkd-net\src\Sdkd\Views\ViewCommand.cs:line 219
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at SdkdConsole.Daemon.Handle.dispatchCommand(Request req) in \\vboxsrv\src\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 177
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at SdkdConsole.Daemon.Handle.Run() in \\vboxsrv\src\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 110
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at System.Threading.ThreadHelper.ThreadStart()
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] [Sdkd.Main|Fatal] Will now exit..
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] [Sdkd.Main|Fatal] Unhandled Exception System.InvalidOperationException Server returned Found: Moved Temporarily, {"error":"no_active_vbuckets","reason":"Cannot execute view query since the node has no active vbuckets"} at Couchbase.HammockHttpClient.HammockResponseWrapper.ExecuteWith(RestClient client)
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at Couchbase.HammockHttpClient.HammockRequestWrapper.Couchbase.IHttpRequest.GetResponse()
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at Couchbase.CouchbaseViewHandler.GetResponse(IDictionary`2 viewParams)
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at Couchbase.CouchbaseViewHandler.<TransformResults>d__0`1.MoveNext()
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at Sdkd.Views.ViewCommand.Run()
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at SdkdConsole.Daemon.Handle.dispatchCommand(Request req)
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at SdkdConsole.Daemon.Handle.Run()
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at System.Threading.ThreadHelper.ThreadStart()
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] [Sdkd.Main|Fatal] Will now exit..
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] [Sdkd.Main|Fatal] Unhandled Exception System.InvalidOperationException Server returned Found: Moved Temporarily, {"error":"no_active_vbuckets","reason":"Cannot execute view query since the node has no active vbuckets"} at Couchbase.HammockHttpClient.HammockResponseWrapper.ExecuteWith(RestClient client)
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at Couchbase.HammockHttpClient.HammockRequestWrapper.Couchbase.IHttpRequest.GetResponse()
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at Couchbase.CouchbaseViewHandler.GetResponse(IDictionary`2 viewParams)
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at Couchbase.CouchbaseViewHandler.<TransformResults>d__0`1.MoveNext()
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at Sdkd.Views.ViewCommand.Run()
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at SdkdConsole.Daemon.Handle.dispatchCommand(Request req)
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at SdkdConsole.Daemon.Handle.Run()
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at System.Threading.ThreadHelper.ThreadStart()
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] [Sdkd.Main|Fatal] Will now exit..
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] [Sdkd.Main|Fatal] Will now exit..




[NCBC-264] document the release process Created: 17/May/13  Updated: 17/May/13

Status: Open
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Critical
Reporter: Matt Ingenthron Assignee: Saakshi Manocha
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Somewhere in the source repository, please document the release process.



[NCBC-262] .Net client fails in two sdkd scenarios Created: 14/May/13  Updated: 15/May/13

Status: Open
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: 1.2.5
Fix Version/s: 1.2.7

Type: Bug Priority: Major
Reporter: Saakshi Manocha Assignee: Saakshi Manocha
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
.Net client is producing errors (socket reset, operation time out, etc) for two scenarios:

HYBRID_rb-1-swap (swap rebalance (one added, one removed))
HYBRID_svc-restart-75pct (restart couchbase-server on 3/4 nodes)

 Comments   
Comment by Saakshi Manocha [ 14/May/13 ]
HYBRID_rb-1-swap

http://sdk-testresults.couchbase.com.s3.amazonaws.com/sdkd/HWIN-335SPEPOCGT-IHYBRID_rb-1-swap-Sdotnet-1.2-release-T2013-05-14-10.16.06-LV_CB_BASIC.txt
http://sdk-testresults.couchbase.com.s3.amazonaws.com/sdkd/HWIN-335SPEPOCGT-IHYBRID_rb-1-swap-Sdotnet-1.2-release-T2013-05-14-10.16.06-LV_MC_BASIC.txt
http://sdk-testresults.couchbase.com.s3.amazonaws.com/sdkd/HWIN-335SPEPOCGT-IHYBRID_rb-1-swap-Sdotnet-1.2-release-T2013-05-14-10.16.06-LV_HTTP_BASIC.txt

HYBRID_svc-restart-75pct

http://sdk-testresults.couchbase.com.s3.amazonaws.com/sdkd/HWIN-335SPEPOCGT-IHYBRID_svc-restart-75pct-Sdotnet-1.2-release-T2013-04-02-00.44.50-LV_CB_BASIC.txt
http://sdk-testresults.couchbase.com.s3.amazonaws.com/sdkd/HWIN-335SPEPOCGT-IHYBRID_svc-restart-75pct-Sdotnet-1.2-release-T2013-04-02-00.44.50-LV_MC_BASIC.txt
http://sdk-testresults.couchbase.com.s3.amazonaws.com/sdkd/HWIN-335SPEPOCGT-IHYBRID_svc-restart-75pct-Sdotnet-1.2-release-T2013-04-02-00.44.50-LV_HTTP_BASIC.txt
Comment by John Zablocki [ 15/May/13 ]
These runs aren't using the latest client. I don't think that will change the results, but RestSharp is being used according to the logs.



[NCBC-263] Support durability requirements on JSON store extensions Created: 15/May/13  Updated: 15/May/13  Resolved: 15/May/13

Status: Closed
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Minor
Reporter: John Zablocki Assignee: John Zablocki
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Comments   
Comment by John Zablocki [ 15/May/13 ]
Already supported.



[NCBC-257] During rebalance client tries to connect the primary node only Created: 02/May/13  Updated: 15/May/13

Status: Open
Project: Couchbase .NET client library
Component/s: library
Affects Version/s: 1.2.6
Fix Version/s: 1.2.7

Type: Bug Priority: Blocker
Reporter: Saakshi Manocha Assignee: Saakshi Manocha
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
I'm adding this bug to identify performance issue that is raised in CBSE-521 and CBSE-528

It is observed during the sdkd scenario tests, that while rebalance is happening, the client tries to connect only the primary node and does not connect to the other secondary nodes in the cluster. During rebalance the topology changes and hence many errors like socket reset, no response received, operation time out, etc.
These errors go away when the rebalance is over and with rebound phase, no errors are observed.
Please see some sample reports:
http://sdk-testresults.couchbase.com.s3.amazonaws.com/sdkd/HWIN-335SPEPOCGT-IHYBRID_fo-ept-rb-Sdotnet-1.2-release-T2013-04-02-00.11.35-LV_MC_BASIC.txt
http://sdk-testresults.couchbase.com.s3.amazonaws.com/sdkd/HWIN-335SPEPOCGT-IHYBRID_rb-2-in-Sdotnet-1.2-release-T2013-04-02-00.21.03-LV_HTTP_BASIC.txt
http://sdk-testresults.couchbase.com.s3.amazonaws.com/sdkd/HWIN-335SPEPOCGT-IHYBRID_fo-ept-eject-Sdotnet-1.2-release-T2013-04-02-00.17.30-LV_HTTP_BASIC.txt

Mark - need your input here too, do you think these errors during rebalance can impact performance or stability at customer site.


 Comments   
Comment by Saakshi Manocha [ 02/May/13 ]
Also, as per the documentation and our understanding, we can expect errors during CHANGE phase and ideally they should go away in REBOUND phase.

CHANGE: Here we see that errors start happening. This is because a cluster topology change started around this time. We can expect errors until the topology change is completed. In this case, the topology change was adding a single node to the cluster.
REBOUND: Here we see the errors are stopping. This is because the topology change has been completed. Since we added an extra node to the
cluster, the rate of operations has actually gone up from before. This is because there are more nodes to handle requests now.
Comment by Matt Ingenthron [ 10/May/13 ]
This appears to be a critical issue. Marking as blocker for 1.2.7 until we have a better understanding.
Comment by John Zablocki [ 15/May/13 ]
When you say "connect to the primary node only" are you referring to the streaming connection or all ops are going on the primary node?



[NCBC-253] flush_all method still available through API, does nothing against 2.0 cluster Created: 22/Apr/13  Updated: 14/May/13

Status: In Progress
Project: Couchbase .NET client library
Component/s: docs, library
Affects Version/s: 1.2.4
Fix Version/s: 1.2.7

Type: Bug Priority: Critical
Reporter: Perry Krug Assignee: Matt Ingenthron
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Is flush_all deprecated for 2.x clusters? No error is returned when run against a 2.0 bucket

Need SDK documentation on the deprecation and how to use flush properly (it's currently only in the release notes)

 Comments   
Comment by John Zablocki [ 13/May/13 ]
FlushAll is a method on the Enyim MemchacedClient, so it's inherited.

I've posted a change to Gerrit that checks to see if any of the working nodes is of type CouchbaseNode (2.0+). If so, an NotImplementedException is raised. Otherwise, if it's a Memcached bucket or 1.8.x, the MemcachedClient.FlushAll is performed.
Comment by John Zablocki [ 14/May/13 ]
Would this approach address your concern?
Comment by Perry Krug [ 14/May/13 ]
Sounds very reasonable to me, thank you.
Comment by Matt Ingenthron [ 14/May/13 ]
Should it perform a RESTful flush if the server is a 2.0 server && couchbase bucket? This is what we did in the Java client if I recall correctly. The logic being this way code moves over and just works.
Comment by John Zablocki [ 14/May/13 ]
Is that the right API? To me it feels like it isn't, since flush is no longer a "client" API action. It's easy enough to implement, but seems best to steer people to the right API, imo...



[NCBC-261] Use an enumeration instead of integers for return codes Created: 14/May/13  Updated: 14/May/13

Status: Open
Project: Couchbase .NET client library
Component/s: docs, library
Affects Version/s: 1.2.6
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: Perry Krug Assignee: John Zablocki
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Customer suggested an improvement of using an enumeration for the operation results instead of integer values.



[NCBC-233] Enhance packaging to not conflict with other tools that include Enyim.Caching via Nuget Created: 26/Feb/13  Updated: 08/May/13

Status: Open
Project: Couchbase .NET client library
Component/s: library
Affects Version/s: 1.2.1
Fix Version/s: 1.3

Type: Improvement Priority: Minor
Reporter: Perry Krug Assignee: John Zablocki
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate

 Description   
The CouchbaseClient nuget package includes Enyim.Caching which causes compatibility issues with 3rd party applications also relying on the Enyim.Caching assembly.

The third party tool we were looking at using was ServiceStack's Caching interface, specifically the Memcached client implementation. This tool was where were were getting the conflict as they include the Enyim.Caching assembly as a nuget dependency.

See also http://www.couchbase.com/issues/browse/CBSE-412

 Comments   
Comment by Sergey Avseyev [ 25/Apr/13 ]
Not sure if it is related, but IMHO it is

http://www.couchbase.com/forums/thread/please-use-nuget-correctly

> Your NuGet packages have several problems.
> 1. You take binary dependencies on other things which are available via NuGet, but you're shipping those binaries yourself. You should be taking a package dependency instead, so that things can be referenced and versioned correctly.
> 2. Your "Couchbase with Logging" package should be an additive package that takes a package dependency on your "Couchbase" package, rather than shipping an entirely separate copy of the assembly. This causes linking conflicts.

Probably it worth to increase priority of this issue
Comment by Sergey Avseyev [ 25/Apr/13 ]
http://www.couchbase.com/forums/thread/please-stop-using-private-build-restsharp-couchbase-net-client

> You are currently shipping an unsigned but otherwise identically named DLL called RestSharp, which conflicts with anybody who actually uses the real shipping version of RestSharp.
> Either use the signed production version of RestSharp, or else rename the assembly so it does not collide with the real version of RestSharp.
Comment by John Zablocki [ 25/Apr/13 ]
This is actually being addressed in NCBC-247.



[NCBC-226] Docs: Reference installation Created: 11/Feb/13  Updated: 08/May/13

Status: Open
Project: Couchbase .NET client library
Component/s: docs
Affects Version/s: 1.2.1
Fix Version/s: 1.2.7

Type: Improvement Priority: Major
Reporter: Perry Krug Assignee: John Zablocki
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Customers have lots of choices at their fingertips, and many of those choices will result in a non-functioning installation, or at least a lot of time spent figuring out what the right pieces are.

Can we please provide as much details as possible about a reference installation that we can be sure will work for a customer who is just getting started? This is outside of our support for any one operatin system, but more about telling the customer "if you install with these versions and packages, this code will work"

-OS
-"language" version (.NET 4, etc)
-other packages/modules required and/or tested with



[NCBC-225] Docs: Recommendations for which logging level to be set during testing/staging/production and examples of messages at each level Created: 07/Feb/13  Updated: 08/May/13

Status: Open
Project: Couchbase .NET client library
Component/s: docs
Affects Version/s: 1.2.1
Fix Version/s: 1.2.8

Type: Bug Priority: Major
Reporter: Perry Krug Assignee: John Zablocki
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Customer read http://www.couchbase.com/docs/couchbase-sdk-net-1.1/couchbase-sdk-net-logging.html, but still not clear on what level we recommend to get meaningful output from, and examples of what log messages that would see under certain situations.



[NCBC-223] Check for SetTcpKeepAlive at runtime for Mono support Created: 05/Feb/13  Updated: 08/May/13

Status: Open
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: None
Fix Version/s: 1.2.7

Type: Improvement Priority: Minor
Reporter: John Zablocki Assignee: John Zablocki
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Mono doesn't support this method on the ServicePointManager.



[NCBC-221] Docs: working with multiple buckets in the .NET client Created: 05/Feb/13  Updated: 08/May/13

Status: Open
Project: Couchbase .NET client library
Component/s: docs
Affects Version/s: 1.2.0
Fix Version/s: 1.2.7

Type: Improvement Priority: Major
Reporter: Perry Krug Assignee: John Zablocki
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Apologies if it's already in there, it wasn't particularly obvious to find.

Can we have a section of documentation on working with multiple buckets from within the .NET client when configured in the app.config?



[NCBC-164] "View.Exists" Created: 26/Nov/12  Updated: 08/May/13  Resolved: 08/May/13

Status: Closed
Project: Couchbase .NET client library
Component/s: library
Affects Version/s: None
Fix Version/s: 1.2.3

Type: New Feature Priority: Major
Reporter: Kyle Sama Assignee: John Zablocki
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
When performing a query in the vein of:
_couchClient.GetView<object>("DocumentName", "ViewName");
It would be helpful to have a command like View.Exists before fetching the View. At the very least, something similar to the TryGet command, but for getting a view.


 Comments   
Comment by John Zablocki [ 26/Dec/12 ]
under the Couchbase.Management namespace, there is a CouchbaseCluster class with a GetDesignDocument. You'd have to interrogate the JSON to check for a view, but it is possible. I'll look into updating the API to have a view exists method.
Comment by John Zablocki [ 08/May/13 ]
Released.
Comment by John Zablocki [ 08/May/13 ]
Wrong close reason.



[NCBC-145] Couchbase .NET Client needs to support get with lock Created: 22/Oct/12  Updated: 08/May/13  Resolved: 08/May/13

Status: Closed
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: None
Fix Version/s: 1.2.4

Type: Bug Priority: Major
Reporter: John Zablocki Assignee: John Zablocki
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified




[NCBC-104] Provide Get and Lock Created: 24/Aug/12  Updated: 08/May/13  Resolved: 08/May/13

Status: Closed
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: None
Fix Version/s: 1.2.4

Type: Improvement Priority: Major
Reporter: Karen Zeller Assignee: John Zablocki
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Provide Get and Lock implementation.



[NCBC-84] Replica read command Created: 12/Jul/12  Updated: 08/May/13

Status: Open
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: None
Fix Version/s: 1.2.7

Type: Improvement Priority: Major
Reporter: Matt Ingenthron Assignee: John Zablocki
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Implement a simple replica read command


 Comments   
Comment by Matt Ingenthron [ 29/Aug/12 ]
See http://www.couchbase.com/wiki/display/couchbase/Replica+Read for details on implementation.



[NCBC-260] Improve discussion around using store versus executestore Created: 08/May/13  Updated: 08/May/13

Status: Open
Project: Couchbase .NET client library
Component/s: docs
Affects Version/s: 1.2.4
Fix Version/s: 1.2.7

Type: Bug Priority: Major
Reporter: Perry Krug Assignee: John Zablocki
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
From a user:

Another thing I have seen is using set and exeuteset method usage. When in samples we are using set, it is not very clear that it might fail due to memory limitation and instead of using set we should use executeset and lookout for result and if it is fail due to memory issue than we should try again in few millisecond so couchbase do memory clean-up in mean time for new data.
 



[NCBC-259] Enhance installation docs Created: 08/May/13  Updated: 08/May/13

Status: Open
Project: Couchbase .NET client library
Component/s: docs
Affects Version/s: 1.2.4
Fix Version/s: 1.2.7

Type: Improvement Priority: Major
Reporter: Perry Krug Assignee: John Zablocki
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Can we update the installation instructions in the manual with this greater detail that you've provided here? Right now, this page is awfully sparse: http://www.couchbase.com/docs/couchbase-sdk-net-1.2/downloading.html

Now on NuGet:
 
CouchbaseNetClient – the core client, version 1.2.6. RestSharp and Hammock have been removed as dependencies. Logging assemblies are no longer included. NuGet will figure out whether to install 3.5 or 4.0.
 
CouchbaseHttpClients – legacy support for RestSharp and Hammock. Unsigned, because RestSharp is not signed.
 
CouchbaseLog4NetAdapter and CouchbaseNLogAdapter – new NuGet packages that pull in log4net and NLog as NuGet package dependencies instead of local assemblies.
 
The S3 zip file contains directories for net40 and net35. Logging assemblies and dependencies are included.



[NCBC-258] Improvement needed around documentation of using singleton client Created: 07/May/13  Updated: 08/May/13

Status: Open
Project: Couchbase .NET client library
Component/s: docs
Affects Version/s: 1.2.4
Fix Version/s: 1.2.7

Type: Improvement Priority: Major
Reporter: Perry Krug Assignee: John Zablocki
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
This has been coming up more and more lately. Apparently customers are not seeing or understanding the need for using a singleton client, even in their very basic testing.

Additionally, all of the tutorial and API examples in the documentation show the creation of a client for every operation and so tend to reinforce the bad habits.

Can we make an effort around identifying and improving the visibility of this very painful issue?

 Comments   
Comment by John Zablocki [ 07/May/13 ]
See "Instantiating the Client" - http://www.couchbase.com/develop/net/current

See http://www.couchbase.com/docs/couchbase-sdk-net-1.2/stage3.html in the Tutorial.

I think that's pretty clear, no?
Comment by Perry Krug [ 07/May/13 ]
Yes, I've seen both of those...but users are still missing it with wild frequency which is causing support cases to be logged and disruption to the sales process (not to mention the unknown impact to users who don't tell us they're having problems) so I'm asking for creative ways to make it a bigger deal. Even making the text on http://www.couchbase.com/develop/net/current into an explicit "note" would help call attention to it.

What about a ".NET best practices" page? Or "troubleshooting common performance issues with .NET"?
Comment by Perry Krug [ 08/May/13 ]
John, the customer pointed me to this page which does seem to show a client being created more often that we would normally recommend: http://www.couchbase.com/docs/couchbase-sdk-net-1.2/jsonextensions.html. I presume there are other places though I haven't looked through.
Comment by John Zablocki [ 08/May/13 ]
This example is meant to be a standalone, run once console app. So it doesn't actually create the client more than we would recommend. This example is a highly contrived "Hello, World" type of app. So I don't think it would make sense to include another singleton layer, when the client is only created once during the life of the app's execution. I could see how if that's the only code one read, it would not fully detail the proper usage. The right answer might be to implement a layer of abstraction over the client creation, via a factory or something similar...
Comment by Perry Krug [ 08/May/13 ]
That's fair enough John. Maybe it's enough to make a bold note on that page to say "you should create a singleton"



[NCBC-256] Throw exception when get with lock timeout set to greater than 30 seconds. Created: 01/May/13  Updated: 08/May/13  Resolved: 08/May/13

Status: Closed
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: 1.2.4
Fix Version/s: 1.2.5

Type: Task Priority: Major
Reporter: John Zablocki Assignee: John Zablocki
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Comments   
Comment by John Zablocki [ 08/May/13 ]
Released.



[NCBC-255] Implement Unlock without CAS Created: 30/Apr/13  Updated: 08/May/13  Resolved: 08/May/13

Status: Closed
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: 1.2.4
Fix Version/s: 1.2.5

Type: New Feature Priority: Major
Reporter: John Zablocki Assignee: John Zablocki
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Comments   
Comment by John Zablocki [ 08/May/13 ]
Released.



[NCBC-254] JSON extensions should default to ignore Id property on add/replace/set. Created: 25/Apr/13  Updated: 08/May/13  Resolved: 08/May/13

Status: Closed
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: None
Fix Version/s: 1.2.5

Type: Improvement Priority: Major
Reporter: John Zablocki Assignee: John Zablocki
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
To be consistent with the view approach, the ID should not be serialized into the JSON. A new contract resolver will keep the ID from making it into the JSON. ExecuteGetJson and GetJson will insert the ID into the JSON for deserialization.

 Comments   
Comment by John Zablocki [ 08/May/13 ]
Released.



[NCBC-252] Docs/Library: Unlock after getl Created: 17/Apr/13  Updated: 08/May/13

Status: Open
Project: Couchbase .NET client library
Component/s: docs, library
Affects Version/s: 1.2.4
Fix Version/s: 1.2.7

Type: Bug Priority: Major
Reporter: Perry Krug Assignee: John Zablocki
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Does the .NET client support an unlock? If not, will we have it? If it does, can we document it?

 Comments   
Comment by John Zablocki [ 08/May/13 ]
Seems to be a problem with the docs - http://www.couchbase.com/docs/couchbase-sdk-net-1.2/api-reference-retrieve.html. I'll investigate.



[NCBC-251] Certain method summaries are not linked properly in docs Created: 17/Apr/13  Updated: 08/May/13

Status: Open
Project: Couchbase .NET client library
Component/s: docs
Affects Version/s: 1.2.4
Fix Version/s: 1.2.7

Type: Bug Priority: Major
Reporter: Perry Krug Assignee: John Zablocki
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
I haven't checked all of them, but many links off of this page do not go anywhere: http://www.couchbase.com/docs/couchbase-sdk-net-1.2/api-reference-summary.html

For example, all the getwithlock links do not have documentation behind them.



[NCBC-174] Fix invalid tests in NUnit project. Created: 07/Dec/12  Updated: 08/May/13

Status: Open
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: 1.2 Beta-2, 1.2 Beta-3, 1.2.0
Fix Version/s: 1.2.7

Type: Bug Priority: Major
Reporter: John Zablocki Assignee: John Zablocki
Resolution: Unresolved Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
Dependency
Sub-Tasks:
Key
 Summary
 Type
 Status
 Assignee
NCBC-250 Fix the test : CouchbaseAuthenticated... Technical task Open John Zablocki  

 Comments   
Comment by Saakshi Manocha [ 29/Jan/13 ]
I ran the .net unit tests against the latest code of couchbase-net-client and cluster version 2.0.0-1976
My cluster config comprise of the following nodes:
10.3.121.134
10.3.121.135
10.3.121.136
10.3.3.206

Some of the tests are failing, mostly are related to views. Please find the observations and their possible causes:

1. CouchbaseAuthenticatedViewTests\When_Bucket_Is_Authenticated_View_Returns_Results :

First the test was failing because there was no document getting created in "authenticated" bucket. Supposedly the code was creating the default client object in method CouchbaseClientFactory.CreateCouchbaseClient(), where the bucket name is default. So I changed it the initialization statement to :
_client = new CouchbaseClient("authenticated","secret");
Again running the test, now the documents are getting created for "authenticated" bucket but no views. Infact the test report is:
Couchbase.Tests.CouchbaseAuthenticatedViewTests.When_Bucket_Is_Authenticated_View_Returns_Results:
System.Net.WebException : The remote server returned an error: (404) Not Found.

2. DefaultConfigurationSettingsTests\When_Http_Timeout_Is_Not_Set_And_Using_App_Config_Default_Is_20_Seconds
and
DefaultConfigurationSettingsTests\When_Http_Timeout_Is_Not_Set_And_Using_Code_Config_Default_Is_20_Seconds:

Test fails with the error:
  Expected: 00:00:20
  But was: 00:01:00
Error reason:
In method Couchbase\Configuration\ServersElement.cs -> HttpRequestTimeout(), the following attribute is set:
[ConfigurationProperty("httpRequestTimeout", IsRequired = false, DefaultValue = "00:01:00"), PositiveTimeSpanValidator]
DefaultValue set is 00:01:00, in test we compare the result with 00:00:20, hence the failure.
The DefaultValue in attribute needs to be changed.

3. CouchbaseClusterBucketAdminTests\When_Getting_Cluster_Item_Count_Count_Matches_Interesting_Stats and When_Getting_Bucket_Item_Count_Count_Matches_Basic_Stats:
Error: System.Net.WebException : The remote server returned an error: (404) Not Found.
ErrorSource: This test would run find if we provide the username and password for the cluster. The Http response object returns an error because it is not able to connect to the clusterm possibly error in ConfigurationManager.GetSection(configSectionName) which does not return "couchbase" config section

4. CouchbaseClusterBucketAdminTests\When_Creating_New_Bucket_With_Ram_Quota_Less_Than_100_Argument_Exception_Is_Thrown:
The exception message text was incorrect
Expected message containing: Quota.RAM
 but was: RamQuotaMB must be at least 100
Solution is to change the expected message in test attribute

5. CouchbaseClientObserveTests\When_Storing_A_New_Key_With_Master_Persistence_That_Key_Is_In_View_When_Stale_Is_False:

6. CouchbaseClientObserveTests\When_Storing_A_New_Key_Observe_Will_Fail_When_Cluster_Has_Too_Few_Nodes_For_Replication:
This would run fine if we run on cluster with only one server node.
Comment by Saakshi Manocha [ 29/Jan/13 ]
Also, many a times 'Operation time out' errors occur while running the test. I'm running test over VPN, is there any performance issue?
This happens generally with GenericView and SpatialView tests.
Although these tests run fine if debugged separately
Comment by Saakshi Manocha [ 05/Feb/13 ]
Following test failures have been fixed: (http://review.couchbase.org/#/c/24394/)
Refer SDKQE-182 to track status.

1. DefaultConfigurationSettingsTests\When_Http_Timeout_Is_Not_Set_And_Using_App_Config_Default_Is_20_Seconds
  and
2. DefaultConfigurationSettingsTests\When_Http_Timeout_Is_Not_Set_And_Using_Code_Config_Default_Is_20_Seconds:
Test fails with the error:
  Expected: 00:00:20
  But was: 00:01:00
Fix provided: Recommended http time out is 1 minute so change the test and verify that the test is now passing after this change.
 Change request uploaded in Gerrit and pending for code review.

3. CouchbaseClusterBucketAdminTests\When_Creating_New_Bucket_With_Ram_Quota_Less_Than_100_Argument_Exception_Is_Thrown:
  The exception message text was incorrect
Expected message containing: Quota.RAM
 but was: RamQuotaMB must be at least 100
Fix provided : change the expected message in test attribute and verify that the test is now passing after this change.
 Change request uploaded in Gerrit and pending for code review.
  
4. DocHelperTests:
Failure: Expected: String containing ""_id":"8675309""
But was: "{"id":"8675309", "message" : "Test" }"\
Fix provided is: remove the unnecessary underscore from id and test will pass. Change request uploaded in Gerrit and pending for code review.
Comment by Saakshi Manocha [ 04/Mar/13 ]
Few more issues corrected:
(a) http://review.couchbase.org/#/c/24977/
NCBC-234: Return CAS value with ExecuteGetJson

(b) http://review.couchbase.org/#/c/24978/
NCBC-236: Fix view param JSON serialization tests
Comment by Saakshi Manocha [ 04/Mar/13 ]
More tests added :
http://review.couchbase.org/#/c/24980/

1. CouchbaseAuthenticatedViewTests ->
(a) Added new test :
When_Bucket_Is_Authenticated_And_Bad_Credentials_Are_Provided_Exception_Is_Thrown

2. CouchbaseClientGetTests ->
(a) Added new tests:
When_Getting_Multiple_Non_Existent_Keys_Result_Is_Not_Successful
and When_Getting_A_Zero_Length_Key_No_Exception_Is_Thrown_And_Success_Is_False
(b) Renamed
When_Getting_Multiple_Keys_Result_Is_Successful -> When_Getting_Multiple_Existent_Keys_Result_Is_Successful

3. CouchbaseClientObserveTests ->
(a) Added new tests:
When_Storing_A_New_Key_Observe_Will_Succeed_With_Zero_Persistence_And_Zero_Replication
and
When_Storing_A_New_Key_Observe_Will_Pass_With_Replication_More_Than_Available_Nodes
and
When_Storing_A_New_Key_Observe_Will_Fail_With_Persistence_More_Than_Available_Nodes

4. CouchbaseClientCasTests ->
(a) Added new tests:
When_Replacing_Item_With_Valid_Cas_Result_Is_Successful



[NCBC-246] .Net 3.5 support for couchbase-net-client Created: 03/Apr/13  Updated: 08/May/13  Resolved: 05/Apr/13

Status: Closed
Project: Couchbase .NET client library
Component/s: library
Affects Version/s: 1.2.4
Fix Version/s: 1.2.5

Type: Task Priority: Major
Reporter: Saakshi Manocha Assignee: John Zablocki
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Zip Archive Couchbase.zip    
Issue Links:
Dependency

 Description   
Couchbase .net client should support .net 3.5 framework, many customers have raised this request.
The related ticket with all the details is CBSE-425

 Comments   
Comment by John Zablocki [ 03/Apr/13 ]
Untested 3.5 build.
Comment by John Zablocki [ 03/Apr/13 ]
3.5 compatible code posted to Gerrit for review. The project is left as a 4.0 build with 4.0 Nuget references. But all code will compile under a 3.5.
Comment by Perry Krug [ 03/Apr/13 ]
Thanks so much John. Can you provide a bit more insight into what you mean about the project being 4.0 but compiling under 3.5? Does that mean there are certain features that will only work when using 4.0? I presume the users still need to load the project specific to their version rather than a single one applying to all? We'll probably want a bit of documentation on how to deal with the open-source aspect as well as what 3.5 users can/should expect.

Thanks again, I'll pass this first build over to the customer to see if they have any feedback.
Comment by John Zablocki [ 03/Apr/13 ]
The source code is fully 3.5 compatible, but the Visual Studio project is setup to compile to 4.0. To compile the project under 3.5, the target framework needs to be changed and NuGet references have to be downgraded to 3.5. Other than that, there are no differences in the code or features. We'll figure out how to publish two versions using our build system. NuGet will automatically add the correct reference. The next *.zip release will include two directories, one for 3.5 and one for 4.0.

The build I attached to this ticket was compiled against 3.5.
Comment by John Zablocki [ 04/Apr/13 ]
Update: I've submitted a new solution/project structure to Gerrit that includes a new Couchbase.Net35 project. The project is effectively just a set of linked files from the actual Couchbase project, which remains 4.0. The new project also has proper NuGet references.
Comment by Saakshi Manocha [ 05/Apr/13 ]
The code changes submitted in Gerrit for framework 3.5 support to .net client have been reviewed and merged in Git repository.
Initial build also passed to customer, would wait for any feedback that comes.
Hence, Closing this JIRA task.
Comment by John Zablocki [ 08/May/13 ]
Released.



[NCBC-247] Refactor 3rd party HttpClient implementations into separate assembly Created: 05/Apr/13  Updated: 08/May/13  Resolved: 08/May/13

Status: Closed
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: 1.2.4
Fix Version/s: 1.2.5

Type: Improvement Priority: Major
Reporter: John Zablocki Assignee: John Zablocki
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Currently, there are dependencies on Hammock (obsolete) and RestSharp for view queries. RestSharp requires a custom built assembly and can't be used with the NuGet package, because it's not signed. There is very little RestSharp code being used in an HTTP client and it's probably sufficient to use a standard WebClient as the default.

 Comments   
Comment by John Zablocki [ 08/May/13 ]
Released.



[NCBC-248] Touch should return a boolean Created: 06/Apr/13  Updated: 08/May/13

Status: Open
Project: Couchbase .NET client library
Component/s: docs, library
Affects Version/s: 1.2.4
Fix Version/s: 1.2.7

Type: Bug Priority: Major
Reporter: Mike Wiederhold Assignee: John Zablocki
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
If touch doesn't return anything then we need to at least update the documentation (with right now says touch returns a boolean) and explain how the user can know if the operation was successful.



[NCBC-249] We need documentation that explains how users can check for error codes Created: 06/Apr/13  Updated: 08/May/13

Status: Open
Project: Couchbase .NET client library
Component/s: docs
Affects Version/s: 1.2.4
Fix Version/s: 1.2.7

Type: Bug Priority: Major
Reporter: Mike Wiederhold Assignee: John Zablocki
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
I'm pretty sure that the .NET SDK allows us to do this, but I might be wrong. If we can properly check for errors we should document it.



[NCBC-227] intermittent failures during add-back rebalance Created: 13/Feb/13  Updated: 07/May/13  Resolved: 07/May/13

Status: Resolved
Project: Couchbase .NET client library
Component/s: library
Affects Version/s: 1.2.1
Fix Version/s: 1.2.5

Type: Bug Priority: Major
Reporter: Matt Ingenthron Assignee: Saakshi Manocha
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Our integration testing is showing irregular operations failing during tests where a node is failed over, then added back and rebalanced. This is not expected, as there should be no failures during rebalance.

Assigning to Saakshi to further fill out the description.

 Comments   
Comment by Saakshi Manocha [ 14/Feb/13 ]
- Reproduced the brun test lists again to include the newly added reAdd test.

- Ran the command:
python .\brun -C Sdkd.args -S dotnet-1.2-release -V 2.0.0-1976 -i cluster_config.ini -T HYBRID_readd-2
(This command will fail two nodes, add them back and then rebalance)

- Cluster_config.ini comprise of 4 nodes:
10.3.121.134 10.3.121.135 10.3.121.136 10.3.3.206

- Output is here:
http://sdk-testresults.couchbase.com.s3.amazonaws.com/sdkd/HWIN-335SPEPOCGT-IHYBRID_readd-2-Sdotnet-1.2-release-T2013-02-14-03.49.12-LV_CB_BASIC.txt

http://sdk-testresults.couchbase.com.s3.amazonaws.com/sdkd/HWIN-335SPEPOCGT-IHYBRID_readd-2-Sdotnet-1.2-release-T2013-02-14-03.49.12-LV_MC_BASIC.txt

http://sdk-testresults.couchbase.com.s3.amazonaws.com/sdkd/HWIN-335SPEPOCGT-IHYBRID_readd-2-Sdotnet-1.2-release-T2013-02-14-03.49.12-LV_HTTP_BASIC.txt

- Observations:
(a) Following errors occur continuously during CHANGE phase while the rebalance operation is undergoing:
      [Enyim.Caching.Memcached.MemcachedNode|Error] System.IO.IOException: Failed to read from the socket '10.3.121.136:11210'. Error: SocketError value was Success, but 0 bytes were received
      [Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl|Error] Could not init pool. System.NullReferenceException Object reference not set to an instance of an object.
      [Sdkd.ViewQuery|Warn] Unrecognized error System.Net.WebException The operation has timed out

(b) No Errors occur during REBOUND phase, which is a good sign. This is the time when Rebalance operation is complete and no more topology changes occur.
Comment by Mark Nunberg [ 14/Feb/13 ]
Interesting to note that there are NOT_MY_VBUCKET errors well after the rebalance after the readd
Comment by Saakshi Manocha [ 01/Mar/13 ]
Ran a full suite of hybrid test scenarios using sdkd and latest enyim.caching changes (as done by John related to issue# CBSE-396).
The report is ready with comments and shared through Google docs:
sdkd-reports -> nosdk-nocluster-3d_AT-2013-02-24T22-21-32

The report has better grades than the last month report which is good.
Comment by Saakshi Manocha [ 05/Mar/13 ]
The report: sdkd-reports -> nosdk-nocluster-3d_AT-2013-02-24T22-21-32
shows the error messages occur in debug mode during rebalance, but the error rate does not increase. And during and after rebound phase, the errors disappear and there is a full recovery of the cluster.
As long as there are no errors after rebalance operation is complete, the report is good.
Comment by Matt Ingenthron [ 06/Mar/13 ]
Note that we ran into this in a Java deployment today. There may be something odd happening here.

Is it possible to capture from this, using 2.0.0 server on linux, a packet capture of port 8091, 8092 and 11210 from the client system? This would allow us to see if the cluster is behaving as expected.
Comment by Saakshi Manocha [ 07/May/13 ]
The required changes for this issue already got released with NCBC-228, so I'm closing out this one.
No further similar issue reported



[NCBC-244] Explicit docs for what .NET Framework versions are supported Created: 02/Apr/13  Updated: 06/May/13

Status: In Progress
Project: Couchbase .NET client library
Component/s: docs
Affects Version/s: 1.2.3
Fix Version/s: None

Type: Task Priority: Minor
Reporter: Tim Smith Assignee: John Zablocki
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment: http://www.couchbase.com/docs/couchbase-sdk-net-1.2/ch01s03s01.html


 Description   
Need to be explicit about what versions of Visual Studio are supported, and what .NET Framework is supported. 3.5? 4.0?

The docs mention that you need the full .NET Framework, not just a Client profile. But don't mention if 4.0 is needed. It seems that 3.5 is not supported, but I'm not positive.



 Comments   
Comment by Tim Smith [ 02/Apr/13 ]
I just got this update:

The 1.2 versions use 4.0 features for some things. 3.5 will still work with the 1.1 series (1.2 series is recommended, has important stability fixes).
Comment by Tim Smith [ 02/Apr/13 ]
Probably need to confirm this info, and decide if we want to just state plainly that 4.0 features are used in the .NET SDK. Probably need input from SDK dev team on this.

Tim
Comment by John Zablocki [ 02/Apr/13 ]
The release note for 1.2 GA does announce the 4.0 requirement - http://www.couchbase.com/docs/couchbase-sdk-net-1.2/couchbase-sdk-net-rn_1-2-0g.html. But agree, it could be added to the getting started. 3.5 support will be targeted for the May release.



[NCBC-245] Document bugs Created: 02/Apr/13  Updated: 17/Apr/13  Resolved: 17/Apr/13

Status: Closed
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Trivial
Reporter: Saakshi Manocha Assignee: John Zablocki
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Reviewed the Getting Started Guide at link : http://www.couchbase.com/docs/couchbase-sdk-net-1.2/stage1.html

The overall document looks good, however, few points that may be considered are:

1. Prerequisites
Mention the link where to download asp.net mvc4

2.4. Encapsulating Data Access
Add reference to couchbase.dll in project and include the statement
"using couchbase;"

2.5. Working with ViewsMay be a short description or screenshot on how to add a new design document in couchbase console.
Add few details of how to access CouchbaseLabs project and the CouchbaseCluster API found in Couchbase.dll

The below statement
"using CouchbaseModelViews.Framework.Attributes; "
is required when we define class level attributes

The below statement
"using System.Reflection;
using CouchbaseModelViews.Framework; "
is required in Global.asax class

The below statement
"using CouchbaseBeerWeb.Models; "
is required in BreweriesController class

 Comments   
Comment by John Zablocki [ 03/Apr/13 ]
Tutorial updated and pull request sent to the docs team...

1. I added a link to asp.net/mvc
2.4 Project setup in 2.2 already mentions the reference. I added the using.
2.5 I added a link to the docs for using the View editor as well as links to Couchbase Labs and the Cluster API.

I don't think the using statements are necessary, since this is a description of a project that is on GitHub. It's not meant to be a fully functioning set of code.
Comment by Saakshi Manocha [ 04/Apr/13 ]
Thanks John. Where can I see the changes made to the document, the changes are still not reflecting in the link here: http://www.couchbase.com/docs/couchbase-sdk-net-1.2/stage1.html
Will they be seen after docs team uploads the changes ?
Comment by Saakshi Manocha [ 17/Apr/13 ]
Verified the changes done, closing the issue.



[NCBC-240] Fix dependency issue of nunit.framework in Enyim.Caching\MemcachedTest and assembly signing Created: 26/Mar/13  Updated: 16/Apr/13  Resolved: 16/Apr/13

Status: Resolved
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: Saakshi Manocha Assignee: Saakshi Manocha
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
We need to fix the missing binary reference of nunit.framework.dll from Enyim.Caching\MemcachedTest repository and also work on signing of assembly like the ironpython script of enyim-dev-prep.py in EnyimMemcached repository.

 Comments   
Comment by Saakshi Manocha [ 05/Apr/13 ]
Task done:
For the missing reference of nunit.framework.dll and disable signing of assemblies, i have sent a pull request from the forked repository.
you could review here: https://github.com/couchbase/EnyimMemcached/pull/11
and then merge it with the mail repo if the changes are good.

Question:
I could not submit the changes for this project to gerrit, is this project not configured in Gerrit ?



Fix invalid tests in NUnit project. (NCBC-174)

[NCBC-250] Fix the test : CouchbaseAuthenticatedViewTests\When_Bucket_Is_Authenticated_View_Returns_Results Created: 09/Apr/13  Updated: 09/Apr/13

Status: Open
Project: Couchbase .NET client library
Component/s: library
Affects Version/s: 1.2.4
Fix Version/s: 1.2.5

Type: Technical task Priority: Minor
Reporter: Saakshi Manocha Assignee: John Zablocki
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Fix the following test in .Net library, it is constantly failing:

Test Class: CouchbaseAuthenticatedViewTests
Test Name: When_Bucket_Is_Authenticated_View_Returns_Results

Reason for failure:
There is no document/view getting created in SASL bucket with name "authenticated".
Instead the code creates the documents/views in "default" bucket since the code uses the default initialization of couchbase client which uses the "default" bucket.




[NCBC-241] Fix dependency issue of nunit.framework in Enyim.Caching\MemcachedTest and assembly signing Created: 26/Mar/13  Updated: 04/Apr/13  Resolved: 04/Apr/13

Status: Resolved
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Minor
Reporter: Saakshi Manocha Assignee: John Zablocki
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Dependency

 Description   

We need to fix the missing binary reference of nunit.framework.dll from Enyim.Caching\MemcachedTest repository and also work on signing of assembly like the ironpython script of enyim-dev-prep.py in EnyimMemcached repository.


 Comments   
Comment by Saakshi Manocha [ 04/Apr/13 ]
Duplicate of NCBC-240



[NCBC-224] Critical:Problematic Link for Download Client Library. Created: 06/Feb/13  Updated: 03/Apr/13  Resolved: 03/Apr/13

Status: Closed
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: 1.2.1
Fix Version/s: None

Type: Task Priority: Major
Reporter: Muthu Kumar Assignee: John Zablocki
Resolution: Fixed Votes: 0
Labels: .net, client, clients, corrupt, download, link
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
The Download link for the .Net Client needs to be fixed. The existing link doesn't work as expected. It has corrupted files.

"Download Client Library" in this http://www.couchbase.com/docs/couchbase-sdk-net-1.2/index.html has to be Fixed

The link should be

http://packages.couchbase.com/clients/net/1.2/Couchbase-Net-Client-1.2.0.zip or http://packages.couchbase.com/clients/net/1.2/Couchbase-Net-Client-1.2.1.zip

 Comments   
Comment by John Zablocki [ 06/Feb/13 ]
Pull request sent to docs team.



[NCBC-239] RestSharpHttpClient timeout value set from wrong timespan property Created: 22/Mar/13  Updated: 03/Apr/13  Resolved: 03/Apr/13

Status: Closed
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: 1.2.3
Fix Version/s: 1.2.4

Type: Task Priority: Critical
Reporter: John Zablocki Assignee: John Zablocki
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Zip Archive NCBC-239.zip    

 Comments   
Comment by John Zablocki [ 22/Mar/13 ]
Verification build.
Comment by John Zablocki [ 03/Apr/13 ]
Released



[NCBC-238] Allow support for in-memory on master only key checks with Observe Created: 21/Mar/13  Updated: 03/Apr/13  Resolved: 03/Apr/13

Status: Closed
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: None
Fix Version/s: 1.2.4

Type: Improvement Priority: Major
Reporter: John Zablocki Assignee: John Zablocki
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Basic use case is to allow a user to check key exists without doing a Get.

 Comments   
Comment by Perry Krug [ 21/Mar/13 ]
Worth using the "stats key" instead? You can get more info back and use that in other ways...
Comment by John Zablocki [ 21/Mar/13 ]
Not opposed to that option, but this effort basically came for free since I had to add a missing code path for an existing method. KeyExists() just wraps that scenario.
Comment by John Zablocki [ 03/Apr/13 ]
Released



[NCBC-231] Implement getl operation Created: 20/Feb/13  Updated: 03/Apr/13  Resolved: 03/Apr/13

Status: Closed
Project: Couchbase .NET client library
Component/s: library
Affects Version/s: 1.2.1
Fix Version/s: 1.2.4

Type: New Feature Priority: Major
Reporter: John Zablocki Assignee: John Zablocki
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Zip Archive CouchbaseNetClient-1.2.4.zip    

 Comments   
Comment by Perry Krug [ 21/Feb/13 ]
John, when this has been implemented, would it be possible to get a pre-release build for a customer who is working on an implementation at the moment?
Comment by Perry Krug [ 12/Mar/13 ]
Hey John, any update on this? I've just got a customer asking for a pre-release if available...

thanks
Comment by John Zablocki [ 12/Mar/13 ]
No status at this time. I hope to be able to look into this next week.
Comment by John Zablocki [ 20/Mar/13 ]
Verification build.
Comment by John Zablocki [ 03/Apr/13 ]
Released



[NCBC-211] Bug in .Net Documentation (A line repeated twice) Created: 28/Jan/13  Updated: 03/Apr/13  Resolved: 03/Apr/13

Status: Closed
Project: Couchbase .NET client library
Component/s: docs
Affects Version/s: 1.2.0
Fix Version/s: 1.2.4

Type: Bug Priority: Major
Reporter: Muthu Kumar Assignee: Matt Ingenthron
Resolution: Fixed Votes: 0
Labels: bug, documentation
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Hi Team,
   There is a line that is repeated twice in this document, that needs to be corrected.

http://www.couchbase.com/develop/net/current

"If you add a line to print the savedBeer to the console, you should see a JSON string that contains the data above. If you add a line to print the savedBeer to the console, you should see a JSON string that contains the data above."

 Comments   
Comment by John Zablocki [ 19/Feb/13 ]
Matt - the latest revision of this page should be published to fix this problem.



[NCBC-209] Mistake in http://www.couchbase.com/develop/net/current document Created: 22/Jan/13  Updated: 03/Apr/13  Resolved: 03/Apr/13

Status: Closed
Project: Couchbase .NET client library
Component/s: docs
Affects Version/s: 1.2.0
Fix Version/s: 1.2.4

Type: Bug Priority: Major
Reporter: Vijayaraghavan Mohanasundaram Assignee: Matt Ingenthron
Resolution: Fixed Votes: 0
Labels: customer
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment: Microsoft Windows, ,Net


 Description   
Hi Team,
   There is a bug in document, that needs to be corrected.

Document Link "http://www.couchbase.com/develop/net/current"

Issue reported : 'Instantiating the Client' section

    public static class CouchbaseManager
    {
    private readonly static CouchbaseClient _instance;
    static CouchbaseClient()
    {
    _instance = new CouchbaseClient();
    }
    public static CouchbaseClient Instance { get { return _instance; } }
    }

Error to be rectified : 4th line static CouchbaseClient() should be -> static CouchbaseManager()

 Comments   
Comment by John Zablocki [ 19/Feb/13 ]
Another fix in the latest revision for that page



[NCBC-122] whitespace not allowed by default Created: 19/Sep/12  Updated: 02/Apr/13  Resolved: 02/Apr/13

Status: Closed
Project: Couchbase .NET client library
Component/s: library
Affects Version/s: None
Fix Version/s: 1.2.1

Type: Bug Priority: Major
Reporter: Mark Nunberg Assignee: John Zablocki
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Apparently the default KeyTransformer does not allow whitespace or control characters. This is likely a relic from the ASCII memcached protocol and shouldn't be the default for couchbase users.

 Comments   
Comment by Matt Ingenthron [ 19/Sep/12 ]
Actually, I don't know that we decided whitespace should be legal. While it is per the protocol, there are parts of the server that may not behave properly. We should follow up on this one before promising to support it. May even get into XDCR questions.
Comment by Matt Ingenthron [ 04/Oct/12 ]
Unknown if we'll allow this, a decision needs to be made on the server compatibility.
Comment by John Zablocki [ 02/Apr/13 ]
NCBC-166



[NCBC-237] Exists and Count/TotalRows Created: 14/Mar/13  Updated: 02/Apr/13  Resolved: 02/Apr/13

Status: Resolved
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: None
Fix Version/s: 1.2.4

Type: New Feature Priority: Minor
Reporter: Daniel Wertheim Assignee: John Zablocki
Resolution: Fixed Votes: 0
Labels: .net
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Would be nice to either be able to get the keys that are stored in RAM or for you to implement simple `Exists(key:string)` and `Count` members.

Exists would be really nice to have instead of performing a Get which also pulls the actual data. Of course you could work around this by creating a view, but it seems overkill just to check for key existence.

//Dan



[NCBC-243] Client hangs when requested durability nodes > available nodes Created: 29/Mar/13  Updated: 01/Apr/13  Resolved: 01/Apr/13

Status: Resolved
Project: Couchbase .NET client library
Component/s: library
Affects Version/s: 1.2.3
Fix Version/s: None

Type: Task Priority: Major
Reporter: Mark Nunberg Assignee: Mark Nunberg
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
When requesting durability to more nodes than the cluster has online, an ObserveExpectationException is not thrown and the client waits forever.

 Comments   
Comment by Mark Nunberg [ 29/Mar/13 ]
http://review.couchbase.org/#/c/25410/



[NCBC-229] Add Remove with Cas overload Created: 19/Feb/13  Updated: 05/Mar/13  Resolved: 05/Mar/13

Status: Closed
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: 1.2.1
Fix Version/s: 1.2.2

Type: New Feature Priority: Major
Reporter: John Zablocki Assignee: John Zablocki
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Comments   
Comment by John Zablocki [ 05/Mar/13 ]
Released



[NCBC-228] Frequent PooledSocket errors appear during rebalance Created: 19/Feb/13  Updated: 05/Mar/13  Resolved: 05/Mar/13

Status: Closed
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: 1.2.1
Fix Version/s: 1.2.2

Type: Task Priority: Major
Reporter: John Zablocki Assignee: John Zablocki
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Zip Archive Couchbase-1.2.2_Pre-Release.zip    

 Description   
During a rebalance - or any other period with frequent configuration updates - there appears to be a concurrency issue where pooled sockets are being destroyed while still in use.

 Comments   
Comment by John Zablocki [ 19/Feb/13 ]
Local build with fix, verified locally not by QE.
Comment by John Zablocki [ 19/Feb/13 ]
Adding a brief delay between the triggering of the disposal of a node instance and its actual resource disposal appears to avoid any concurrency issues, at least during a rebalance.
Comment by John Zablocki [ 05/Mar/13 ]
Released



[NCBC-234] ExecuteGetJson does not return CAS value Created: 26/Feb/13  Updated: 05/Mar/13  Resolved: 05/Mar/13

Status: Closed
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: 1.2.1
Fix Version/s: 1.2.2

Type: Task Priority: Major
Reporter: John Zablocki Assignee: John Zablocki
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Comments   
Comment by John Zablocki [ 05/Mar/13 ]
Released



[NCBC-179] Add expiries and CAS to StoreJson extension methods Created: 12/Dec/12  Updated: 20/Feb/13

Status: Reopened
Project: Couchbase .NET client library
Component/s: library
Affects Version/s: 1.2.0
Fix Version/s: 1.2.1

Type: New Feature Priority: Minor
Reporter: John Zablocki Assignee: John Zablocki
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Comments   
Comment by John Zablocki [ 05/Feb/13 ]
Released
Comment by Perry Krug [ 06/Feb/13 ]
Hey John, this this come with associated doc changes? Can you link to them?

Thanks
Comment by John Zablocki [ 20/Feb/13 ]
I haven't had a chance to work on doc improvements. After 1.2.2 is released, I'll try to prioritize doc updates.



[NCBC-58] Way to determine which Servers are active Created: 05/Jun/12  Updated: 18/Feb/13

Status: Open
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: None
Fix Version/s: 1.3

Type: Improvement Priority: Major
Reporter: James Mauss Assignee: John Zablocki
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Can there a way to determine if there are no available Couchbase servers?
There should be someway to check the status of the cluster from the Client.


 Comments   
Comment by Hari Subramaniam [ 28/Jun/12 ]
along same lines, another customer requests enhancement to the .NET client to include the following methods
getUnavailableServers
getAvailableServers

These methods are already available in the Couchbase JAVA SDK. Would like .NET SDK to provide the same functionality
Comment by Matt Ingenthron [ 12/Feb/13 ]
This RFE will remain open for that.



[NCBC-12] logging level documentation needed Created: 05/Dec/11  Updated: 07/Feb/13

Status: Reopened
Project: Couchbase .NET client library
Component/s: docs
Affects Version/s: None
Fix Version/s: 1.2.1

Type: Improvement Priority: Minor
Reporter: Matt Ingenthron Assignee: John Zablocki
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Currently, there's insufficient information on how to change the logging level to see what's happening when diagnosing an issue.

 Comments   
Comment by Matt Ingenthron [ 05/Dec/11 ]
From Bin:

Attila added more logging for operation Delete/Get/Set at https://github.com/enyim/EnyimMemcached/commit/768fb5956f2f69b6c57a484a3aee367dc0d42ba0#Enyim.Caching/Memcached/Protocol/Binary/GetOperation.cs.
 
The customer needs to get the latest Enyim library and build with symbol ‘EVEN_MORE_LOGGING’. See attached picture for illustration.
At the same time, they need to set the log level to DEBUG in their configuration file.
Comment by John Zablocki [ 02/Mar/12 ]
I added a section "Configuring Logging" to the "Getting Started" document - http://www.couchbase.com/develop/net/current. This doesn't cover the build with EVEN_MORE_LOGGING though...
Comment by John Zablocki [ 05/Feb/13 ]
Released
Comment by Perry Krug [ 07/Feb/13 ]
John, does this doc need to be updated to cover EVEN_MORE_LOGGING?

This is related to NCBC-225 as well.



[NCBC-150] Increment examples show incorrect initialization of key Created: 07/Nov/12  Updated: 06/Feb/13  Resolved: 06/Feb/13

Status: Resolved
Project: Couchbase .NET client library
Component/s: docs
Affects Version/s: 1.1.6
Fix Version/s: 1.2.1

Type: Bug Priority: Major
Reporter: Perry Krug Assignee: John Zablocki
Resolution: Fixed Votes: 0
Labels: customer
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
http://www.couchbase.com/docs/couchbase-sdk-net-1.1/couchbase-sdk-net-update-increment.html

All of the examples on this page show the default value as an integer when in reality it needs to be enclosed in quotes in order to function properly. There should also be a note/warning in the documentation warning users of this idiosyncrasy


 Comments   
Comment by John Zablocki [ 08/Jan/13 ]
The default value should be a ulong as shown in the docs. I've updated the docs (and sent a pull request) to note that it's not possible to use with Store.

https://github.com/enyim/EnyimMemcached/issues/86
Comment by Perry Krug [ 09/Jan/13 ]
Hey John, thanks for taking a look at this.

What do you mean that it's not possible to use with Store? Do you mean it's not supported to initialize a counter with store, or just that you can't use a ulong?
Comment by John Zablocki [ 09/Jan/13 ]
Well, technically (as you noted) it will work to set a string value via Store and then increment it, but I think that's unintentional behavior and works only because (as Attila pointed out in the linked issue) of the way counters are treated on the server. The correct use of the API should be to initialize a counter with Increment or Decrement by setting the default value.

Either way I think there's an intentional step imposed on the developer. I think it's better to discourage setting a value as a string to initialize a counter, since that's not very intuitive.

Thoughts?
Comment by Perry Krug [ 09/Jan/13 ]
Thanks for the clarification, makes perfect sense to me.

I do, however, think we need to make that distinction clearer in the docs, both on the increment side and the store side to let customers know what the best practices are (what to do is good, what NOT to do is even more important IMO)

Thanks
Comment by John Zablocki [ 05/Feb/13 ]
Released
Comment by Perry Krug [ 06/Feb/13 ]
Hey John, could you fill in the links of the areas that changed?

Thanks
Comment by Perry Krug [ 06/Feb/13 ]
Never mind, I see it now: http://www.couchbase.com/docs/couchbase-sdk-net-1.2/couchbase-sdk-net-update-increment.html



[NCBC-77] Need details on "StoreMode" values Created: 26/Jun/12  Updated: 06/Feb/13

Status: Reopened
Project: Couchbase .NET client library
Component/s: docs
Affects Version/s: 1.1.6
Fix Version/s: 1.2.1

Type: Bug Priority: Major
Reporter: Perry Krug Assignee: John Zablocki
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
In this page: http://www.couchbase.com/docs/couchbase-sdk-net-1.1/couchbase-sdk-net-retrieve-set.html

There is no detail on what the available store modes are (set/add/replace)

 Comments   
Comment by John Zablocki [ 10/Jan/13 ]
Pull request pending in docs.
Comment by John Zablocki [ 05/Feb/13 ]
Released
Comment by Perry Krug [ 06/Feb/13 ]
http://www.couchbase.com/docs/couchbase-sdk-net-1.2/couchbase-sdk-net-store-set.html

Hey John, I think this page could still use a little cleaning up.

Many of the API calls are listed as: "object.Store(storemode, key, value, expiresat)". and the descriptions are all the same as well. Some of the API calls do not match the method they are describing (see the very last one for example)

Can we include some description of what the user should expect to see when each of them fails?



[NCBC-166] allow full fidelity of keys with .NET client Created: 26/Nov/12  Updated: 05/Feb/13  Resolved: 05/Feb/13

Status: Closed
Project: Couchbase .NET client library
Component/s: docs
Affects Version/s: None
Fix Version/s: 1.2.1

Type: Improvement Priority: Critical
Reporter: Matt Ingenthron Assignee: John Zablocki
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Currently, underlying EnyimMemcached does a certain amount of key validation, based on legacy memcached rules. We've decided that we'll allow any binary byte-string for keys, with some caveats. This means that for the 1.2 client, we should support the same fidelity.

The caveats are:
* We expect this to be fine with all key/value use cases in Couchbase Server 2.0
* We strongly recommend users select keys which are valid UTF-8 such that they can be used in views. This is valid even with \0, \n, \r, " ", etc.
* Couchbase Server 2.0 does not have any known issues with the above, but some areas like Cross Datacenter Replication, backup and restore, statistics utilities have not been fully tested and could have unknown issues. Any issues will be fixed with subsequent fixes in the 2.0.x release line.

 Comments   
Comment by John Zablocki [ 05/Feb/13 ]
Released



[NCBC-189] NRE thrown in Increment/Decrement with CAS Created: 27/Dec/12  Updated: 05/Feb/13  Resolved: 05/Feb/13

Status: Closed
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: 1.2.0
Fix Version/s: 1.2.1

Type: Bug Priority: Major
Reporter: John Zablocki Assignee: John Zablocki
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Zip Archive Couchbase-1.2.1-Preview.zip    

 Description   
https://gist.github.com/4353487 --> Link from which the code is used.
https://github.com/couchbase/EnyimMemcached/pull/4 --> Pull request submitted by customer
https://github.com/couchbase/EnyimMemcached/commit/5b3e829ef9491923d2eb3c28e4be8551ac220ee8#commitcomment-2345966 --> Reference link provided by customer.

 Comments   
Comment by John Zablocki [ 02/Jan/13 ]
Attached is 1.2.1 preview with fix for this issue. This is not a fully tested version.
Comment by John Zablocki [ 02/Jan/13 ]
Attachment Couchbase.zip is invalid, please disregard.
Comment by Saran Kumar [ 29/Jan/13 ]
Hi John,

Could you please let us know the status on this issue as the customer is expecting an update.

Thanks,
Saran
Comment by John Zablocki [ 29/Jan/13 ]
Per my last note, their merge is in the attached build. 1.2.1 will contain this merge when it's released on 2/5/13.
Comment by Saran Kumar [ 29/Jan/13 ]
Please confirm if i can pass the attached build( Couchbase-1.2.1-Preview.zip ) to the customer or should i ask him to wait for the 1.2.1 release on 2/5/13.

Comment by John Zablocki [ 04/Feb/13 ]
The build was attached for customer verification, however, the 1.2.1 client is being tested by QE now and is expected to be released tomorrow.
Comment by John Zablocki [ 05/Feb/13 ]
Released



[NCBC-192] NRE when executing ops against down node or invalid configuration Created: 02/Jan/13  Updated: 05/Feb/13  Resolved: 05/Feb/13

Status: Closed
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: 1.2.0
Fix Version/s: 1.2.1

Type: Bug Priority: Critical
Reporter: John Zablocki Assignee: John Zablocki
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Zip Archive Couchbase-Net-Client-1.2.1.zip     Zip Archive Couchbase-Net-Client-Logging-1.2.1.zip    

 Comments   
Comment by John Zablocki [ 02/Jan/13 ]
Fix pushed to Gerrit for review.
Comment by John Zablocki [ 03/Jan/13 ]
Pre-release of 1.2.1 build attached.
Comment by John Zablocki [ 03/Jan/13 ]
Attached are two new build packages - previous packages were from incorrect builds. NUnit tests verified and dotPeek verified.
Comment by John Zablocki [ 05/Feb/13 ]
Released



[NCBC-208] Missing method summaries in API docs Created: 18/Jan/13  Updated: 05/Feb/13  Resolved: 05/Feb/13

Status: Closed
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: None
Fix Version/s: 1.2.1

Type: Bug Priority: Major
Reporter: John Zablocki Assignee: John Zablocki
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
http://www.couchbase.com/docs/couchbase-sdk-net-1.2/api-reference-retrieve.html
 -- object.GetWithCas(key)

http://www.couchbase.com/docs/couchbase-sdk-net-1.2/api-reference-update.html
 -- object.Cas(storemode, key, value) //all overloads
 -- object.ExecuteCas(storemode, key, value, expiresat, casunique) //all overloads
 -- object.Increment/ExecuteIncrement(key, defaultvalue, offset, casunique) //all overloads
  

 Comments   
Comment by John Zablocki [ 18/Jan/13 ]
Pull request sent.
Comment by John Zablocki [ 05/Feb/13 ]
Released



[NCBC-159] Add Debug option to queries Created: 21/Nov/12  Updated: 05/Feb/13  Resolved: 05/Feb/13

Status: Closed
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: 1.2 Beta
Fix Version/s: 1.2.1

Type: Improvement Priority: Minor
Reporter: John Zablocki Assignee: John Zablocki
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Comments   
Comment by John Zablocki [ 21/Nov/12 ]
Published and tagged
Comment by John Zablocki [ 08/Jan/13 ]
Debug JSON format changed between Beta and GA
Comment by John Zablocki [ 05/Feb/13 ]
Released



[NCBC-75] Sync operation does not actually exist, and it should not say "Membase" Created: 26/Jun/12  Updated: 05/Feb/13  Resolved: 05/Feb/13

Status: Closed
Project: Couchbase .NET client library
Component/s: docs
Affects Version/s: None
Fix Version/s: 1.2.1

Type: Bug Priority: Major
Reporter: Perry Krug Assignee: John Zablocki
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
This page: http://www.couchbase.com/docs/couchbase-sdk-net-1.1/couchbase-sdk-net-update-sync.html

 Comments   
Comment by John Zablocki [ 26/Jun/12 ]
There is actually a Sync method on CouchbaseClient.
Comment by Perry Krug [ 26/Jun/12 ]
Will have to check with Matt, but I believe it was disabled on the server-side...or at least should not be documented since we don't support it. I think the page should be removed, but if it stays we need to change Membase to Couchbase and provide examples on how to use so it doesn't look as empty as it does now.
Comment by John Zablocki [ 10/Jan/13 ]
Pull request sent. Removed from docs.
Comment by John Zablocki [ 05/Feb/13 ]
Released



[NCBC-190] Support bucket flushing Created: 27/Dec/12  Updated: 05/Feb/13  Resolved: 05/Feb/13

Status: Closed
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: 1.2.0
Fix Version/s: 1.2.1

Type: New Feature Priority: Major
Reporter: John Zablocki Assignee: John Zablocki
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Comments   
Comment by John Zablocki [ 05/Feb/13 ]
Released



[NCBC-191] Update submodule to latest Enyim commits Created: 02/Jan/13  Updated: 05/Feb/13  Resolved: 05/Feb/13

Status: Closed
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: None
Fix Version/s: 1.2.1

Type: New Feature Priority: Major
Reporter: John Zablocki Assignee: John Zablocki
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Comments   
Comment by John Zablocki [ 05/Feb/13 ]
Released



[NCBC-212] ExecuteRemove swallows status code Created: 28/Jan/13  Updated: 05/Feb/13  Resolved: 05/Feb/13

Status: Closed
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: 1.2.0
Fix Version/s: 1.2.1

Type: Bug Priority: Major
Reporter: John Zablocki Assignee: John Zablocki
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Comments   
Comment by John Zablocki [ 05/Feb/13 ]
Released



[NCBC-172] NRE In view query during rebalance-in Created: 06/Dec/12  Updated: 05/Feb/13  Resolved: 05/Feb/13

Status: Closed
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: 1.2.0
Fix Version/s: 1.2.1

Type: Bug Priority: Critical
Reporter: Mark Nunberg Assignee: John Zablocki
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment: Cluster 1974, SDK Versions (master at time of writing)

Attachments: Zip Archive Couchbase-Net-Client-1.2.1.zip     Zip Archive Couchbase-Net-Client-Logging-1.2.1.zip     Text File NCBC-172-readable.txt     File RestSharp.dll     Text File RestSharpHttpClient.cs    

 Description   
[INFO 32.82 cbsdk.scenario rebalance.py:207] Sleeping 30 seconds for ramp-up
[ACTION 62.84 cbsdk.scenario rebalance.py:210] Starting rebalance action
[SDKD(INFO) 65.22 cbsdk.sdkd.remote remote.py:263] [Couchbase.CouchbaseViewHandler|Warn] View Couchbase.CouchbaseViewHandler was mapped to a dead node, failing.
[SDKD(INFO) 65.22 cbsdk.sdkd.remote remote.py:263] [Sdkd.ViewQuery|Error] ... System.InvalidOperationException Operation is not valid due to the current state of the object. at Couchbase.CouchbaseViewHandler.GetResponse(IDictionary`2 viewParams) in c:\ncbc\src\Couchbase\CouchbaseViewHandler.cs:line 131
[SDKD(INFO) 65.22 cbsdk.sdkd.remote remote.py:263] at Couchbase.CouchbaseViewHandler.<TransformResults>d__0`1.MoveNext() in c:\ncbc\src\Couchbase\CouchbaseViewHandler.cs:line 38
[SDKD(INFO) 65.22 cbsdk.sdkd.remote remote.py:263] at Sdkd.Views.ViewCommand.Run() in c:\Users\Administrator\Documents\GitHub\sdkd-net\src\Sdkd\Views\ViewCommand.cs:line 219
[SDKD(INFO) 65.91 cbsdk.sdkd.remote remote.py:263] [Couchbase.CouchbaseViewHandler|Warn] View Couchbase.CouchbaseViewHandler was mapped to a dead node, failing.
[SDKD(INFO) 65.91 cbsdk.sdkd.remote remote.py:263] [Couchbase.CouchbaseViewHandler|Warn] View Couchbase.CouchbaseViewHandler was mapped to a dead node, failing.
[SDKD(INFO) 65.91 cbsdk.sdkd.remote remote.py:263] [Couchbase.CouchbaseViewHandler|Warn] View Couchbase.CouchbaseViewHandler was mapped to a dead node, failing.
[SDKD(INFO) 65.91 cbsdk.sdkd.remote remote.py:263] [Couchbase.CouchbaseViewHandler|Warn] View Couchbase.CouchbaseViewHandler was mapped to a dead node, failing.
[SDKD(INFO) 65.92 cbsdk.sdkd.remote remote.py:263] [Couchbase.CouchbaseViewHandler|Warn] View Couchbase.CouchbaseViewHandler was mapped to a dead node, failing.
[SDKD(INFO) 65.92 cbsdk.sdkd.remote remote.py:263] [Couchbase.CouchbaseViewHandler|Warn] View Couchbase.CouchbaseViewHandler was mapped to a dead node, failing.
[SDKD(INFO) 65.92 cbsdk.sdkd.remote remote.py:263] [Couchbase.CouchbaseViewHandler|Warn] View Couchbase.CouchbaseViewHandler was mapped to a dead node, failing.
[SDKD(INFO) 65.92 cbsdk.sdkd.remote remote.py:263] [Couchbase.CouchbaseViewHandler|Warn] View Couchbase.CouchbaseViewHandler was mapped to a dead node, failing.
[SDKD(INFO) 65.92 cbsdk.sdkd.remote remote.py:263] [Couchbase.CouchbaseViewHandler|Warn] View Couchbase.CouchbaseViewHandler was mapped to a dead node, failing.
[SDKD(INFO) 65.92 cbsdk.sdkd.remote remote.py:263] [Couchbase.CouchbaseViewHandler|Warn] View Couchbase.CouchbaseViewHandler was mapped to a dead node, failing.
[SDKD(INFO) 65.92 cbsdk.sdkd.remote remote.py:263] [Couchbase.CouchbaseViewHandler|Warn] View Couchbase.CouchbaseViewHandler was mapped to a dead node, failing.
[SDKD(INFO) 65.92 cbsdk.sdkd.remote remote.py:263] [Couchbase.CouchbaseViewHandler|Warn] View Couchbase.CouchbaseViewHandler was mapped to a dead node, failing.
[SDKD(INFO) 65.92 cbsdk.sdkd.remote remote.py:263] [Couchbase.CouchbaseViewHandler|Warn] View Couchbase.CouchbaseViewHandler was mapped to a dead node, failing.
[SDKD(INFO) 65.92 cbsdk.sdkd.remote remote.py:263] [Couchbase.CouchbaseViewHandler|Warn] View Couchbase.CouchbaseViewHandler was mapped to a dead node, failing.
[SDKD(INFO) 65.92 cbsdk.sdkd.remote remote.py:263] [Couchbase.CouchbaseViewHandler|Warn] View Couchbase.CouchbaseViewHandler was mapped to a dead node, failing.
[SDKD(INFO) 65.92 cbsdk.sdkd.remote remote.py:263] [Couchbase.CouchbaseViewHandler|Warn] View Couchbase.CouchbaseViewHandler was mapped to a dead node, failing.
[SDKD(INFO) 65.92 cbsdk.sdkd.remote remote.py:263] [Couchbase.CouchbaseViewHandler|Warn] View Couchbase.CouchbaseViewHandler was mapped to a dead node, failing.
[SDKD(INFO) 65.92 cbsdk.sdkd.remote remote.py:263] [Couchbase.CouchbaseViewHandler|Warn] View Couchbase.CouchbaseViewHandler was mapped to a dead node, failing.
[SDKD(INFO) 65.92 cbsdk.sdkd.remote remote.py:263] [Couchbase.CouchbaseViewHandler|Warn] View Couchbase.CouchbaseViewHandler was mapped to a dead node, failing.
[SDKD(INFO) 65.92 cbsdk.sdkd.remote remote.py:263] [Couchbase.CouchbaseViewHandler|Warn] View Couchbase.CouchbaseViewHandler was mapped to a dead node, failing.
[SDKD(INFO) 65.92 cbsdk.sdkd.remote remote.py:263] [Couchbase.CouchbaseViewHandler|Warn] View Couchbase.CouchbaseViewHandler was mapped to a dead node, failing.
[SDKD(INFO) 66.24 cbsdk.sdkd.remote remote.py:263] [Couchbase.CouchbaseViewHandler|Warn] View Couchbase.CouchbaseViewHandler was mapped to a dead node, failing.
[SDKD(INFO) 66.24 cbsdk.sdkd.remote remote.py:263] [Couchbase.CouchbaseViewHandler|Warn] View Couchbase.CouchbaseViewHandler was mapped to a dead node, failing.
[SDKD(INFO) 66.24 cbsdk.sdkd.remote remote.py:263] [Couchbase.CouchbaseViewHandler|Warn] View Couchbase.CouchbaseViewHandler was mapped to a dead node, failing.
[SDKD(INFO) 66.24 cbsdk.sdkd.remote remote.py:263] [Couchbase.CouchbaseViewHandler|Warn] View Couchbase.CouchbaseViewHandler was mapped to a dead node, failing.
[SDKD(INFO) 66.24 cbsdk.sdkd.remote remote.py:263] [Couchbase.CouchbaseViewHandler|Warn] View Couchbase.CouchbaseViewHandler was mapped to a dead node, failing.
[SDKD(INFO) 66.24 cbsdk.sdkd.remote remote.py:263] [Couchbase.CouchbaseViewHandler|Warn] View Couchbase.CouchbaseViewHandler was mapped to a dead node, failing.
[SDKD(INFO) 66.24 cbsdk.sdkd.remote remote.py:263] [Couchbase.CouchbaseViewHandler|Warn] View Couchbase.CouchbaseViewHandler was mapped to a dead node, failing.
[SDKD(INFO) 66.24 cbsdk.sdkd.remote remote.py:263] [Couchbase.CouchbaseViewHandler|Warn] View Couchbase.CouchbaseViewHandler was mapped to a dead node, failing.
[SDKD(INFO) 66.24 cbsdk.sdkd.remote remote.py:263] [Couchbase.CouchbaseViewHandler|Warn] View Couchbase.CouchbaseViewHandler was mapped to a dead node, failing.
[SDKD(INFO) 66.82 cbsdk.sdkd.remote remote.py:263] [Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl|Error] Could not init pool. System.NullReferenceException Object reference not set to an instance of an object. at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.CreateSocket() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 279
[SDKD(INFO) 66.82 cbsdk.sdkd.remote remote.py:263] at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.InitPool() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 257
[SDKD(INFO) 66.91 cbsdk.sdkd.remote remote.py:263] [Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl|Error] Could not init pool. System.NullReferenceException Object reference not set to an instance of an object. at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.CreateSocket() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 279
[SDKD(INFO) 66.91 cbsdk.sdkd.remote remote.py:263] at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.InitPool() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 257
[SDKD(INFO) 67.53 cbsdk.sdkd.remote remote.py:263] [Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl|Error] Could not init pool. System.NullReferenceException Object reference not set to an instance of an object. at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.CreateSocket() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 279
[SDKD(INFO) 67.53 cbsdk.sdkd.remote remote.py:263] at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.InitPool() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 257
[SDKD(INFO) 67.76 cbsdk.sdkd.remote remote.py:263] [Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl|Error] Could not init pool. System.NullReferenceException Object reference not set to an instance of an object. at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.CreateSocket() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 279
[SDKD(INFO) 67.76 cbsdk.sdkd.remote remote.py:263] at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.InitPool() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 257
[SDKD(INFO) 67.76 cbsdk.sdkd.remote remote.py:263] [Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl|Error] Could not init pool. System.NullReferenceException Object reference not set to an instance of an object. at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.CreateSocket() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 279
[SDKD(INFO) 67.76 cbsdk.sdkd.remote remote.py:263] at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.InitPool() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 257
[SDKD(INFO) 68.06 cbsdk.sdkd.remote remote.py:263] [Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl|Error] Could not init pool. System.NullReferenceException Object reference not set to an instance of an object. at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.CreateSocket() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 279
[SDKD(INFO) 68.06 cbsdk.sdkd.remote remote.py:263] at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.InitPool() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 257
[SDKD(INFO) 70.01 cbsdk.sdkd.remote remote.py:263] [Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl|Error] Could not init pool. System.NullReferenceException Object reference not set to an instance of an object. at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.CreateSocket() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 279
[SDKD(INFO) 70.01 cbsdk.sdkd.remote remote.py:263] at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.InitPool() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 257
[SDKD(INFO) 70.01 cbsdk.sdkd.remote remote.py:263] [Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl|Error] Could not init pool. System.NullReferenceException Object reference not set to an instance of an object. at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.CreateSocket() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 279
[SDKD(INFO) 70.01 cbsdk.sdkd.remote remote.py:263] at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.InitPool() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 257
[SDKD(INFO) 70.02 cbsdk.sdkd.remote remote.py:263] [Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl|Error] Could not init pool. System.NullReferenceException Object reference not set to an instance of an object. at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.CreateSocket() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 279
[SDKD(INFO) 70.02 cbsdk.sdkd.remote remote.py:263] at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.InitPool() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 257
[SDKD(INFO) 70.07 cbsdk.sdkd.remote remote.py:263] [Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl|Error] Could not init pool. System.NullReferenceException Object reference not set to an instance of an object. at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.CreateSocket() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 279
[SDKD(INFO) 70.07 cbsdk.sdkd.remote remote.py:263] at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.InitPool() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 257
[SDKD(INFO) 70.07 cbsdk.sdkd.remote remote.py:263] [Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl|Error] Could not init pool. System.NullReferenceException Object reference not set to an instance of an object. at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.CreateSocket() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 279
[SDKD(INFO) 70.07 cbsdk.sdkd.remote remote.py:263] at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.InitPool() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 257
[SDKD(INFO) 70.20 cbsdk.sdkd.remote remote.py:263] [Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl|Error] Could not init pool. System.NullReferenceException Object reference not set to an instance of an object. at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.CreateSocket() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 279
[SDKD(INFO) 70.20 cbsdk.sdkd.remote remote.py:263] at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.InitPool() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 257
[SDKD(INFO) 70.20 cbsdk.sdkd.remote remote.py:263] [Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl|Error] Could not init pool. System.NullReferenceException Object reference not set to an instance of an object. at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.CreateSocket() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 279
[SDKD(INFO) 70.20 cbsdk.sdkd.remote remote.py:263] at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.InitPool() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 257
[SDKD(INFO) 70.22 cbsdk.sdkd.remote remote.py:263] [Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl|Error] Could not init pool. System.NullReferenceException Object reference not set to an instance of an object. at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.CreateSocket() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 279
[SDKD(INFO) 70.22 cbsdk.sdkd.remote remote.py:263] at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.InitPool() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 257
[SDKD(INFO) 70.22 cbsdk.sdkd.remote remote.py:263] [Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl|Error] Could not init pool. System.NullReferenceException Object reference not set to an instance of an object. at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.CreateSocket() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 279
[SDKD(INFO) 70.22 cbsdk.sdkd.remote remote.py:263] at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.InitPool() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 257
[SDKD(INFO) 70.22 cbsdk.sdkd.remote remote.py:263] [Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl|Error] Could not init pool. System.NullReferenceException Object reference not set to an instance of an object. at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.CreateSocket() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 279
[SDKD(INFO) 70.22 cbsdk.sdkd.remote remote.py:263] at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.InitPool() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 257
[SDKD(INFO) 70.23 cbsdk.sdkd.remote remote.py:263] [Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl|Error] Could not init pool. System.NullReferenceException Object reference not set to an instance of an object. at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.CreateSocket() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 279
[SDKD(INFO) 70.23 cbsdk.sdkd.remote remote.py:263] at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.InitPool() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 257
[SDKD(INFO) 70.28 cbsdk.sdkd.remote remote.py:263] [Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl|Error] Could not init pool. System.NullReferenceException Object reference not set to an instance of an object. at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.CreateSocket() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 279
[SDKD(INFO) 70.28 cbsdk.sdkd.remote remote.py:263] at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.InitPool() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 257
[SDKD(INFO) 70.82 cbsdk.sdkd.remote remote.py:263] [Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl|Error] Could not init pool. System.NullReferenceException Object reference not set to an instance of an object. at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.CreateSocket() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 279
[SDKD(INFO) 70.82 cbsdk.sdkd.remote remote.py:263] at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.InitPool() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 257
[SDKD(INFO) 70.84 cbsdk.sdkd.remote remote.py:263] [Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl|Error] Could not init pool. System.NullReferenceException Object reference not set to an instance of an object. at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.CreateSocket() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 279
[SDKD(INFO) 70.84 cbsdk.sdkd.remote remote.py:263] at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.InitPool() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 257
[SDKD(INFO) 70.87 cbsdk.sdkd.remote remote.py:263] [Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl|Error] Could not init pool. System.NullReferenceException Object reference not set to an instance of an object. at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.CreateSocket() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 279
[SDKD(INFO) 70.87 cbsdk.sdkd.remote remote.py:263] at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.InitPool() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 257
[SDKD(INFO) 71.16 cbsdk.sdkd.remote remote.py:263] [Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl|Error] Could not init pool. System.NullReferenceException Object reference not set to an instance of an object. at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.CreateSocket() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 279
[SDKD(INFO) 71.16 cbsdk.sdkd.remote remote.py:263] at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.InitPool() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 257
[SDKD(INFO) 72.13 cbsdk.sdkd.remote remote.py:263] [Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl|Error] Could not init pool. System.NullReferenceException Object reference not set to an instance of an object. at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.CreateSocket() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 279
[SDKD(INFO) 72.13 cbsdk.sdkd.remote remote.py:263] at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.InitPool() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 257
[SDKD(INFO) 72.32 cbsdk.sdkd.remote remote.py:263] [Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl|Error] Could not init pool. System.NullReferenceException Object reference not set to an instance of an object. at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.CreateSocket() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 279
[SDKD(INFO) 72.32 cbsdk.sdkd.remote remote.py:263] at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.InitPool() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 257
[SDKD(INFO) 72.34 cbsdk.sdkd.remote remote.py:263] [Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl|Error] Could not init pool. System.NullReferenceException Object reference not set to an instance of an object. at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.CreateSocket() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 279
[SDKD(INFO) 72.34 cbsdk.sdkd.remote remote.py:263] at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.InitPool() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 257
[SDKD(INFO) 72.35 cbsdk.sdkd.remote remote.py:263] [Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl|Error] Could not init pool. System.NullReferenceException Object reference not set to an instance of an object. at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.CreateSocket() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 279
[SDKD(INFO) 72.35 cbsdk.sdkd.remote remote.py:263] at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.InitPool() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 257
[SDKD(INFO) 72.74 cbsdk.sdkd.remote remote.py:263] [Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl|Error] Could not init pool. System.NullReferenceException Object reference not set to an instance of an object. at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.CreateSocket() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 279
[SDKD(INFO) 72.74 cbsdk.sdkd.remote remote.py:263] at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.InitPool() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 257
[SDKD(INFO) 73.44 cbsdk.sdkd.remote remote.py:263] [Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl|Error] Could not init pool. System.NullReferenceException Object reference not set to an instance of an object. at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.CreateSocket() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 279
[SDKD(INFO) 73.44 cbsdk.sdkd.remote remote.py:263] at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.InitPool() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 257
[SDKD(INFO) 73.46 cbsdk.sdkd.remote remote.py:263] [Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl|Error] Could not init pool. System.NullReferenceException Object reference not set to an instance of an object. at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.CreateSocket() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 279
[SDKD(INFO) 73.46 cbsdk.sdkd.remote remote.py:263] at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.InitPool() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 257
[SDKD(INFO) 73.97 cbsdk.sdkd.remote remote.py:263] [Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl|Error] Could not init pool. System.NullReferenceException Object reference not set to an instance of an object. at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.CreateSocket() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 279
[SDKD(INFO) 73.97 cbsdk.sdkd.remote remote.py:263] at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.InitPool() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 257
[SDKD(INFO) 74.63 cbsdk.sdkd.remote remote.py:263] [Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl|Error] Could not init pool. System.NullReferenceException Object reference not set to an instance of an object. at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.CreateSocket() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 279
[SDKD(INFO) 74.63 cbsdk.sdkd.remote remote.py:263] at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.InitPool() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 257
[SDKD(INFO) 74.65 cbsdk.sdkd.remote remote.py:263] [Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl|Error] Could not init pool. System.NullReferenceException Object reference not set to an instance of an object. at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.CreateSocket() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 279
[SDKD(INFO) 74.65 cbsdk.sdkd.remote remote.py:263] at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.InitPool() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 257
[SDKD(INFO) 74.65 cbsdk.sdkd.remote remote.py:263] [Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl|Error] Could not init pool. System.NullReferenceException Object reference not set to an instance of an object. at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.CreateSocket() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 279
[SDKD(INFO) 74.65 cbsdk.sdkd.remote remote.py:263] at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.InitPool() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 257
[SDKD(INFO) 74.65 cbsdk.sdkd.remote remote.py:263] [Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl|Error] Could not init pool. System.NullReferenceException Object reference not set to an instance of an object. at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.CreateSocket() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 279
[SDKD(INFO) 74.65 cbsdk.sdkd.remote remote.py:263] at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.InitPool() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 257
[SDKD(INFO) 74.65 cbsdk.sdkd.remote remote.py:263] [Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl|Error] Could not init pool. System.NullReferenceException Object reference not set to an instance of an object. at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.CreateSocket() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 279
[SDKD(INFO) 74.65 cbsdk.sdkd.remote remote.py:263] at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.InitPool() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 257
[SDKD(INFO) 74.83 cbsdk.sdkd.remote remote.py:263] [Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl|Error] Could not init pool. System.NullReferenceException Object reference not set to an instance of an object. at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.CreateSocket() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 279
[SDKD(INFO) 74.83 cbsdk.sdkd.remote remote.py:263] at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.InitPool() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 257
[SDKD(INFO) 74.90 cbsdk.sdkd.remote remote.py:263] [Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl|Error] Could not init pool. System.NullReferenceException Object reference not set to an instance of an object. at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.CreateSocket() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 279
[SDKD(INFO) 74.90 cbsdk.sdkd.remote remote.py:263] at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.InitPool() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 257
[SDKD(INFO) 74.90 cbsdk.sdkd.remote remote.py:263] [Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl|Error] Could not init pool. System.NullReferenceException Object reference not set to an instance of an object. at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.CreateSocket() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 279
[SDKD(INFO) 74.90 cbsdk.sdkd.remote remote.py:263] at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.InitPool() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 257
[SDKD(INFO) 80.13 cbsdk.sdkd.remote remote.py:263] [Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl|Error] Could not init pool. System.NullReferenceException Object reference not set to an instance of an object. at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.CreateSocket() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 279
[SDKD(INFO) 80.13 cbsdk.sdkd.remote remote.py:263] at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.InitPool() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 257
[SDKD(INFO) 83.91 cbsdk.sdkd.remote remote.py:263] [Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl|Error] Could not init pool. System.NullReferenceException Object reference not set to an instance of an object. at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.CreateSocket() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 279
[SDKD(INFO) 83.91 cbsdk.sdkd.remote remote.py:263] at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.InitPool() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 257
[SDKD(INFO) 83.91 cbsdk.sdkd.remote remote.py:263] [Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl|Error] Could not init pool. System.NullReferenceException Object reference not set to an instance of an object. at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.CreateSocket() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 279
[SDKD(INFO) 83.91 cbsdk.sdkd.remote remote.py:263] at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.InitPool() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 257
[SDKD(INFO) 84.24 cbsdk.sdkd.remote remote.py:263] [Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl|Error] Could not init pool. System.NullReferenceException Object reference not set to an instance of an object. at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.CreateSocket() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 279
[SDKD(INFO) 84.24 cbsdk.sdkd.remote remote.py:263] at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.InitPool() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 257
[ACTION 85.48 cbsdk.scenario rebalance.py:213] Rebalance action complete
[ACTION 85.48 cbsdk.scenario base.py:50] Sleeping 5 seconds before collection
[SDKD(INFO) 88.21 cbsdk.sdkd.remote remote.py:263] [Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl|Error] Could not init pool. System.NullReferenceException Object reference not set to an instance of an object. at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.CreateSocket() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 279
[SDKD(INFO) 88.21 cbsdk.sdkd.remote remote.py:263] at Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl.InitPool() in c:\ncbc\lib\EnyimMemcached\Enyim.Caching\Memcached\MemcachedNode.cs:line 257
[DEBUG 90.48 cbsdk.driver driver.py:39] CANCEL:77 @2 {}
[DEBUG 90.51 cbsdk.driver driver.py:48] CANCEL:77 @2 (OK) {}
[DEBUG 90.51 cbsdk.driver driver.py:39] CANCEL:78 @3 {}
[SDKD(INFO) 90.51 cbsdk.sdkd.remote remote.py:263] [Sdkd.Control|Info] Cancelling command for Handle 2
[DEBUG 90.61 cbsdk.driver driver.py:48] CANCEL:78 @3 (OK) {}
[DEBUG 90.61 cbsdk.driver driver.py:39] CANCEL:79 @4 {}
[SDKD(INFO) 90.61 cbsdk.sdkd.remote remote.py:263] [Sdkd.Control|Info] Cancelling command for Handle 3
[DEBUG 90.63 cbsdk.driver driver.py:48] CANCEL:79 @4 (OK) {}
[DEBUG 90.63 cbsdk.driver driver.py:39] CANCEL:80 @5 {}
[SDKD(INFO) 90.64 cbsdk.sdkd.remote remote.py:263] [Sdkd.Control|Info] Cancelling command for Handle 4
[DEBUG 90.72 cbsdk.driver driver.py:48] CANCEL:80 @5 (OK) {}
[DEBUG 90.72 cbsdk.driver driver.py:39] CANCEL:81 @6 {}
[SDKD(INFO) 90.72 cbsdk.sdkd.remote remote.py:263] [Sdkd.Control|Info] Cancelling command for Handle 5
[DEBUG 90.76 cbsdk.driver driver.py:48] CANCEL:81 @6 (OK) {}
[DEBUG 90.76 cbsdk.driver driver.py:39] CANCEL:82 @7 {}
[SDKD(INFO) 90.82 cbsdk.sdkd.remote remote.py:263] [Sdkd.Control|Info] Cancelling command for Handle 6
[DEBUG 90.88 cbsdk.driver driver.py:48] CANCEL:82 @7 (OK) {}
[DEBUG 90.88 cbsdk.driver driver.py:39] CANCEL:83 @8 {}
[SDKD(INFO) 90.89 cbsdk.sdkd.remote remote.py:263] [Sdkd.Control|Info] Cancelling command for Handle 7
[DEBUG 90.97 cbsdk.driver driver.py:48] CANCEL:83 @8 (OK) {}
[DEBUG 90.97 cbsdk.driver driver.py:39] CANCEL:84 @9 {}
[SDKD(INFO) 91.02 cbsdk.sdkd.remote remote.py:263] [Sdkd.Control|Info] Cancelling command for Handle 8
[DEBUG 91.17 cbsdk.driver driver.py:48] CANCEL:84 @9 (OK) {}
[DEBUG 91.17 cbsdk.driver driver.py:39] CANCEL:85 @10 {}
[SDKD(INFO) 91.19 cbsdk.sdkd.remote remote.py:263] [Sdkd.Control|Info] Cancelling command for Handle 9
[DEBUG 91.22 cbsdk.driver driver.py:48] CANCEL:85 @10 (OK) {}
[DEBUG 91.22 cbsdk.driver driver.py:39] CANCEL:86 @11 {}
[SDKD(INFO) 91.24 cbsdk.sdkd.remote remote.py:263] [Sdkd.Control|Info] Cancelling command for Handle 10
[DEBUG 91.30 cbsdk.driver driver.py:48] CANCEL:86 @11 (OK) {}
[SDKD(INFO) 91.32 cbsdk.sdkd.remote remote.py:263] [Sdkd.Control|Info] Cancelling command for Handle 11
[DEBUG 91.78 cbsdk.driver driver.py:48] CB_VIEW_QUERY:14 @2 (OK) {u'Timings': '< Timings Truncated >', u'Summary': {u'0': 507}}
[DEBUG 92.01 cbsdk.driver driver.py:48] CB_VIEW_QUERY:15 @3 (OK) {u'Timings': '< Timings Truncated >', u'Summary': {u'0': 709}}
[DEBUG 92.01 cbsdk.driver driver.py:48] CB_VIEW_QUERY:16 @4 (OK) {u'Timings': '< Timings Truncated >', u'Summary': {u'0': 608}}
[SDKD(INFO) 128.53 cbsdk.sdkd.remote remote.py:263] [Sdkd.ViewQuery|Warn] Unrecognized error System.Net.WebException The operation has timed out at Couchbase.HammockHttpClient.HammockResponseWrapper.ExecuteWith(RestClient client) in c:\ncbc\src\Couchbase\HammockHttpClient.cs:line 141
[SDKD(INFO) 128.53 cbsdk.sdkd.remote remote.py:263] at Couchbase.HammockHttpClient.HammockRequestWrapper.Couchbase.IHttpRequest.GetResponse() in c:\ncbc\src\Couchbase\HammockHttpClient.cs:line 112
[SDKD(INFO) 128.54 cbsdk.sdkd.remote remote.py:263] at Couchbase.CouchbaseViewHandler.GetResponse(IDictionary`2 viewParams) in c:\ncbc\src\Couchbase\CouchbaseViewHandler.cs:line 144
[SDKD(INFO) 128.54 cbsdk.sdkd.remote remote.py:263] at Couchbase.CouchbaseViewHandler.<TransformResults>d__0`1.MoveNext() in c:\ncbc\src\Couchbase\CouchbaseViewHandler.cs:line 38
[SDKD(INFO) 128.54 cbsdk.sdkd.remote remote.py:263] at Sdkd.Views.ViewCommand.Run() in c:\Users\Administrator\Documents\GitHub\sdkd-net\src\Sdkd\Views\ViewCommand.cs:line 219
[SDKD(INFO) 139.64 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 139.64 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 139.64 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 139.66 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 140.92 cbsdk.sdkd.remote remote.py:263] [Sdkd.ViewQuery|Warn] Unrecognized error System.Net.WebException The operation has timed out at Couchbase.HammockHttpClient.HammockResponseWrapper.ExecuteWith(RestClient client) in c:\ncbc\src\Couchbase\HammockHttpClient.cs:line 141
[SDKD(INFO) 140.92 cbsdk.sdkd.remote remote.py:263] at Couchbase.HammockHttpClient.HammockRequestWrapper.Couchbase.IHttpRequest.GetResponse() in c:\ncbc\src\Couchbase\HammockHttpClient.cs:line 112
[SDKD(INFO) 140.92 cbsdk.sdkd.remote remote.py:263] at Couchbase.CouchbaseViewHandler.GetResponse(IDictionary`2 viewParams) in c:\ncbc\src\Couchbase\CouchbaseViewHandler.cs:line 144
[SDKD(INFO) 140.92 cbsdk.sdkd.remote remote.py:263] at Couchbase.CouchbaseViewHandler.<TransformResults>d__0`1.MoveNext() in c:\ncbc\src\Couchbase\CouchbaseViewHandler.cs:line 38
[SDKD(INFO) 140.92 cbsdk.sdkd.remote remote.py:263] at Sdkd.Views.ViewCommand.Run() in c:\Users\Administrator\Documents\GitHub\sdkd-net\src\Sdkd\Views\ViewCommand.cs:line 219
[SDKD(INFO) 142.35 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 142.36 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 142.38 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 142.41 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 142.46 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 142.49 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 142.55 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 142.57 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 142.62 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 142.63 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 142.66 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 142.68 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 142.71 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 142.75 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 142.77 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 142.79 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 142.82 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 142.87 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 142.91 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 142.94 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 142.99 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 143.02 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 143.05 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 143.10 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 143.13 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 143.19 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 143.25 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 143.30 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 143.35 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 143.36 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 143.39 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 143.43 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 143.47 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 143.51 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 143.53 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 143.63 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 143.68 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 143.69 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 143.71 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 143.73 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 143.77 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 143.80 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 143.85 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 143.90 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 143.94 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 143.96 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 143.99 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 144.04 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 144.04 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 144.05 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 144.10 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 144.14 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 144.17 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 144.20 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 144.23 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 144.28 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 144.30 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 144.32 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 144.34 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 144.37 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 144.39 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 144.43 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 144.49 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 144.52 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 144.54 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 144.57 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 144.62 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 144.63 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 144.65 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 144.66 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 144.72 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 144.76 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 144.80 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 144.82 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 144.84 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 144.89 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 144.91 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 144.93 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 144.98 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 144.98 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 145.01 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 145.03 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 145.07 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 145.09 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 145.11 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 145.13 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 145.18 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 145.18 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 145.21 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 145.22 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 145.24 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 145.29 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 145.30 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 145.31 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 145.35 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 145.38 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 145.40 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 145.43 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 145.49 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 145.51 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 145.55 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 145.58 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 145.62 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 145.64 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 145.66 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 145.68 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 145.72 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 145.76 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 145.81 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 145.84 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 145.90 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 145.94 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 145.96 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 145.97 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 146.01 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 146.06 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 146.09 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 146.12 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 146.15 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 146.18 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 146.21 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 146.24 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 146.27 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 146.27 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 146.32 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 146.36 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 146.39 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 146.44 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 146.46 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 146.50 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 146.52 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 146.54 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 146.58 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 146.63 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 146.68 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 146.70 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 146.79 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 146.82 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 146.84 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 146.85 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 146.88 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 146.91 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 146.94 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 146.97 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 147.04 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 147.08 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 147.13 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 147.16 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 147.21 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 147.22 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 147.24 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 147.25 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 147.32 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 147.37 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 147.40 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 147.44 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 147.51 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 147.55 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 147.57 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 147.60 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 147.61 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 147.68 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 147.71 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 147.73 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 147.80 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 147.91 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 147.98 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 148.02 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 148.05 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 148.07 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 148.08 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 148.12 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 148.18 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 148.22 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 148.24 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 148.27 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 148.30 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 148.32 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 148.33 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 148.33 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 148.41 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 148.43 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 148.44 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 148.46 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 148.54 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 148.56 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 148.57 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 148.62 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 148.63 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 148.68 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 148.72 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 148.76 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 148.79 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 148.83 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 148.84 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 148.86 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 148.87 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 148.91 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 148.96 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 148.98 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 149.03 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 149.09 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 149.13 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 149.13 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 149.17 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 149.22 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 149.23 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 149.25 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 149.30 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 149.34 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 149.36 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 149.42 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 149.45 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 149.50 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 149.53 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 149.55 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 149.56 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 149.61 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 149.63 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 149.64 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 149.68 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 149.72 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 149.75 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 149.76 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 149.79 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 149.83 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 149.84 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 149.89 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 149.94 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 149.99 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 150.03 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 150.06 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 150.11 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 150.14 cbsdk.sdkd.remote remote.py:263] [Couchbase.HammockHttpClient|Warn] Retrying
[SDKD(INFO) 150.17 cbsdk.sdkd.remote remote.py:263] [Sdkd.Main|Fatal] Requested suppression of exception dialog box..
[SDKD(INFO) 150.22 cbsdk.sdkd.remote remote.py:263] [Sdkd.Main|Fatal] Unhandled Exception System.NullReferenceException Object reference not set to an instance of an object. at Hammock.RestClient.CompleteWithQuery(WebQuery query, RestRequest request, RestCallback callback, WebQueryAsyncResult result) in C:\Users\Daniel\Desktop\Dropbox\_7_Source_Code\_1_Projects\hammock\src\net35\Hammock\RestClient.cs:line 1797
[SDKD(INFO) 150.22 cbsdk.sdkd.remote remote.py:263] at Hammock.RestClient.<>c__DisplayClass18.<BeginRequestImpl>b__15(Object sender, WebQueryResponseEventArgs args) in C:\Users\Daniel\Desktop\Dropbox\_7_Source_Code\_1_Projects\hammock\src\net35\Hammock\RestClient.cs:line 1190
[SDKD(INFO) 150.22 cbsdk.sdkd.remote remote.py:263] at System.EventHandler`1.Invoke(Object sender, TEventArgs e)
[SDKD(INFO) 150.22 cbsdk.sdkd.remote remote.py:263] at Hammock.Web.WebQuery.OnQueryResponse(WebQueryResponseEventArgs args) in C:\Users\Daniel\Desktop\Dropbox\_7_Source_Code\_1_Projects\hammock\src\net35\Hammock\Web\WebQuery.cs:line 991
[SDKD(INFO) 150.22 cbsdk.sdkd.remote remote.py:263] at Hammock.Web.WebQuery.HandleWebException(WebException exception) in C:\Users\Daniel\Desktop\Dropbox\_7_Source_Code\_1_Projects\hammock\src\net35\Hammock\Web\WebQuery.cs:line 831
[SDKD(INFO) 150.22 cbsdk.sdkd.remote remote.py:263] at Hammock.Web.WebQuery.GetAsyncResponseCallback(IAsyncResult asyncResult) in C:\Users\Daniel\Desktop\Dropbox\_7_Source_Code\_1_Projects\hammock\src\net35\Hammock\Web\WebQuery.Async.cs:line 396
[SDKD(INFO) 150.22 cbsdk.sdkd.remote remote.py:263] at System.Net.LazyAsyncResult.Complete(IntPtr userToken)
[SDKD(INFO) 150.23 cbsdk.sdkd.remote remote.py:263] at System.Net.ContextAwareResult.CompleteCallback(Object state)
[SDKD(INFO) 150.23 cbsdk.sdkd.remote remote.py:263] at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
[SDKD(INFO) 150.23 cbsdk.sdkd.remote remote.py:263] at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
[SDKD(INFO) 150.23 cbsdk.sdkd.remote remote.py:263] at System.Net.ContextAwareResult.Complete(IntPtr userToken)
[SDKD(INFO) 150.23 cbsdk.sdkd.remote remote.py:263] at System.Net.LazyAsyncResult.ProtectedInvokeCallback(Object result, IntPtr userToken)
[SDKD(INFO) 150.23 cbsdk.sdkd.remote remote.py:263] at System.Net.HttpWebRequest.SetResponse(Exception E)
[SDKD(INFO) 150.23 cbsdk.sdkd.remote remote.py:263] at System.Net.HttpWebRequest.Abort(Exception exception, Int32 abortState)
[SDKD(INFO) 150.23 cbsdk.sdkd.remote remote.py:263] at System.Net.HttpWebRequest.Abort()
[SDKD(INFO) 150.23 cbsdk.sdkd.remote remote.py:263] at Hammock.Web.WebQuery.TimedOutCallback(Object state, Boolean timedOut) in C:\Users\Daniel\Desktop\Dropbox\_7_Source_Code\_1_Projects\hammock\src\net35\Hammock\Web\WebQuery.Async.cs:line 267
[SDKD(INFO) 150.23 cbsdk.sdkd.remote remote.py:263] at System.Threading._ThreadPoolWaitOrTimerCallback.WaitOrTimerCallback_Context(Object state, Boolean timedOut)
[SDKD(INFO) 150.23 cbsdk.sdkd.remote remote.py:263] at System.Threading._ThreadPoolWaitOrTimerCallback.WaitOrTimerCallback_Context_t(Object state)
[SDKD(INFO) 150.23 cbsdk.sdkd.remote remote.py:263] at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
[SDKD(INFO) 150.23 cbsdk.sdkd.remote remote.py:263] at System.Threading._ThreadPoolWaitOrTimerCallback.PerformWaitOrTimerCallback(Object state, Boolean timedOut)
[SDKD(INFO) 150.23 cbsdk.sdkd.remote remote.py:263] [Sdkd.Main|Fatal] Will now exit..


 Comments   
Comment by Mark Nunberg [ 06/Dec/12 ]
I also get this when a node is being shut down
Comment by Matt Ingenthron [ 06/Dec/12 ]
Setting this to 1.2 for now, but let's chat about this in the morning John. Thanks.
Comment by John Zablocki [ 13/Dec/12 ]
Mark, you can use the attached client file and dll to test whether a different provider handles better the failover scenario.
Comment by John Zablocki [ 13/Dec/12 ]
And for config:

var config = new CouchbaseClientConfiguration();
config.Bucket = "beer-sample";
config.BucketPassword = "";
config.Urls.Add(new Uri("http://localhost:8091/pools"));
config.HttpClientFactory = new RestSharpHttpClientFactory();

//Quick test of Store/Get operations
var client = new CouchbaseClient(config);
Comment by Mark Nunberg [ 14/Dec/12 ]
Running them now. It took me about an hour to figure out how to build it; a git branch or commit would be helpful in the future :)
Comment by Mark Nunberg [ 14/Dec/12 ]
Reports are looking good so far. However I'm still seeing inconclusive results for some tests where they just 'hang' -- is there a specific timeout that we have somewhere --

I'll run the tests a bit longer now (specifically, at least 90 seconds after rebalance/failover/whatever) - I should expect everything to recover to normal levels by then; right?
Comment by Mark Nunberg [ 14/Dec/12 ]
Passes all tests. Nice work!

- This version is much better
Comment by John Zablocki [ 14/Dec/12 ]
I will fix up the code and add this as the default, leaving Hammock as an option so that it doesn't break anyone.
Comment by John Zablocki [ 10/Jan/13 ]
Attached to this case is a signed, pre-release build of 1.2.1.
Comment by Saran Kumar [ 28/Jan/13 ]
Hi John/Mark,

As mentioned by Hari in CBSE-304, i have provided Couchbase-Net-Client-1.2.1.zip to the customer(Hobsons). After testing, he is stating that the issue is not fixed and the code fails the same exact way as before. Could you please look into this.

Thanks,
Saran


Comment by Mark Nunberg [ 28/Jan/13 ]
This issue does not seem to have anything to do with what is listed in CBSE-304. This issue is specifically about cluster changes during view operations; the issue mentioned in CBSE-304 seems to deal with providing CAS inside an arithmetic operation..
Comment by John Zablocki [ 28/Jan/13 ]
This is an unrelated fix.
Comment by John Zablocki [ 05/Feb/13 ]
Released



[NCBC-197] When 0 bytes received on socket, IO Exception thrown with message "?" Created: 08/Jan/13  Updated: 05/Feb/13  Resolved: 05/Feb/13

Status: Closed
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: 1.2.0
Fix Version/s: 1.2.1

Type: Improvement Priority: Major
Reporter: John Zablocki Assignee: John Zablocki
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Comments   
Comment by John Zablocki [ 05/Feb/13 ]
Released



[NCBC-165] GetView doesn't return an exception if the view doesn't exist. Created: 26/Nov/12  Updated: 05/Feb/13  Resolved: 05/Feb/13

Status: Closed
Project: Couchbase .NET client library
Component/s: library
Affects Version/s: None
Fix Version/s: 1.2.1

Type: Bug Priority: Major
Reporter: Kyle Sama Assignee: John Zablocki
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment: Visual Studio 2012, .net Client, couchbase 2.0,
win7/x64


 Description   
When you call var result = _couchClient.GetView(<etc.>), there is no exception thrown when the view does not exist. The program will only throw an exception when it attempts to access the data, ie: result.Count() will throw an exception.

 Comments   
Comment by John Zablocki [ 26/Dec/12 ]
The view isn't queried until the IEnumerable is actually iterated over. Therefore when you call GetView, there's no way to know that the view doesn't exist.

I will look into catching the 400 error and throwing a more meaningful exception.
Comment by John Zablocki [ 18/Jan/13 ]
Baking better exceptions into the view reading process and providing a CheckExists method.
Comment by John Zablocki [ 05/Feb/13 ]
Released



[NCBC-195] NRE when executing view query on authenticated bucket without proper credentials Created: 08/Jan/13  Updated: 05/Feb/13  Resolved: 05/Feb/13

Status: Closed
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: 1.2.0
Fix Version/s: 1.2.1

Type: Bug Priority: Major
Reporter: John Zablocki Assignee: John Zablocki
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Comments   
Comment by John Zablocki [ 05/Feb/13 ]
Released



[NCBC-220] Error handling documentation Created: 05/Feb/13  Updated: 05/Feb/13

Status: Open
Project: Couchbase .NET client library
Component/s: docs
Affects Version/s: 1.2.0
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: Perry Krug Assignee: John Zablocki
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Please create some documentation specifying possible error/failures to operations, what they "look" like in the logs/exceptions/stack traces and what our recommendation is on how to handle them.

i.e. tmp_oom, timeouts (connection/operation/java-internal/etc), "get miss" (it's technically a failure, let's make it overly obvious what it means), CAS failure, add() failure, replace() failure,

Some of this should be covered in the API reference, but this bug is specifically for a single page where this information is aggregated that a customer/user could read about how to handle errors.



[NCBC-218] Cannot build couchbase-net-client solution Created: 04/Feb/13  Updated: 04/Feb/13  Resolved: 04/Feb/13

Status: Closed
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Critical
Reporter: Saakshi Manocha Assignee: Saakshi Manocha
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Take latest code from Git for couchbase-net-client.
Build the solution.

Error:
'Couchbase.IView<Couchbase.IViewRow>' does not contain a definition for 'CheckExists' and no extension method 'CheckExists' accepting a first argument of type 'Couchbase.IView<Couchbase.IViewRow>' could be found (are you missing a using directive or an assembly reference?)

Error Source:
couchbase-net-client\src\Couchbase.Tests\CouchbaseClientViewTests.cs 68 22 Couchbase.Tests


 Comments   
Comment by John Zablocki [ 04/Feb/13 ]
http://review.couchbase.org/#/c/24387/2
Comment by Saakshi Manocha [ 04/Feb/13 ]
Verified and tested code submitted in Gerrit. Issue is fixed now. Thanks!



[NCBC-216] customer get error after set document in c# and read with Created: 03/Feb/13  Updated: 04/Feb/13  Resolved: 04/Feb/13

Status: Closed
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Ilan Katz Assignee: John Zablocki
Resolution: Incomplete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified




[NCBC-210] .NET Client is throwing NullReferenceExceptions (CBSE-341) Created: 25/Jan/13  Updated: 30/Jan/13  Resolved: 30/Jan/13

Status: Closed
Project: Couchbase .NET client library
Component/s: library
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Saakshi Manocha Assignee: Saakshi Manocha
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File CouchbaseClientNullReferenceCrash.rar    

 Description   
Issue is raised by a customer in ticket CBSE-341 (http://www.couchbase.com/issues/browse/CBSE-341), the details are mentioned in the ticket itself.

Following are the observations related to the issue:

--> when we create a client with bucket which doesn't exist, the error message should be more appropriate like "Bucket does not exist" and the code should simply exit with a false status. Currently it throws an exception and the error message that comes is "Object reference not set to an instance of an object.".

Error source : Couchbase.CouchbasePool.Enyim.Caching.Memcached.IServerPool.Locate(String key)
                       Couchbase.CouchbaseClient.PerformStore(StoreMode mode, String key, Object value, UInt32 expires, UInt64& cas, Int32& statusCode)
                       Enyim.Caching.MemcachedClient.Store(StoreMode mode, String key, Object value)
May be we need to add some condition that checks whether node (returned from Locate()) in null or not. If null, it should not proceed further to perform store operation. It should return apt message and simply exit with false status.

--> Rebalance operation takes quite some time. During this operation, the server nodes may become unavailable for sometime or even get removed from the cluster and hence the bucket is also not available. Exception is thrown "Object reference not set to an instance of an object)". Error source same as above : Couchbase.CouchbasePool.Enyim.Caching.Memcached.IServerPool.Locate(String key)


--> Refer to the attached sample code, I used my cluster which has following server nodes:
10.3.3.206
10.3.121.134
10.3.121.135
10.3.121.136
In the code Program.cs, use the bucket name that does not exist, the code will throw the exception.
Next use the correct bucket name but manually fail over a node & start rebalance. It will throw the exception.


 Comments   
Comment by Saakshi Manocha [ 25/Jan/13 ]
sample code to reproduce issue
Comment by John Zablocki [ 30/Jan/13 ]
http://www.couchbase.com/issues/browse/NCBC-192



[NCBC-213] .NET docs include "Java Troubleshooting" section Created: 28/Jan/13  Updated: 29/Jan/13  Resolved: 29/Jan/13

Status: Closed
Project: Couchbase .NET client library
Component/s: docs
Affects Version/s: 1.2.0
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Tim Smith Assignee: Karen Zeller
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment: https://www.couchbase.com/docs/couchbase-sdk-net-1.2/api-reference-troubleshooting.html


 Description   
The .NET docs include Java-specific information:


https://www.couchbase.com/docs/couchbase-sdk-net-1.2/api-reference-troubleshooting.html

Chapter 9. Java Troubleshooting

Table of Contents

9.1. Configuring Logging
9.2. Handling Timeouts
9.3. Timing-out and Blocking
9.4. Bulk Load and Exponential Backoff
9.5. Retrying After Receiving a Temporary Failure


All of that info is Java-specific. Quite confusing when reading the .NET SDK docs.



 Comments   
Comment by John Zablocki [ 28/Jan/13 ]
Not sure how this could be... Doesn't seem to be in the index.
Comment by Karen Zeller [ 28/Jan/13 ]
This is really annoying. I had added your backoff example from the wiki to the .net chapter and somehow only an earlier addition has been committed (using Java chapter as template, but not the .net changes I added) Will fix.
Comment by Karen Zeller [ 28/Jan/13 ]
Fixed in this commit: https://github.com/couchbase/docs/commit/397d8bc8e3793f2c6226560921b60a8db9555ecd
Comment by Karen Zeller [ 28/Jan/13 ]
Fixed in this commit: https://github.com/couchbase/docs/commit/397d8bc8e3793f2c6226560921b60a8db9555ecd
Comment by Perry Krug [ 29/Jan/13 ]
While we're on it, the Java docs contain .NET troubleshooting: http://www.couchbase.com/docs/couchbase-sdk-java-1.1/api-reference-troubleshooting.html
Comment by Karen Zeller [ 29/Jan/13 ]
Oh nuts. The files got inverted. Next time I'm going to have the individual SDK owner (in this case, JohnZ) update their own guide with the code sample they have created. Too many directories and files across the guides.....
Comment by Karen Zeller [ 29/Jan/13 ]
Oh nuts. The files got inverted. Next time I'm going to have the individual SDK owner (in this case, JohnZ) update their own guide with the code sample they have created. Too many directories and files across the guides.....



[NCBC-206] Method links anchor to awkward section of page Created: 15/Jan/13  Updated: 28/Jan/13  Resolved: 28/Jan/13

Status: Resolved
Project: Couchbase .NET client library
Component/s: docs
Affects Version/s: 1.2.0
Fix Version/s: 1.2.1

Type: Bug Priority: Major
Reporter: Perry Krug Assignee: MC Brown
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
This link: http://www.couchbase.com/docs/couchbase-sdk-net-1.2/couchbase-sdk-net-retrieve-get.html#table-couchbase-sdk_net_executeget

Puts the anchor right on the API call, but cuts off the example above that introduces the ExecuteGet() method and the fact that it returns an IGetOperationResult. A customer would not know to scroll up a little bit.

I have a sneaky suspicion that many of the other method links are anchored in awkward positions as well and it would be great to review and fix as many as possible so they make sense to a user navigating the documentation.

 Comments   
Comment by John Zablocki [ 18/Jan/13 ]
Karen - is there an easy way to change the anchoring?
Comment by Karen Zeller [ 18/Jan/13 ]
This has to do with our XML to HTML conversion and the jump-links that it creates. This needs to go to MC.
Comment by MC Brown [ 21/Jan/13 ]
The links are automatically generated between the tables. The tables should be repositioned to be before any examples relating to their content, not afterwards.
Comment by MC Brown [ 24/Jan/13 ]
I've reposition the tables within the .NET SDK doc
Comment by Perry Krug [ 28/Jan/13 ]
I'm still seeing these anchors drop into the page below where the text related to the method begins...am I missing something?
Comment by MC Brown [ 28/Jan/13 ]
They link straight into the tables on that page, before the example, for me. Have you tried reloading?
Comment by Perry Krug [ 28/Jan/13 ]
Okay, now I see. I think the problem just "sort of" remains with the first anchor: http://www.couchbase.com/docs/couchbase-sdk-net-1.2/couchbase-sdk-net-retrieve-get.html#table-couchbase-sdk_net_get

it drops you into the page, a few lines below where the page starts. I guess it's not too big a deal, but looked to me like the problem still existed.

Is it considered at all confusing that the order of operations on the "Chapter 6" page doesn't match the order they are described on the 6.1 page?
Comment by MC Brown [ 28/Jan/13 ]
Hmm, well, the table at the head of the chapter should be sorted alphabetically (and it's not), but the latter page should order the content in terms of how they are used (there is no point discussing the CAS without the simpler get() for example.

The whole reason for the linking is that the order in the latter pages shouldn't matter because you don't have to scan for the right item - you are taken right to it.
Comment by Perry Krug [ 28/Jan/13 ]
Okay, well it seems that for multiple SDK docs, the first method is getting anchored to *after* it's introducing text...is that something we can fix?
Comment by MC Brown [ 28/Jan/13 ]
OK, post sorting fixed, now rebuilding.
Comment by MC Brown [ 28/Jan/13 ]
Fixed some additional areas where the text/tables are mismatched.



[NCBC-182] API summary links don't go anywhere Created: 14/Dec/12  Updated: 18/Jan/13  Resolved: 18/Jan/13

Status: Closed
Project: Couchbase .NET client library
Component/s: docs
Affects Version/s: 1.2.0
Fix Version/s: 1.2.1

Type: Bug Priority: Major
Reporter: Tim Smith Assignee: John Zablocki
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment: http://www.couchbase.com/docs/couchbase-sdk-net-1.2/api-reference-summary.html


 Description   
When I click on a link on the api-reference-summary.html page for about half of the methods, it doesn't go anywhere. The others do go to an appropriate sub-page. Something broken with the docs generation?

For example, currently the .Append() methods go to the right place, but the .ExecuteAppend() do not. It's not just the Execute* methods that are broken, though. I think this affects the 1.1 docs as well.

 Comments   
Comment by John Zablocki [ 10/Jan/13 ]
There is a pull request pending with updated docs for the missing Execute methods.
Comment by John Zablocki [ 18/Jan/13 ]
See NCBC-186



[NCBC-186] Links for Execute methods from API reference go nowhere Created: 19/Dec/12  Updated: 18/Jan/13  Resolved: 18/Jan/13

Status: Closed
Project: Couchbase .NET client library
Component/s: docs
Affects Version/s: 1.2.0
Fix Version/s: 1.2.1

Type: Bug Priority: Major
Reporter: Perry Krug Assignee: John Zablocki
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
http://www.couchbase.com/docs/couchbase-sdk-net-1.2/api-reference-summary.html

The "Executexxx" methods link back to this same page.

 Comments   
Comment by John Zablocki [ 10/Jan/13 ]
Docs updated. Pull request sent.
Comment by John Zablocki [ 18/Jan/13 ]
Docs merged and deployed.



[NCBC-79] Store mode example using replace is incorrect Created: 26/Jun/12  Updated: 18/Jan/13  Resolved: 18/Jan/13

Status: Closed
Project: Couchbase .NET client library
Component/s: docs
Affects Version/s: 1.1.6
Fix Version/s: 1.2.1

Type: Bug Priority: Major
Reporter: Perry Krug Assignee: John Zablocki
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
This page: http://www.couchbase.com/docs/couchbase-sdk-net-1.1/couchbase-sdk-net-retrieve-set.html#table-couchbase-sdk_net_executestore-expiresat

A couple things wrong:
-First, the example uses "Storemode.replace", yet the description says: Store a value using the specified key, whether the key already exists or not. Will overwrite a value if the given key/value already exists. (that's not what replace does)
-Second, according to the layout of the docs, "replace" should be an update operation, not a store operation. However, it is a "storemode" so there may need to be some cross referencing?
-Third, the parent page (http://www.couchbase.com/docs/couchbase-sdk-net-1.1/api-reference-set.html) lists the ExecuteStore methods out of order compared to how they are shown on the child page

 Comments   
Comment by John Zablocki [ 10/Jan/13 ]
Descriptions updated and pull request was sent. Not sure about the ordering since that's part of the merge process. I've ordered them correctly as far as I can tell, but will double check after merge and assign to docs team if that's not the case.
Comment by John Zablocki [ 18/Jan/13 ]
Docs merged and deployed.



[NCBC-144] CreateDesignDocument() exception Created: 21/Oct/12  Updated: 18/Jan/13  Resolved: 18/Jan/13

Status: Closed
Project: Couchbase .NET client library
Component/s: library
Affects Version/s: 1.2 Beta
Fix Version/s: 1.2.1

Type: Bug Priority: Major
Reporter: Perry Krug Assignee: Perry Krug
Resolution: Fixed Votes: 0
Labels: customer
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
On a Windows 7 x64 VM, single node cluster, Couchbase 2.0 beta, freshly downloaded and installed, I am getting the following exception:
System.Net.WebException was unhandled
  HResult=-2146233079
  Message=The remote server returned an error: (500) Internal Server Error.
  Source=System
  StackTrace:
       at System.Net.HttpWebRequest.GetResponse()
       at Couchbase.Helpers.HttpHelper.doRequest(Uri uri, String verb, String username, String password, String postData, String contentType) in c:\Cloud\Platform\PlatformSpike\Reference Assemblies\Couchbase\Couchbase\Helpers\HttpHelper.cs:line 77
       at Couchbase.Helpers.HttpHelper.Put(Uri uri, String username, String password, String postData, String contentType) in c:\Cloud\Platform\PlatformSpike\Reference Assemblies\Couchbase\Couchbase\Helpers\HttpHelper.cs:line 42
       at Couchbase.Management.CouchbaseCluster.CreateDesignDocument(String bucket, String name, String document) in c:\Cloud\Platform\PlatformSpike\Reference Assemblies\Couchbase\Couchbase\Management\CouchbaseCluster.cs:line 115
       at Platform.Data.Couchbase.Provisioning.CouchbaseProvisioning.CreateDesignDocument(String bucketName, String name, DesignDocument document) in c:\Cloud\Platform\PlatformSpike\Platform.Data.Couchbase.Provisioning\ProvisioningClient.cs:line 217
       at Platform.Data.Couchbase.Provisioning.CouchbaseProvisioning.Execute() in c:\Cloud\Platform\PlatformSpike\Platform.Data.Couchbase.Provisioning\ProvisioningClient.cs:line 56
       at CouchbaseUpdater.Program.Main(String[] args) in c:\Cloud\Platform\PlatformSpike\CouchbaseUpdater\Program.cs:line 26
  InnerException:
 
The server log contains the following entry, but I'm not sure if it is related:
Client-side error-report for user "admin" on node 'ns_1@192.168.54.178':
User-Agent:Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.2; WOW64; Trident/6.0)
Got unhandled error: Object doesn't support this action
At: http://192.168.54.178:8091/js/cells.js:64
Backtrace:
Function: collectBacktraceViaCaller
Args:
---------
Function: appOnError
Args:
"Object doesn't support this action"
"http://192.168.54.178:8091/js/cells.js"
64
30
---------
Function: (function () {throw e;})
Args:
---------
(repeated 1 times)
 
Those are the parameters to the doRequest() method:
uri = http://192.168.54.178:8092/tenants/_design/tenant_views
verb = PUT
contentType = application/json
username = admin
password = password
postData =
{
  "views": {
    "tenants_all": {
      "map": "function(doc,meta) \r\n{\r\n\tif (doc.Schema === \"tenant\") \r\n\t{ \r\n\t\temit(meta.id, null); \r\n\t} \r\n}"
    },
    "tenants_by_status": {
      "map": "function (doc,meta) \r\n{ \r\n\tif (doc.Schema === \"tenant\" && doc.Status) \r\n\t{ \r\n\t\temit(doc.Status, null); \r\n\t} \r\n}"
    },
    "tenants_by_user_application_instance": {
      "map": "function(doc,meta) \r\n{\r\n\tif (doc.Schema === \"tenant\" && doc.UserId && doc.TenantIdentifiers && identifier.Status === 1) \r\n\t{ \r\n\t\tfor (var i = 0; i < doc.TenantIdentifiers.length; i++) \r\n\t\t{\r\n\t\t\tvar identifier = doc.TenantIdentifiers[i];\r\n\t\t\tif (identifier.ApplicationInstanceId)\r\n\t\t\t{\r\n\t\t\t\temit([doc.UserId, identifier.ApplicationInstanceId], null); \r\n\t\t\t}\r\n\t\t}\r\n\t} \r\n}"
    }
  }
}
 
On the client I am using the compiled latest .NET source code from GitHub with no modifications.

 Comments   
Comment by John Zablocki [ 22/Oct/12 ]
Could we get a code snippet for the call that was made for this failure? I've used the client recently with Win7 64 and CBS Beta and haven't had any issues.

I have a partially completed demo app @ https://github.com/jzablocki/couchbase-beer.net/blob/master/src/CouchbaseBeersWeb/Models/WebRepositoryBase%271.cs#L140 that creates views.
Comment by John Zablocki [ 18/Jan/13 ]
Perry - haven't heard back on this issue. The 500 error was likely due to a bad view name or something similar. Closing this issue for now. The fix for NCBC-165 means better error handling.



[NCBC-1] error format changing Created: 27/Jul/11  Updated: 18/Jan/13  Resolved: 18/Jan/13

Status: Closed
Project: Couchbase .NET client library
Component/s: library
Affects Version/s: None
Fix Version/s: 1.2.1

Type: Bug Priority: Major
Reporter: Matt Ingenthron Assignee: John Zablocki
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
The error format is changing, need to ensure that's updated in the client.

Rough example format:

{"total_rows":0,"rows":[

],
"errors": [{"from":"127.0.0.1:5984","reason":"Design document `_design/testfoobar` missing in database `test_db_b`."},
{"from":"http://localhost:5984/_view_merge/","reason":"Design document `_design/testfoobar` missing in database `test_db_c`."}]}

 Comments   
Comment by Matt Ingenthron [ 28/Jul/11 ]
Here's a better example of the format. It changed slightly again.

{"total_rows":0,"rows":[
],
"errors":[
{"from":"local","reason":"Design document `_design/testfoobar` missing
in database `test_db_b`."},
{"from":"http://localhost:5984/_view_merge/","reason":"Design document
`_design/testfoobar` missing in database `test_db_c`."}
]}
Comment by Matt Ingenthron [ 05/Aug/11 ]
Was this handled in 0.9?
Comment by Matt Ingenthron [ 25/Aug/11 ]
The code needs to be inspected to verify this error handling.
Comment by John Zablocki [ 07/Dec/12 ]
Code is handling errors, but need unit test.
Comment by John Zablocki [ 18/Jan/13 ]
This error format is out of date. Current error format is below. As part of NCBC-165, error handling was cleaned up.

{"error":"error","reason":"Error opening view `does_not_exist`, from set `default`, design document `_design/cities`: {not_found,\n missing_named_view}"}

http://localhost:8092/default/_design/cities/_view/does_not_exist



[NCBC-181] Docs do not explain Execute* operation results Created: 14/Dec/12  Updated: 15/Jan/13  Resolved: 15/Jan/13

Status: Closed
Project: Couchbase .NET client library
Component/s: docs
Affects Version/s: 1.2.0
Fix Version/s: 1.2.1

Type: Bug Priority: Major
Reporter: Tim Smith Assignee: John Zablocki
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 24h
Time Spent: Not Specified
Original Estimate: 24h
Environment: http://www.couchbase.com/docs/couchbase-sdk-net-1.2/api-reference-summary.html


 Description   
I can't find any description of IOperationResult or any of its subclasses in the .NET docs.

I can find a pretty decent description in the wiki, here:

http://www.couchbase.com/wiki/display/couchbase/Couchbase+.NET+Client+Library#Couchbase.NETClientLibrary-%23HandlingFailureswiththeOperationResultsAPI

That info needs to be in the manual. Also, the return value for an operation is critical for understanding what it does. The API summaries elide the return value, and make it difficult to understand the function fully. It's worth the extra screen real estate to specify the return value in all the API summaries.

 Comments   
Comment by John Zablocki [ 10/Jan/13 ]
The API docs have been updated and I've added an appendix on how to work with the results. Pull request sent to docs team.
Comment by John Zablocki [ 15/Jan/13 ]
http://www.couchbase.com/docs/couchbase-sdk-net-1.2/couchbase-sdk-net-operation-results.html



[NCBC-205] Document how to use TTL with JSON extension methods Created: 15/Jan/13  Updated: 15/Jan/13  Resolved: 15/Jan/13

Status: Resolved
Project: Couchbase .NET client library
Component/s: docs
Affects Version/s: 1.2.0
Fix Version/s: 1.2.1

Type: Bug Priority: Major
Reporter: Perry Krug Assignee: John Zablocki
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Along with http://www.couchbase.com/issues/browse/NCBC-204, please include how to apply a TTL to a document being stored.

 Comments   
Comment by John Zablocki [ 15/Jan/13 ]
There aren't currently TTL extensions. I'm adding them to 1.2.1 and will update the appendix for that release.
Comment by Perry Krug [ 15/Jan/13 ]
Okay thanks, so is there a bug that this is a duplicate of?
Comment by John Zablocki [ 15/Jan/13 ]
Not for the documentation, but there is a bug for the new extensions - http://www.couchbase.com/issues/browse/NCBC-179.
Comment by Perry Krug [ 15/Jan/13 ]
http://www.couchbase.com/issues/browse/NCBC-179



[NCBC-203] Restructure .NET tests Created: 10/Dec/12  Updated: 14/Jan/13  Resolved: 25/Dec/12

Status: Resolved
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Mark Nunberg Assignee: Saakshi Manocha
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Zip Archive couchbase.tests.changedfiles.zip     Zip Archive Couchbase.Tests.zip    
Issue Links:
Dependency
depends on NCBC-177 Consolidate test options from App.config Resolved

 Description   
Eliminate redundant tests. I see there are some repetitive tests which differ only by 1-2 parameters. For example, we don't need individual functions for each scenario of observe, and it should be possible to abstract this all into a single function, with different tests just calling into that function with different parameters.

I recall that you brought this up as a concern before; now it's a task :)

 Comments   
Comment by Saakshi Manocha [ 11/Dec/12 ]
http://review.couchbase.org/#/c/23202/
Comment by Mark Nunberg [ 11/Dec/12 ]
I've sectioned out the previous bug into an NCBC issue. In general any changes to the SDKs themselves should be branched out into issues which touch those specific projects, with the SDKQE task tracking them.
Comment by Saakshi Manocha [ 18/Dec/12 ]
updated files attached for review :
couchbase.tests.changedfiles.zip
Comment by Saakshi Manocha [ 19/Dec/12 ]
please review:
http://review.couchbase.org/#/c/23430/
Comment by Saakshi Manocha [ 25/Dec/12 ]
Mark to review the changes updated in Gerrit
Comment by Saakshi Manocha [ 14/Jan/13 ]
moved this task from SDKQE project to NCBC, as per mail from Matt so that we can use NCBC in comment while submitting code in gerrit.
updated comment in gerrit and submitted a new patch set.,
please review http://review.couchbase.org/#/c/23604/
Comment by Matt Ingenthron [ 14/Jan/13 ]
Saakshi: it's not so much that this task needed to be moved, but an underlying NCBC enhancement issue needed to be created-- even one with just a one line summary of what's to be done.

NCBC tracks this product/project, so we should always be able to see the changes in a version via this issue tracker and cross reference that with the code changes.

Thanks!



[NCBC-200] code review Created: 10/Jan/13  Updated: 10/Jan/13  Resolved: 10/Jan/13

Status: Resolved
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major
Reporter: Saakshi Manocha Assignee: Saakshi Manocha
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
code review for NCBC-159, NCBC-172, NCBC-179, NCBC-195

 Comments   
Comment by Saakshi Manocha [ 10/Jan/13 ]
code review done, comments published on Gerrit



[NCBC-137] design document management is not in the documentation or API reference Created: 05/Oct/12  Updated: 08/Jan/13  Resolved: 08/Jan/13

Status: Closed
Project: Couchbase .NET client library
Component/s: docs
Affects Version/s: None
Fix Version/s: 1.2.1

Type: Bug Priority: Blocker
Reporter: Matt Ingenthron Assignee: John Zablocki
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Had reason to look up design document management from .NET earlier today and it seems to not be documented. This and all new features should be added to the API reference before release.

 Comments   
Comment by John Zablocki [ 08/Jan/13 ]
http://www.couchbase.com/docs/couchbase-sdk-net-1.2/couchbase-sdk-net-cluster-management.html
Comment by John Zablocki [ 08/Jan/13 ]
Merged into docs.



[NCBC-53] "Cas" should be capitalized Created: 04/May/12  Updated: 07/Jan/13  Resolved: 07/Jan/13

Status: Closed
Project: Couchbase .NET client library
Component/s: docs
Affects Version/s: None
Fix Version/s: 1.2.1

Type: Bug Priority: Major
Reporter: Perry Krug Assignee: John Zablocki
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Tiny nitpick I know, but it's always worth being as correct as possible.

Noticed it on this page (http://www.couchbase.com/develop/net/current) but it probably exists many places elsewhere.

"Cas" should be CAS...the only exception could be within the actual API/command itself if that's how it's spelled in the code.

 Comments   
Comment by John Zablocki [ 08/Aug/12 ]
Waiting for approval in CMS.
Comment by John Zablocki [ 08/Aug/12 ]
Also updated getting started and tutorial in the docs.
Comment by John Zablocki [ 07/Jan/13 ]
Docs updated.



[NCBC-193] Bug in .Net Documentation on Connection Parameters Created: 02/Jan/13  Updated: 04/Jan/13  Resolved: 04/Jan/13

Status: Resolved
Project: Couchbase .NET client library
Component/s: docs
Affects Version/s: 1.2.0
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Muthu Kumar Assignee: MC Brown
Resolution: Fixed Votes: 0
Labels: .net, client, documentation
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
The connection configuration here should point to pools than to pools/default @ http://www.couchbase.com/docs/couchbase-sdk-net-1.2/api-reference-connection.html . Please correct this documentation.

It is correct @ http://www.couchbase.com/docs/couchbase-sdk-net-1.2/couchbase-sdk-net-configuration.html

 Comments   
Comment by MC Brown [ 04/Jan/13 ]
Documentation has been fixed and is currently rebuilding



[NCBC-194] Review change : http://review.couchbase.org/#/c/23660/ Created: 04/Jan/13  Updated: 04/Jan/13  Resolved: 04/Jan/13

Status: Resolved
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Minor
Reporter: Saakshi Manocha Assignee: Saakshi Manocha
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Review change : http://review.couchbase.org/#/c/23660/

 Comments   
Comment by Saakshi Manocha [ 04/Jan/13 ]
review done, review comments posted in Gerrit



[NCBC-121] Null Reference Exception during rebalance Created: 17/Sep/12  Updated: 03/Jan/13  Resolved: 21/Nov/12

Status: Closed
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: 1.1.6
Fix Version/s: 1.2 Beta-2

Type: Bug Priority: Blocker
Reporter: Mark Nunberg Assignee: John Zablocki
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File net-bug.png    

 Description   
Happens during the rebalancing-out of two nodes.

Reproduce:

* Perform get/set operations continuously
* Rebalance out two nodes
poof!

I was using multiple client handles for this test.. it seems each of them got that error.

 Comments   
Comment by Farshid Ghods [ 17/Sep/12 ]
mark,

Just wondering if major is the right priority for this issue given that this happens during rebalancing
Do users tend to ignore one or two errors and are okay with retries for these type of errors
Comment by Mark Nunberg [ 17/Sep/12 ]
This causes a complete application crash.
Comment by Mark Nunberg [ 19/Sep/12 ]
I've patched up Enyim a bit so that it no longer crashes -- the problem being some apparent reentrancy and race condition issues when a node is dying.

I'll file a gerrit patch when I figure out how to use this thing on my windows box
Comment by Mark Nunberg [ 27/Sep/12 ]
Interim changeset is here
https://github.com/mnunberg/EnyimMemcached/commit/f2b161a0909badf7981e055605d3a20f9a5db4dd
Comment by Matt Ingenthron [ 04/Oct/12 ]
John, can you evaluate the severity of this? This has been a blocker for QE tests.
Comment by John Zablocki [ 23/Oct/12 ]
Merged Mark's code into our Enyim fork
Comment by John Zablocki [ 21/Nov/12 ]
Published



[NCBC-134] Failover on bootstrap node never recovers Created: 02/Oct/12  Updated: 03/Jan/13  Resolved: 21/Nov/12

Status: Closed
Project: Couchbase .NET client library
Component/s: library
Affects Version/s: 1.1.6
Fix Version/s: 1.2 Beta-2

Type: Bug Priority: Blocker
Reporter: Mark Nunberg Assignee: John Zablocki
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment: Server 2.0.

Attachments: Text File dotnet.log     Zip Archive dotnet-log.zip    

 Description   
When I fail over two nodes while performing operations, where one of them it the 'entry point' node (i.e. the one which is the source of the streaming API), it seems the client never recovers. It does not crash or provide an exception. Operations continue failing from the workload generator.

This is using a modified Enyim (see NCBC-121) without which I'm not even trying as it seems to crash my application during the slightest network issue.

 Comments   
Comment by Mark Nunberg [ 25/Oct/12 ]
I've attached the log file - it's rather large :)
Comment by John Zablocki [ 21/Nov/12 ]
Published



[NCBC-63] Support removing of bucket from client Created: 12/Jun/12  Updated: 03/Jan/13  Resolved: 05/Sep/12

Status: Closed
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: None
Fix Version/s: 1.2 DP3

Type: New Feature Priority: Major
Reporter: John Zablocki Assignee: John Zablocki
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Add method to remove buckets from client

 Comments   
Comment by John Zablocki [ 05/Sep/12 ]
Released in 1.2 DP3



[NCBC-64] Support flushing of bucket from client Created: 12/Jun/12  Updated: 03/Jan/13  Resolved: 05/Sep/12

Status: Closed
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: None
Fix Version/s: 1.2 DP3

Type: New Feature Priority: Major
Reporter: John Zablocki Assignee: John Zablocki
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Add method to flush a bucket

 Comments   
Comment by John Zablocki [ 05/Sep/12 ]
Released in 1.2 DP3



[NCBC-69] Client needs to support server authentication and config for bucket admin tasks Created: 14/Jun/12  Updated: 03/Jan/13  Resolved: 05/Sep/12

Status: Closed
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: None
Fix Version/s: 1.2 DP3

Type: New Feature Priority: Major
Reporter: John Zablocki Assignee: John Zablocki
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Comments   
Comment by John Zablocki [ 05/Sep/12 ]
Released in 1.2 DP3



[NCBC-96] Latest Enyim ResultHelper.ProcessResponseData has optional message and new param order Created: 17/Aug/12  Updated: 03/Jan/13  Resolved: 05/Sep/12

Status: Closed
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: None
Fix Version/s: 1.2 DP3

Type: Bug Priority: Major
Reporter: John Zablocki Assignee: John Zablocki
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Comments   
Comment by John Zablocki [ 05/Sep/12 ]
Released in 1.2 DP3



[NCBC-98] document the connection pool options Created: 21/Aug/12  Updated: 02/Jan/13  Resolved: 02/Jan/13

Status: Closed
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: None
Fix Version/s: 1.2.1

Type: Improvement Priority: Major
Reporter: Matt Ingenthron Assignee: John Zablocki
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Couldn't find anything about the pool size in the docs. Please add.

<socketPool minPoolSize="10" maxPoolSize="300" connectionTimeout="00:00:10" deadTimeout="00:00:10" />


 Comments   
Comment by John Zablocki [ 02/Jan/13 ]
Merged and deployed.



[NCBC-176] Support flushing of bucket from client Created: 07/Dec/12  Updated: 02/Jan/13  Resolved: 02/Jan/13

Status: Closed
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: 1.2.0
Fix Version/s: 1.2 Beta-3

Type: New Feature Priority: Major
Reporter: John Zablocki Assignee: John Zablocki
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Comments   
Comment by John Zablocki [ 02/Jan/13 ]
NCBC-190



[NCBC-60] Cache misses incorrectly being returning "Unable to locate node" errors Created: 11/Jun/12  Updated: 02/Jan/13  Resolved: 02/Jan/13

Status: Resolved
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: 1.1, 1.1.5, 1.1.6
Fix Version/s: 1.2 Beta-2

Type: Bug Priority: Major
Reporter: John Zablocki Assignee: John Zablocki
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Comments   
Comment by John Zablocki [ 02/Jan/13 ]
Released



[NCBC-185] document bugs Created: 18/Dec/12  Updated: 01/Jan/13  Resolved: 01/Jan/13

Status: Resolved
Project: Couchbase .NET