You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Include expected and announced identities in peer-binding refusal logs #1153
Deferred from the closing review of #1116 for declarative sharding (Pro #980). The owner explicitly scoped this root cause out of the closing implementation batch.
Current assessment: The refusal is enforced; additional expected/announced peer names improve diagnosis only.
Owning path:replication/replicationConnection.ts. Review lines move as the companion branches integrate main; use the linked PR's current source.
Follow-up: Implement and verify the scoped documentation or test improvement without expanding the current runtime contract.
This issue does not reopen #980's approved primary-key-only scope, complete-history requirement, or ban on write serialization. It does not block the current drafts. No release or backport is committed; milestone is intentionally unset. Found through source review and synthetic tests; there is no customer-specific incident evidence.
Triage: P3; effort Low; type Task. Low-priority follow-up: no demonstrated correctness failure or new release requirement. This is deliberately below the parent reliability priority.
Activity