[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-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-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-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-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. |