couchbaselabs

Couchbase SDK error handling — UnambiguousTimeoutException vs AmbiguousTimeoutException, DocumentNotFoundException, CasMismatchException, DurabilityImpossibleException, SDK debug logging, sdk-doctor connectivity diagnostics, retryable vs non-retryable errors, circuit breaker, error best practices

Couchbase SDK patterns for Rust — CAS optimistic locking, retry on CasMismatch, tokio bulk operations with join_all/FuturesUnordered, atomic counters, sub-document (MutateInSpec/LookupInSpec), array operations, exists, replica reads, touch/getAndTouch, preserve_expiry, error handling

Configure and optimize Couchbase SDK connections in Rust — async/tokio cluster setup, singleton pattern, wait_until_ready, timeouts, KV CRUD (upsert/insert/get/replace/remove), expiry, durability, sub-document operations

SQL++ queries with the Couchbase Rust SDK — scope.query, cluster.query, positional and named parameters, scan consistency, deserializing rows into structs, DML (INSERT/UPDATE/DELETE/UPSERT), MutationState RYOW

Testing Couchbase Rust applications — unit testing with mockall, integration testing with testcontainers-rs, scope/collection isolation

Distributed ACID transactions are not supported by the Couchbase Rust SDK 1.x — alternatives and workarounds

Entry point for all Couchbase questions — routes to the right skill based on topic and language. Use for any question about Couchbase SDK connection, querying, search, transactions, analytics, field-level encryption, testing, mobile, caching, eventing, Kafka, XDCR, backup, security, or data modeling.

Introduction to Couchbase for new developers — mental model, core concepts (bucket/scope/collection/document), service map (KV vs SQL++ vs Search vs Analytics), choosing the right skill, and where to start

Structured code review process for TAF changes. Provides step-by-step guidance for reviewing Python test code, configuration files, and library changes. Use when asked to review a PR, diff, or set of changed files in TAF.

Adds source citations to responses indicating which documentation files provided the information, or indicates if response is from general context. Use this whenever providing guidance to ensure transparency and traceability.

Triages and debugs TAF test failures. Phase 1 checks if the test passed on the previous release branch and classifies as test regression or product bug. Phase 2 maps logs to source, diagnoses root cause, and proposes a fix. Use when you have run logs or a failing test name.

Prepare weekly SE-Section opportunity updates for the current SE — a review package of proposed SE Next Steps + validated SE Technical Risk for the opportunities whose SE Section is going stale, so the SE can apply them in Salesforce fast. Use when the user asks to "prep my SE updates", "what SE opps am I behind on", "update my opportunities", "SE section updates", or wants to catch up their weekly Salesforce SE hygiene. v0.1 — SE-Section fields only (activity logging comes later). READ-ONLY: never writes to Salesforce; produces edits for the human to apply.

Generate and publish a Couchbase-branded "Portfolio Account Status" report — a per-account table of AE/TSE, open opportunities, ARR, and support ticket load across all of Austin Gonyou's confirmed Salesforce accounts. Use when the user asks for a "portfolio report", "account status report", "my accounts", "my opportunities", or wants a refreshed view of their SFDC book of business alongside support health. Always re-verify the account list per the process below rather than reusing a previously-confirmed list from memory, since SFDC data changes.

Run a FIT test

Investigate and triage FIT failures on GHA or local runs.