Repository navigation
Update README_TEMPLATE with maintenance notice - #921
Merged
Merged
Conversation
Added a note about project maintenance status and alternative functionality in Apache Kafka.
Antony Stubbs (astubbs)
added a commit
to astubbs/parallel-consumer
that referenced
this pull request
Jul 28, 2026
…p findings in manifest The 2026-07-28 activity sweep surfaced upstream items the manifest didn't have. Reconcile confluentinc#859: upstream PR confluentinc#892 (priesus) MERGED 2025-10-27 also targets the PCMetrics leak, but fixes a DIFFERENT cause (OffsetMapCodecManager re-instantiated each commit, recreating meters) than our fork fix (duplicate meter re-registration on assign/revoke). Issue confluentinc#859 is still open, so mark upstream status 'mixed' and add a reconciliation block tracking the open questions: does the fork already carry confluentinc#892 / conflict with it, and did confluentinc#892 actually break the master build (the author feared so; astubbs attributed it to the io.stubbs.truth dep not being on Maven Central, not a code regression) -- verify before relying on it. Adds a documented optional `reconciliation` field to the schema. Capture other new findings: confluentinc#917 kafka-clients 3.9.2 SECURITY (into the security batch); confluentinc#918/confluentinc#919 log-noise trims as a new logging-ux entry (with confluentinc#640/confluentinc#629/confluentinc#631); confluentinc#920 JDK 17 build-doc PR linked to the Java-baseline entry; confluentinc#902 KEY-ordering issue as a new entry; note confluentinc#921/confluentinc#922 (fork-awareness already partly upstream) on the maintenance-signal entry so we don't duplicate it when backlinking. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Antony Stubbs (astubbs)
added a commit
to astubbs/parallel-consumer
that referenced
this pull request
Aug 5, 2026
PHASE 3. Every upstream issue is now mirrored, so upstream-map.yaml no longer needs to track issues. Slimmed 24 entries -> 14: the 9 that only ever tracked issues are gone (all had mirrors), as is the fork-only release entry, which is now issue #197 plus docs/inflight/release-0.6.0.0.md. Survivors are the entries tracking upstream PRs, which are NOT mirrored - the cherry-pick candidates, the security batch, the dep bumps. Each links its mirror through a single `fork_issue` field. Three fields dropped because something better now answers them: - `forwarded` - the durable record of a backlink is the upstream comment itself, which carries a hidden marker, plus the mirror. A field here goes stale the moment anyone comments and had already drifted. - `related` - noise once the mirror carries the diagnosis. - `todo` - almost every entry was "rebase PR #N, it is 57 behind master", which docs/inflight/AGENTS.md says never to write down: `git rev-list --left-right --count` answers it and cannot be wrong. Editorial notes were ported into the mirrors before deletion rather than lost - notably that upstream PRs confluentinc#921/confluentinc#922 already added a fork-awareness notice to upstream's README (#195), and that upstream confluentinc#803 is the only issue on that tracker labelled "verified bug" (#44). scripts/upstream-map.py: `forwarded` removed from REQUIRED, and the posted-refs and todo subcommands dropped from the usage text. `validate` passes on 14 entries; table/refs/tracked/meta all still work. REFACTOR INDEX. docs/refactoring.md gains a table of the refactor-shaped mirrors with both fork and upstream links, so a refactor sweep can collect them without checking GitHub, plus a pointer on each matching section. Not a parallel list - AGENTS.md is explicit that triage lives in this file. It also carries two findings the file did not have, because they came from diagnosing the mirrors rather than reading the code: WorkContainer.workType is read by nobody, so deletion beats the enum conversion #241 asks for; and #101 fixed the static-state flake but not the hazard the issue is actually about. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QqHpNSXC39ANv9kG1ZvUzn
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.
No description provided.