tiennm99 30fd62a46c fix(couchbase): increment atomically under the tick context ...

Increment read the counter and wrote it back, ignoring the tick context, and
treated any read error as a missing document, so a timeout reset the counter
to 1. A single binary increment is atomic, honours the context, and surfaces
real errors. The cluster is also assigned only after a successful connect so
a failed connect is not closed twice.

2026-10-09 11:10:45 +07:00

..

adapter.go

fix(runtime): initialize resources per service

2026-06-28 18:03:16 +07:00

config_test.go

fix(runtime): initialize resources per service

2026-06-28 18:03:16 +07:00

couchbase_initialization.go

fix(couchbase): restore readiness timeout

2026-06-28 19:20:05 +07:00

couchbase_test.go

fix(couchbase): restore readiness timeout

2026-06-28 19:20:05 +07:00

couchbase.go

fix(couchbase): increment atomically under the tick context

2026-10-09 11:10:45 +07:00

mongodb.go

fix(runtime): initialize resources per service

2026-06-28 18:03:16 +07:00

mysql.go

fix(runtime): initialize resources per service

2026-06-28 18:03:16 +07:00

postgresql.go

fix(runtime): initialize resources per service

2026-06-28 18:03:16 +07:00

redis_test.go

feat(redis): add namespace counter key

2026-06-28 19:35:06 +07:00

redis.go

refactor(adapter)!: drop the valkey adapter in favor of redis

2026-10-09 11:10:44 +07:00