queue-aiops 0.2.1__tar.gz → 0.2.2__tar.gz

{queue_aiops-0.2.1 → queue_aiops-0.2.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: queue-aiops
-Version: 0.2.1
+Version: 0.2.2
 Summary: Governed AI-ops for redis + rabbitmq: memory-pressure/latency/queue-backlog/connection-churn RCAs, slowlog and SCAN-budgeted big-key sampling, queues/policies/nodes, and governed writes (config set, client kill, purge/delete queue, policies) with a built-in governance harness (audit, budget, undo, risk tiers)
 Author-email: wei <zhouwei008@gmail.com>
 License-Expression: MIT
@@ -192,15 +192,16 @@ queue-aiops analyze memory|latency|backlog|churn
 
 ## Verification status
 
-**Live-verified against Redis 7.4.9 (2026-07-19); RabbitMQ still mock-only.**
+**Live-verified against Redis 7.4.9 and RabbitMQ 3.13.7 (2026-07-19/20).**
 Connectivity, every Redis read (cross-checked against `redis-cli` ground truth), all
 four analyses, and the full governance loop (real `redis_config_set` → audit row →
 undo restoring the prior value) were exercised against a real server. That run found
 and fixed a real defect: integer quantities — key counts, client counts, byte totals —
 were rendered as floats (`202.0` keys), which equality assertions cannot catch.
 
-The **entire RabbitMQ command group** remains unverified against a live broker, as do
-Redis cluster/sentinel topologies and AUTH/TLS connections.
+The RabbitMQ group is now verified end-to-end too — reads cross-checked against
+`rabbitmqadmin`, and `set_policy` → `undo_apply` closing on the live broker. **Redis
+cluster/sentinel topologies and AUTH/TLS connections** remain unverified.
 
 [docs/VERIFICATION.md](docs/VERIFICATION.md) records exactly what was checked and what
 is still open. `queue-aiops doctor` is the fastest live check.

{queue_aiops-0.2.1 → queue_aiops-0.2.2}/README.md

@@ -175,15 +175,16 @@ queue-aiops analyze memory|latency|backlog|churn
 
 ## Verification status
 
-**Live-verified against Redis 7.4.9 (2026-07-19); RabbitMQ still mock-only.**
+**Live-verified against Redis 7.4.9 and RabbitMQ 3.13.7 (2026-07-19/20).**
 Connectivity, every Redis read (cross-checked against `redis-cli` ground truth), all
 four analyses, and the full governance loop (real `redis_config_set` → audit row →
 undo restoring the prior value) were exercised against a real server. That run found
 and fixed a real defect: integer quantities — key counts, client counts, byte totals —
 were rendered as floats (`202.0` keys), which equality assertions cannot catch.
 
-The **entire RabbitMQ command group** remains unverified against a live broker, as do
-Redis cluster/sentinel topologies and AUTH/TLS connections.
+The RabbitMQ group is now verified end-to-end too — reads cross-checked against
+`rabbitmqadmin`, and `set_policy` → `undo_apply` closing on the live broker. **Redis
+cluster/sentinel topologies and AUTH/TLS connections** remain unverified.
 
 [docs/VERIFICATION.md](docs/VERIFICATION.md) records exactly what was checked and what
 is still open. `queue-aiops doctor` is the fastest live check.

queue_aiops-0.2.2/RELEASE_NOTES.md

@@ -0,0 +1,29 @@
+# Release notes — queue-aiops 0.2.2
+
+Previous release: 0.2.1.
+
+## Fixed: the remaining float-typed integer quantities
+
+0.2.1 converted the obvious counts, but a regex-driven sweep missed 19 more —
+`consumers`, per-node `fdUsed`/`socketsUsed`, `queues`/`connections`/`channels`
+object totals, connection `connectedAt`, slowlog `id`/`startTime`/`durationUs`, and
+Redis `totalCommands`. A live RabbitMQ broker reported `"consumers": 0.0`.
+
+These are integers now. Genuinely fractional values — `consumerUtilisation`,
+`opsPerSec`, `fragmentationRatio`, and the `*Rate` fields — are unchanged.
+
+## Live-verified: RabbitMQ
+
+The entire RabbitMQ command group had never been run against a live broker. It has
+now been exercised against **RabbitMQ 3.13.7**: `doctor`, every read
+(`overview`, `queues`, `queue`, `connections`, `channels`, `policies`, `nodes`) with
+queue depth cross-checked against `rabbitmqadmin` ground truth, the backlog and
+churn analyses, and the full governance loop — `set_policy` really created a policy
+on the broker, `priorState` recorded that it had not existed, and `undo_apply`
+deleted it, with all three calls audited.
+
+The platform guard was confirmed too: a Redis-only analysis against a RabbitMQ
+target fails with a teaching error naming the mismatch.
+
+See [docs/VERIFICATION.md](docs/VERIFICATION.md). Redis cluster/sentinel topologies
+and AUTH/TLS connections remain unverified.

{queue_aiops-0.2.1 → queue_aiops-0.2.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "queue-aiops"
-version = "0.2.1"
+version = "0.2.2"
 description = "Governed AI-ops for redis + rabbitmq: memory-pressure/latency/queue-backlog/connection-churn RCAs, slowlog and SCAN-budgeted big-key sampling, queues/policies/nodes, and governed writes (config set, client kill, purge/delete queue, policies) with a built-in governance harness (audit, budget, undo, risk tiers)"
 readme = "README.md"
 license = "MIT"

{queue_aiops-0.2.1 → queue_aiops-0.2.2}/queue_aiops/ops/rabbit_reads.py

@@ -31,10 +31,10 @@ def broker_overview(conn: Any) -> dict:
             "messagesReady": as_int(totals.get("messages_ready")),
             "messagesUnacked": as_int(totals.get("messages_unacknowledged")),
             "messagesTotal": as_int(totals.get("messages")),
-            "queues": num(objects.get("queues")),
-            "connections": num(objects.get("connections")),
-            "channels": num(objects.get("channels")),
-            "consumers": num(objects.get("consumers")),
+            "queues": as_int(objects.get("queues")),
+            "connections": as_int(objects.get("connections")),
+            "channels": as_int(objects.get("channels")),
+            "consumers": as_int(objects.get("consumers")),
             "publishRate": rate(stats.get("publish_details")),
             "deliverRate": rate(stats.get("deliver_get_details")),
             "ackRate": rate(stats.get("ack_details")),
@@ -59,7 +59,7 @@ def _queue_row(q: dict) -> dict:
         "messages": as_int(q.get("messages")),
         "messagesReady": as_int(q.get("messages_ready")),
         "messagesUnacked": as_int(q.get("messages_unacknowledged")),
-        "consumers": num(q.get("consumers")),
+        "consumers": as_int(q.get("consumers")),
         "memoryBytes": as_int(q.get("memory")),
         "publishRate": rate(stats.get("publish_details")),
         "deliverRate": rate(stats.get("deliver_get_details")),
@@ -123,8 +123,8 @@ def list_connections(conn: Any) -> dict:
                 "peerHost": opt(pick(c, "peer_host", default="(unknown)"), 64),
                 "user": opt(c.get("user"), 64),
                 "state": opt(c.get("state"), 32),
-                "channels": num(c.get("channels")),
-                "connectedAt": num(c.get("connected_at")),
+                "channels": as_int(c.get("channels")),
+                "connectedAt": as_int(c.get("connected_at")),
                 "clientProduct": s(as_obj(c.get("client_properties")).get("product"), 64),
             }
             for c in conn.platform.rows(conn.get(conn.platform.path("connections")))
@@ -158,9 +158,9 @@ def list_channels(conn: Any) -> dict:
                 "connection": s(as_obj(c.get("connection_details")).get("name"), 128),
                 "user": opt(c.get("user"), 64),
                 "state": opt(c.get("state"), 32),
-                "unacked": num(c.get("messages_unacknowledged")),
-                "prefetch": num(c.get("prefetch_count")),
-                "consumers": num(c.get("consumer_count")),
+                "unacked": as_int(c.get("messages_unacknowledged")),
+                "prefetch": as_int(c.get("prefetch_count")),
+                "consumers": as_int(c.get("consumer_count")),
             }
             for c in conn.platform.rows(conn.get(conn.platform.path("channels")))
         ]
@@ -190,7 +190,7 @@ def list_policies(conn: Any, vhost: str | None = None) -> dict:
                 "vhost": opt(p.get("vhost"), 64),
                 "pattern": opt(p.get("pattern"), 128),
                 "applyTo": opt(pick(p, "apply-to", "apply_to", default="all"), 32),
-                "priority": num(p.get("priority")),
+                "priority": as_int(p.get("priority")),
                 "definition": as_obj(p.get("definition")),
             }
             for p in conn.platform.rows(conn.get(path))
@@ -223,10 +223,10 @@ def node_health(conn: Any) -> dict:
                     "diskFreeBytes": as_int(n.get("disk_free")),
                     "diskFreeLimitBytes": as_int(n.get("disk_free_limit")),
                     "diskAlarm": bool(n.get("disk_free_alarm")),
-                    "fdUsed": num(n.get("fd_used")),
-                    "fdTotal": num(n.get("fd_total")),
-                    "socketsUsed": num(n.get("sockets_used")),
-                    "socketsTotal": num(n.get("sockets_total")),
+                    "fdUsed": as_int(n.get("fd_used")),
+                    "fdTotal": as_int(n.get("fd_total")),
+                    "socketsUsed": as_int(n.get("sockets_used")),
+                    "socketsTotal": as_int(n.get("sockets_total")),
                 }
             )
         rows.sort(key=lambda r: r["memUsedBytes"], reverse=True)

{queue_aiops-0.2.1 → queue_aiops-0.2.2}/queue_aiops/ops/redis_reads.py

@@ -40,7 +40,7 @@ def server_info(conn: Any) -> dict:
             "connectedClients": as_int(info.get("connected_clients")),
             "blockedClients": as_int(info.get("blocked_clients")),
             "opsPerSec": num(info.get("instantaneous_ops_per_sec")),
-            "totalCommands": num(info.get("total_commands_processed")),
+            "totalCommands": as_int(info.get("total_commands_processed")),
             "keyspaceHits": as_int(info.get("keyspace_hits")),
             "keyspaceMisses": as_int(info.get("keyspace_misses")),
             "hitRatePct": pct(
@@ -143,9 +143,9 @@ def slowlog(conn: Any, count: int = MAX_SLOWLOG_ROWS) -> dict:
         entries = conn.redis_slowlog(want + 1)
         rows = [
             {
-                "id": num(e.get("id")),
-                "startTime": num(e.get("start_time")),
-                "durationUs": num(e.get("duration")),
+                "id": as_int(e.get("id")),
+                "startTime": as_int(e.get("start_time")),
+                "durationUs": as_int(e.get("duration")),
                 "command": _command_text(e.get("command")),
                 "clientAddr": opt(e.get("client_address"), 64),
                 "clientName": opt(e.get("client_name"), 64),

{queue_aiops-0.2.1 → queue_aiops-0.2.2}/server.json

@@ -7,12 +7,12 @@
     "url": "https://github.com/AIops-tools/Queue-AIops",
     "source": "github"
   },
-  "version": "0.2.1",
+  "version": "0.2.2",
   "packages": [
     {
       "registryType": "pypi",
       "identifier": "queue-aiops",
-      "version": "0.2.1",
+      "version": "0.2.2",
       "transport": {
         "type": "stdio"
       }

{queue_aiops-0.2.1 → queue_aiops-0.2.2}/uv.lock

@@ -781,7 +781,7 @@ wheels = [
 
 [[package]]
 name = "queue-aiops"
-version = "0.2.1"
+version = "0.2.2"
 source = { editable = "." }
 dependencies = [
     { name = "cryptography" },

queue_aiops-0.2.1/RELEASE_NOTES.md

@@ -1,26 +0,0 @@
-# Release notes — queue-aiops 0.2.1
-
-Previous release: 0.2.0.
-
-## Fixed: integer quantities were rendered as floats
-
-Key counts, client counts and byte totals were routed through the float coercion
-helper, so a live server reported `202.0` keys and `1.0` connected clients. The
-values were arithmetically right but semantically wrong — a count cannot be
-fractional, and a reader should not have to wonder whether `.0` means the number was
-rounded.
-
-These now use a new `as_int()` helper and come back as integers. Genuinely fractional
-values (`hitRatePct`, `usedPctOfMax`, `opsPerSec`, `expiresPct`) are unchanged. Note
-that equality assertions cannot catch this class of bug (`202 == 202.0`), so the
-regression test asserts the *type*.
-
-If you parse these fields, the JSON shape changes from `202.0` to `202`.
-
-## Live-verified
-
-This release was exercised end-to-end against a real **Redis 7.4.9** server: every
-Redis read cross-checked against `redis-cli` ground truth, all four analyses, and the
-full governance loop (real `redis_config_set` → audit row → `undo_apply` restoring the
-prior value). See [docs/VERIFICATION.md](docs/VERIFICATION.md) — **RabbitMQ remains
-mock-only** and is now the largest gap in this repo.