Release v0.14.21 — Redis Cacher + seq/instanceID heartbeat + audit fixes - #43
Merged
Merged
Conversation
…ity) Matches Node.js Moleculer base discoverer heartbeatReceived(): - seq mismatch → services changed on remote node → request fresh INFO - instanceID mismatch → node restarted → request fresh INFO - Also includes seq/instanceID in heartbeat payload so remote Python nodes can detect changes without waiting for INFO round-trip Refs: Node.js base.js:205-229 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…integration tests Fixes P0 gap: RedisCacher.start()/stop() now properly connect/disconnect. Broker calls these during lifecycle — previously they were no-ops, meaning Redis cacher was never actually connected. Changes: - start() → calls connect() (establishes Redis connection) - stop() → calls disconnect() (graceful cleanup) - init() resets connected=False (base sets True, wrong for network cachers) - 16 integration tests with real Redis (get/set/delete/clean/ttl/keys/broker) Evidence: 2371 tests pass, mypy 0, demo 28/28. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
feat(cacher): Redis cacher production-ready + 16 integration tests
fix(transit): seq/instanceID heartbeat checks (Node.js parity)
…ion, ping loop 3 CRITICAL + 1 HIGH from Redis cacher audit: - CRITICAL: self.logger set in __init__ as fallback (was only in init()) - CRITICAL: removed duplicate namespace prefix logic (BaseCacher.init handles it) - CRITICAL: TTL validation — negative/zero TTL now warns and stores without expiry (was silently passing negative to Redis → ResponseError swallowed) - HIGH: ping loop now pings first, then sleeps (detects immediate connection drop) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
… discover cleanup Heartbeat audit (2 CRITICAL, 1 HIGH, 2 MEDIUM): - CRITICAL: instanceID now persisted in process_node_info (was causing infinite re-discovery loop — every heartbeat triggered DISCOVER) - HIGH: seq comparison coerces to int (cross-language safety) - MEDIUM: instanceID=None guard prevents spurious re-discovery on first contact Security audit (1 CRITICAL, 1 HIGH): - CRITICAL: payload dict type guard in _handle_heartbeat (prevents crash on malformed packet where payload is None or non-dict) - HIGH: _discover_pending stale entries evicted in check_remote_nodes (prevents unbounded memory growth under network partitions) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Release v0.14.21: - Redis Cacher production-ready (start/stop lifecycle, 16 integration tests) - seq/instanceID heartbeat checks (Node.js parity) - 10 audit findings fixed (3 CRITICAL: instanceID persistence, payload guard, logger fallback + 4 HIGH + 3 MEDIUM) Evidence: 2374 tests, 28/28 demo matrix, 90/90 comprehensive, mypy 0. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Version: 0.14.21 (supersedes 0.14.20) CHANGELOG: both 0.14.20 and 0.14.21 entries preserved Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Codecov Report❌ Patch coverage is 📢 Thoughts on this report? Let us know! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release v0.14.21
Highlights
Critical fixes
Evidence
🤖 Generated with Claude Code