ginuerzh cd97e5e746 fix(hop): skip priority short-circuit when multiple nodes share the same priority ...

When two or more nodes have an identical matcher rule they receive
identical default priority (rule string length). The priority shortcut
assumed the top-priority node was the single authoritative choice and
returned it directly, bypassing the selector (FailFilter, BackupFilter,
strategy) — so weight, round-robin, and hash were silently ignored.

Add a third condition: the top priority must be strictly greater than
the second-highest. When multiple nodes share the same highest priority
the selector applies normally for load balancing.

Add doc comments on NodeMatcherConfig.Priority explaining the three
semantic ranges (0=auto, negative=always-selector, positive=shortcut).

2026-06-26 22:53:17 +08:00

..

parse_test.go

test(parsing): add 229 unit tests across 18 config/parsing packages

2026-05-24 13:34:33 +08:00

parse.go

fix(hop): skip priority short-circuit when multiple nodes share the same priority

2026-06-26 22:53:17 +08:00