elky 7323d41fbe feat(routing): move sticky-key retries into routing policy with lazy attempts ...

Replace the provider/endpoint max_retries fields as the source of same-key
retries with a routing policy setting, sticky_key_attempts (default 2). Only
the first-ranked candidate is retried on the same key; every failover
candidate gets a single attempt so failover keeps advancing instead of
retrying each fallback key.

Materialize exactly one attempt per candidate and derive same-key retries in
the attempt loop after a candidate-scoped failure, so the retry budget no
longer inflates up-front materialization and needs no upper bound. The budget
travels in the report context; retries reuse the plan with a fresh candidate
id and incremented retry index. Pool groups only retry their first key within
the retry-index stride.

Expose the setting in the routing profile editor and the set_scheduling rule
action, and drop the max_retries input from the provider form.

2026-09-02 20:48:40 +08:00

..

examples

refactor: extract runtime state backends

2026-05-08 00:18:12 +08:00

src

feat(routing): move sticky-key retries into routing policy with lazy attempts

2026-09-02 20:48:40 +08:00

tests

fix(auth): reject unsigned admin identity headers

2026-08-18 11:12:17 +08:00

build.rs

Ignore tunnel release tags for app build version

2026-06-02 09:43:12 +08:00

Cargo.toml

feat(vscodex): add remote Codex collaboration module

2026-09-01 20:25:35 +08:00