Skip to content

fix: standardize leader connection close/keepalive labels - #47

Open
rcbevans wants to merge 1 commit into
mainfrom
fix/leader-label-spelling
Open

fix: standardize leader connection close/keepalive labels#47
rcbevans wants to merge 1 commit into
mainfrom
fix/leader-label-spelling

Conversation

@rcbevans

Copy link
Copy Markdown
Contributor

Problem

The same physical connection (deps.leader_conn) was labeled "leader" in deps.py and shutdown.py but "leader_conn" in leader.py. This meant log events and metrics for a single connection appeared under two different label values, making it harder to correlate close/keepalive events across the codebase.

Fix

Standardized to "leader" (the majority spelling) across all close_conn_bounded and apply_keepalive_to_conn call sites in leader.py, plus the corresponding test assertions in test_leader.py.

Scope

Only string label literals changed — no variable names, attribute names, or function names were touched.

@rcbevans
rcbevans requested review from XBeg9, clinzy and kjw-azx July 29, 2026 04:28
@rcbevans rcbevans self-assigned this Jul 29, 2026
The same physical connection (deps.leader_conn) was labeled "leader"
in deps.py and shutdown.py but "leader_conn" in leader.py, causing
log events and metrics for one connection to appear under two
different label values. Standardized to "leader" (the majority
spelling) across all close_conn_bounded and apply_keepalive_to_conn
call sites.

Only string label literals changed; no variable names, attribute
names, or function names were touched.
@rcbevans
rcbevans force-pushed the fix/leader-label-spelling branch from 4d25e67 to aaae997 Compare July 30, 2026 04:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant