|
Repo Added
|
Files
151
|
Badge
README BADGES
|
github
fix(helper): treat the loopback literal as such in bind lists Two helper paths read `CONFIG GET bind` and now see `::1` or `127.0.0.1` where they used to see the local.inject name. runner: getLocalAddressByIPFamily skipped 127.0.0.1 and the loopback names but not ::1, and matched the family against the unfiltered list, so a bind list of `10.244.1.5 ::1` with IPv6 preferred returned ::1, the runner's own loopback, as the source node's address. It also built the filtered list in place over the input slice. Skip both literals, match against the filtered list only, and never parse a non-literal into a family. sentinel: refreshValkeyServerInfo ran netip.MustParseAddr over every bind entry that was not a loopback literal, a panic for any hostname. The alias name a pod with an older entrypoint still binds reaches it whenever the entries before it do not match the preferred family, which is every entry when no family is set. Extract the pick into internalIPFromBind and skip what does not parse. Table tests for both, on the bind lists the entrypoints write. (cherry picked from commit 937a27931) (cherry picked from commit eced3fdb8)
69 of 71 new or added lines in 8 files covered. (97.18%)
5219 of 20666 relevant lines covered (25.25%)
0.29 hits per line
| Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line |
|---|