cogno-sync 0.1.1__tar.gz

cogno_sync-0.1.1/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Sudoers AI
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

cogno_sync-0.1.1/PKG-INFO

@@ -0,0 +1,191 @@
+Metadata-Version: 2.4
+Name: cogno-sync
+Version: 0.1.1
+Summary: Distributed coordination primitives for the Cogno stack — async lock, token-bucket rate limiter, claim-once idempotency store and rolling daily cap, each with an in-process default and a Redis adapter
+Author: Vinicius Vale
+Maintainer: Sudoers AI
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/sudoers-ai/cogno-sync
+Project-URL: Repository, https://github.com/sudoers-ai/cogno-sync
+Project-URL: Issues, https://github.com/sudoers-ai/cogno-sync/issues
+Keywords: redis,distributed-lock,rate-limiting,token-bucket,idempotency,quota,asgi,agents
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Software Development :: Libraries
+Classifier: Topic :: System :: Distributed Computing
+Classifier: Operating System :: OS Independent
+Classifier: Typing :: Typed
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Provides-Extra: redis
+Requires-Dist: redis>=5.0; extra == "redis"
+Provides-Extra: asgi
+Requires-Dist: starlette>=0.36; extra == "asgi"
+Provides-Extra: dev
+Requires-Dist: pytest>=8.0; extra == "dev"
+Requires-Dist: pytest-asyncio>=0.23.0; extra == "dev"
+Requires-Dist: pytest-cov>=5.0; extra == "dev"
+Requires-Dist: redis>=5.0; extra == "dev"
+Requires-Dist: starlette>=0.36; extra == "dev"
+Requires-Dist: httpx>=0.24; extra == "dev"
+Requires-Dist: ruff>=0.5; extra == "dev"
+Requires-Dist: mypy>=1.8; extra == "dev"
+Dynamic: license-file
+
+# cogno-sync
+
+**Distributed coordination primitives for the [Cogno](https://github.com/sudoers-ai/cogno-anima) stack** — an async lock, a token-bucket rate limiter, a claim-once idempotency store and a rolling daily cap. Each is a `Protocol` port with a zero-infra in-process default and a Redis adapter that shares the state across workers.
+
+> Status: **alpha** — extracted from a production host, with its suite.
+
+## The problem this is for
+
+Everything here exists because **one process is not the deployment**. The in-process versions of
+these four things are five lines each and they are all correct — until a second worker starts.
+Then the lock guards nothing, the limiter hands out N× the budget, the same delivery is handled
+twice, and each worker gives every caller its own daily allowance.
+
+| Port | In-process default | Redis adapter | What the adapter buys |
+| --- | --- | --- | --- |
+| `LockProvider` | `InProcessLockProvider` | `RedisLockProvider` | mutual exclusion **across** processes (`SET NX EX` + owner-only Lua release) |
+| `RateLimiter` | `InMemoryTokenBucketLimiter` | `RedisTokenBucketLimiter` | one shared bucket, refilled atomically under the **server's** clock |
+| `IdempotencyStore` | `InMemoryIdempotencyStore` | `RedisIdempotencyStore` | a claim two workers cannot both win (`SET NX`) |
+| `DailyCap` | `InMemoryDailyCap` | `RedisDailyCap` | one allowance per caller, not one per worker |
+
+## Everything fails OPEN
+
+A Redis outage, a lock that cannot be acquired within `max_wait`, a counter that will not
+answer: the work runs anyway, with a `WARNING`. These are guards against a rare double-run and
+against cost — never correctness barriers. Refusing to serve a legitimate caller because a cache
+blipped is the worse failure, and it is the one that takes the product down with the cache.
+
+If you need the opposite (a strict guard that must refuse when it cannot verify), do not
+configure your way there — wrap the port and decide it in your own code, where the trade-off is
+visible.
+
+## One client, one pool
+
+Every `Redis*` adapter here takes the **same** constructor:
+
+```python
+Adapter(client=None, *, url="", key_prefix="cogno:…:")
+```
+
+Build one client in your process and inject it everywhere:
+
+```python
+from cogno_sync import (client_from_url, RedisLockProvider, RedisTokenBucketLimiter,
+                        RedisIdempotencyStore, RedisDailyCap)
+
+redis = client_from_url(os.environ["REDIS_URL"], decode_responses=True)
+
+locks   = RedisLockProvider(redis)
+limiter = RedisTokenBucketLimiter(redis, rate_per_sec=10, burst=20)
+claims  = RedisIdempotencyStore(redis)
+cap     = RedisDailyCap(redis)
+```
+
+That uniformity is the feature. The code this was extracted from had **three** constructor
+conventions across five adapters and a copy of `Redis.from_url` in each one, so a worker held
+one connection pool per adapter — and a URL passed in the client slot failed on the first
+command, where fail-open swallowed it and the coordination was silently off for months.
+
+Passing `url=` instead builds the client lazily, on first use: handy for a one-adapter script,
+and it keeps start-up independent of whether the server is up yet.
+
+## Using them
+
+```python
+# serialize a critical section by key (across workers)
+async with locks.lock(f"session:{session_id}"):
+    ...
+
+# spend one unit of budget
+decision = await limiter.check(client_ip)
+if not decision.allowed:
+    return too_many_requests(retry_after=decision.retry_after)
+
+# handle a delivery once (claim BEFORE the work, release if nothing happened)
+if await claims.seen_before(key):
+    return
+try:
+    ...
+except NothingHappenedYet:
+    await claims.forget(key)
+
+# a rolling daily ceiling (the caller owns the key, including the day stamp)
+from cogno_sync import utc_day
+used = await cap.hit(f"demo:{utc_day()}:{client_ip}")
+if used > DAILY_LIMIT:
+    return politely_closed()
+```
+
+The **key is always yours to compose**. This library never invents one: what makes two deliveries
+distinct, or two callers separate, is a property of your system — and getting it wrong is
+silent (one caller's budget spent by another, one message dropped as a duplicate of a different
+one).
+
+## ASGI extra
+
+```bash
+pip install "cogno-sync[asgi]"
+```
+
+```python
+from cogno_sync.asgi import RateLimitMiddleware, read_capped_body, BodyTooLarge
+
+app.add_middleware(RateLimitMiddleware, limiter=limiter,
+                   prefixes=("/api", "/chat"),   # default: every path
+                   trusted_proxy_hops=1)         # how many proxies you trust in front
+```
+
+`trusted_proxy_hops` decides which `X-Forwarded-For` entry is the real caller — the N-th from
+the **right**, because each proxy appends the address it saw. Reading the leftmost hop is
+spoofable: a caller sets the header and gets a fresh budget on every request. It is a
+constructor argument, never an environment read at import time, so a test can set it and two
+apps in one runtime can differ.
+
+`read_capped_body` reads a request body incrementally and raises `BodyTooLarge` past the limit —
+for the unauthenticated routes where the signature can only be verified *after* the payload is
+read, and where `await request.body()` would buffer an unbounded stream into the worker's heap.
+
+## Install
+
+```bash
+pip install cogno-sync                # zero hard dependencies
+pip install "cogno-sync[redis]"       # the cross-worker adapters
+pip install "cogno-sync[asgi]"        # the middleware + body cap
+pip install -e ".[dev]"               # tests + lint + type-check
+```
+
+## The Cogno ecosystem
+
+`cogno-sync` is one organ of **[Cogno](https://github.com/sudoers-ai)** — a family of
+small, composable, Apache-2.0 libraries that together form a complete
+conversational-agent platform. Each library owns a single concern and stays
+infra-agnostic; a **host** assembles them into a running agent:
+
+![The Cogno ecosystem](docs/assets/cogno-ecosystem.svg)
+
+The open-source libraries are the organs; the **host is the body** that joins
+them. Our reference host — `cogno-host`, with its `cogno-ui` dashboard — is the
+private product layer, but it holds no special powers: everything it does rides
+on the public seams documented in each library's `docs/HOST_INTEGRATION.md`, so
+you can assemble a body of your own.
+
+## Test
+
+```bash
+pytest tests/unit -q                                    # no server needed
+COGNO_TEST_REDIS_URL=redis://127.0.0.1:6379/0 pytest tests/integration -q
+```
+
+The unit suite drives the Redis adapters against fakes; the integration suite proves the parts
+only a server can show — two clients sharing one bucket, a claim that survives across
+connections, the TTL Redis itself holds, and the release script comparing the owner token
+inside Redis.

cogno_sync-0.1.1/README.md

@@ -0,0 +1,152 @@
+# cogno-sync
+
+**Distributed coordination primitives for the [Cogno](https://github.com/sudoers-ai/cogno-anima) stack** — an async lock, a token-bucket rate limiter, a claim-once idempotency store and a rolling daily cap. Each is a `Protocol` port with a zero-infra in-process default and a Redis adapter that shares the state across workers.
+
+> Status: **alpha** — extracted from a production host, with its suite.
+
+## The problem this is for
+
+Everything here exists because **one process is not the deployment**. The in-process versions of
+these four things are five lines each and they are all correct — until a second worker starts.
+Then the lock guards nothing, the limiter hands out N× the budget, the same delivery is handled
+twice, and each worker gives every caller its own daily allowance.
+
+| Port | In-process default | Redis adapter | What the adapter buys |
+| --- | --- | --- | --- |
+| `LockProvider` | `InProcessLockProvider` | `RedisLockProvider` | mutual exclusion **across** processes (`SET NX EX` + owner-only Lua release) |
+| `RateLimiter` | `InMemoryTokenBucketLimiter` | `RedisTokenBucketLimiter` | one shared bucket, refilled atomically under the **server's** clock |
+| `IdempotencyStore` | `InMemoryIdempotencyStore` | `RedisIdempotencyStore` | a claim two workers cannot both win (`SET NX`) |
+| `DailyCap` | `InMemoryDailyCap` | `RedisDailyCap` | one allowance per caller, not one per worker |
+
+## Everything fails OPEN
+
+A Redis outage, a lock that cannot be acquired within `max_wait`, a counter that will not
+answer: the work runs anyway, with a `WARNING`. These are guards against a rare double-run and
+against cost — never correctness barriers. Refusing to serve a legitimate caller because a cache
+blipped is the worse failure, and it is the one that takes the product down with the cache.
+
+If you need the opposite (a strict guard that must refuse when it cannot verify), do not
+configure your way there — wrap the port and decide it in your own code, where the trade-off is
+visible.
+
+## One client, one pool
+
+Every `Redis*` adapter here takes the **same** constructor:
+
+```python
+Adapter(client=None, *, url="", key_prefix="cogno:…:")
+```
+
+Build one client in your process and inject it everywhere:
+
+```python
+from cogno_sync import (client_from_url, RedisLockProvider, RedisTokenBucketLimiter,
+                        RedisIdempotencyStore, RedisDailyCap)
+
+redis = client_from_url(os.environ["REDIS_URL"], decode_responses=True)
+
+locks   = RedisLockProvider(redis)
+limiter = RedisTokenBucketLimiter(redis, rate_per_sec=10, burst=20)
+claims  = RedisIdempotencyStore(redis)
+cap     = RedisDailyCap(redis)
+```
+
+That uniformity is the feature. The code this was extracted from had **three** constructor
+conventions across five adapters and a copy of `Redis.from_url` in each one, so a worker held
+one connection pool per adapter — and a URL passed in the client slot failed on the first
+command, where fail-open swallowed it and the coordination was silently off for months.
+
+Passing `url=` instead builds the client lazily, on first use: handy for a one-adapter script,
+and it keeps start-up independent of whether the server is up yet.
+
+## Using them
+
+```python
+# serialize a critical section by key (across workers)
+async with locks.lock(f"session:{session_id}"):
+    ...
+
+# spend one unit of budget
+decision = await limiter.check(client_ip)
+if not decision.allowed:
+    return too_many_requests(retry_after=decision.retry_after)
+
+# handle a delivery once (claim BEFORE the work, release if nothing happened)
+if await claims.seen_before(key):
+    return
+try:
+    ...
+except NothingHappenedYet:
+    await claims.forget(key)
+
+# a rolling daily ceiling (the caller owns the key, including the day stamp)
+from cogno_sync import utc_day
+used = await cap.hit(f"demo:{utc_day()}:{client_ip}")
+if used > DAILY_LIMIT:
+    return politely_closed()
+```
+
+The **key is always yours to compose**. This library never invents one: what makes two deliveries
+distinct, or two callers separate, is a property of your system — and getting it wrong is
+silent (one caller's budget spent by another, one message dropped as a duplicate of a different
+one).
+
+## ASGI extra
+
+```bash
+pip install "cogno-sync[asgi]"
+```
+
+```python
+from cogno_sync.asgi import RateLimitMiddleware, read_capped_body, BodyTooLarge
+
+app.add_middleware(RateLimitMiddleware, limiter=limiter,
+                   prefixes=("/api", "/chat"),   # default: every path
+                   trusted_proxy_hops=1)         # how many proxies you trust in front
+```
+
+`trusted_proxy_hops` decides which `X-Forwarded-For` entry is the real caller — the N-th from
+the **right**, because each proxy appends the address it saw. Reading the leftmost hop is
+spoofable: a caller sets the header and gets a fresh budget on every request. It is a
+constructor argument, never an environment read at import time, so a test can set it and two
+apps in one runtime can differ.
+
+`read_capped_body` reads a request body incrementally and raises `BodyTooLarge` past the limit —
+for the unauthenticated routes where the signature can only be verified *after* the payload is
+read, and where `await request.body()` would buffer an unbounded stream into the worker's heap.
+
+## Install
+
+```bash
+pip install cogno-sync                # zero hard dependencies
+pip install "cogno-sync[redis]"       # the cross-worker adapters
+pip install "cogno-sync[asgi]"        # the middleware + body cap
+pip install -e ".[dev]"               # tests + lint + type-check
+```
+
+## The Cogno ecosystem
+
+`cogno-sync` is one organ of **[Cogno](https://github.com/sudoers-ai)** — a family of
+small, composable, Apache-2.0 libraries that together form a complete
+conversational-agent platform. Each library owns a single concern and stays
+infra-agnostic; a **host** assembles them into a running agent:
+
+![The Cogno ecosystem](docs/assets/cogno-ecosystem.svg)
+
+The open-source libraries are the organs; the **host is the body** that joins
+them. Our reference host — `cogno-host`, with its `cogno-ui` dashboard — is the
+private product layer, but it holds no special powers: everything it does rides
+on the public seams documented in each library's `docs/HOST_INTEGRATION.md`, so
+you can assemble a body of your own.
+
+## Test
+
+```bash
+pytest tests/unit -q                                    # no server needed
+COGNO_TEST_REDIS_URL=redis://127.0.0.1:6379/0 pytest tests/integration -q
+```
+
+The unit suite drives the Redis adapters against fakes; the integration suite proves the parts
+only a server can show — two clients sharing one bucket, a claim that survives across
+connections, the TTL Redis itself holds, and the release script comparing the owner token
+inside Redis.

cogno_sync-0.1.1/cogno_sync/__init__.py

@@ -0,0 +1,62 @@
+"""
+cogno-sync — distributed coordination primitives for the Cogno stack.
+
+Four small ports, each with a zero-infra in-process default and a Redis adapter that shares the
+state across workers: a lock, a token-bucket rate limiter, a claim-once idempotency store, and a
+rolling daily counter. Every adapter is async, every one **fails open**, and every one takes the
+same constructor — a ready client, or a URL to build one from.
+
+Redis is an optional extra (``cogno-sync[redis]``), imported only when a client is built; the
+ASGI middleware lives in :mod:`cogno_sync.asgi` behind ``cogno-sync[asgi]``. Importing this
+package pulls in neither.
+"""
+
+from importlib.metadata import PackageNotFoundError
+from importlib.metadata import version as _dist_version
+
+try:
+    __version__ = _dist_version("cogno-sync")
+except PackageNotFoundError:  # source tree without an installed dist (e.g. vendored checkout)
+    __version__ = "0.0.0"
+
+
+from cogno_sync._redis import client_from_url
+from cogno_sync.daily_cap import DailyCap, InMemoryDailyCap, RedisDailyCap, utc_day
+from cogno_sync.idempotency import (
+    DEFAULT_CLAIM_TTL,
+    IdempotencyStore,
+    InMemoryIdempotencyStore,
+    RedisIdempotencyStore,
+)
+from cogno_sync.locks import (
+    DEFAULT_LOCK_TTL,
+    InProcessLockProvider,
+    LockProvider,
+    RedisLockProvider,
+)
+from cogno_sync.ratelimit import (
+    InMemoryTokenBucketLimiter,
+    RateLimitDecision,
+    RateLimiter,
+    RedisTokenBucketLimiter,
+)
+
+__all__ = [
+    "client_from_url",
+    "LockProvider",
+    "InProcessLockProvider",
+    "RedisLockProvider",
+    "DEFAULT_LOCK_TTL",
+    "RateLimiter",
+    "RateLimitDecision",
+    "InMemoryTokenBucketLimiter",
+    "RedisTokenBucketLimiter",
+    "IdempotencyStore",
+    "InMemoryIdempotencyStore",
+    "RedisIdempotencyStore",
+    "DEFAULT_CLAIM_TTL",
+    "DailyCap",
+    "InMemoryDailyCap",
+    "RedisDailyCap",
+    "utc_day",
+]

cogno_sync-0.1.1/cogno_sync/_redis.py

@@ -0,0 +1,66 @@
+"""One lazy Redis client factory, and the shared shape every ``Redis*`` adapter here follows.
+
+``redis`` is an **optional extra** (``cogno-sync[redis]``): it is imported the first time a
+client is actually built, so ``import cogno_sync`` never needs it.
+
+Every adapter in this package takes the same two arguments — a ready client, or a URL to build
+one from — and holds the same three fields. That uniformity is the point: the library this code
+came from had three different constructor conventions across five adapters, and each one grew
+its own copy of ``Redis.from_url``, so a process ended up holding one connection pool per
+adapter. **Build one client and inject it everywhere**; the URL form stays for a one-adapter
+script and for tests.
+"""
+
+from __future__ import annotations
+
+from typing import Any
+
+
+def client_from_url(url: str, *, decode_responses: bool = False) -> Any:
+    """Build a ``redis.asyncio.Redis`` from ``url``.
+
+    Nothing connects here — the client opens its pool on the first command — so this is safe
+    to call at start-up, before the server is up.
+
+    ``decode_responses=True`` makes the client return ``str`` instead of ``bytes``. Every
+    adapter in this package works either way: none of them compares a returned value against a
+    literal (the lock's owner check runs inside Redis, the limiter reads integers), so a caller
+    that shares one client with its own code is free to pick whichever that code needs.
+    """
+    if not url:
+        raise ValueError("client_from_url needs a non-empty redis url")
+    from redis.asyncio import Redis           # lazy: the [redis] extra
+    return Redis.from_url(url, decode_responses=decode_responses)
+
+
+class _RedisAdapter:
+    """Constructor + lazy-client behaviour shared by the ``Redis*`` adapters.
+
+    Subclasses declare the full public signature themselves — ``(client=None, *, url="",
+    key_prefix="cogno:…:")`` — so the default keyspace is readable at the class that owns it.
+    """
+
+    def __init__(self, client: Any = None, *, url: str = "", key_prefix: str = "",
+                 decode_responses: bool = False) -> None:
+        if isinstance(client, str):
+            # A URL handed in the positional (the CLIENT slot) would only surface on the first
+            # command — and every adapter here fails open, so it would be swallowed forever and
+            # the coordination would be silently off. Accept it as the url instead.
+            client, url = None, client
+        if client is None and not url:
+            raise ValueError(f"{type(self).__name__} needs a redis client or a url")
+        self._client: Any = client
+        self._url: str = url
+        self._decode = decode_responses
+        self._prefix = key_prefix
+
+    def _conn(self) -> Any:
+        if self._client is None:
+            self._client = client_from_url(self._url, decode_responses=self._decode)
+        return self._client
+
+    def _key(self, key: str) -> str:
+        return f"{self._prefix}{key}"
+
+
+__all__ = ["client_from_url"]