Repository navigation
#134 feat: the consumer loop logs its recovery after a failure run - #141
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The first good step after one or more failed steps logs one INFO `consumer loop recovered` with `after_failures`, then resets the count (Replicator's shape, replicator#193). No record on a good step after none, nor when a stop ends a backoff. Spec Amended entry and §3 Health; NETWORK.md's flap signature, query and window; MONITORING.md. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…every WARNING Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…p_after Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
22 of 24 tasks
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
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.
Refs #134
The consume loop now logs its recovery: the first good step after one or more failed steps logs one INFO
consumer loop recoveredwithafter_failures(Replicator's shape, CannObserv/replicator#193), then resets the count. No record on a good step after none, nor when a stop ends a backoff.src/processor/consumer.py: afailurescount besidebackoffinrun(); docstring.tests/test_consumer.py(integration): fail×3 then good → 1 record (after_failures == 3, INFO, after the WARNINGs); two runs →[2, 1]; good only → none; stop during a backoff → none; the boot path (broker.invalidunresolved twice) → one record withafter_failures == 2, afterconsuming.-p warninghides it), the window's end. MONITORING.md: one line.docs/plans/2026-11-16-134-consumer-recovery-log.md. Brief check: Consumer loop logs no recovery after a failure run (backoff resets silently) #134 comment 6928995289.No contract, wire, lock or
processor_versionchange. Deploy = restart.🤖 Generated with Claude Code