Repository navigation
Conversation
…sation The fix adds a trailing sweep(now) that enforces the 64-lane limit and refreshes stats after the insertion. The leading sweep(now) ran the same TTL + lane-limit + stats work with the same `now` moments earlier, so it is redundant. Removing it keeps one sweep per learn (the hot path taken on every attributed dispatch) with no behavior change: the per-lane LRU plus the trailing sweep reach the identical final state (verified: 18/18 targeted recall/fingerprint/dsh tests pass with and without it).
Merge upstream master 6a641f3, including the architecture module-map and schedule-independent ranxianglei#2929 probe fixes. Preserve the existing PR head and exact contribution patch. Validation of this refreshed head runs in upstream CI; no local test rerun is claimed.
(ai: vllm-qwen/qwen3.8-27b) Re-verified live check state before touching anything: the three failing checks in this wake ( No merge conflict ( |
Problem
Global conversation-recall eviction chooses the oldest individual session, so an idle sibling can evict a lane containing a recently learned or recalled session. Record-only traffic also leaves 65 lanes until the next operation.
Change
Compare each lane by its most recent session activity, then enforce the existing 64-lane limit immediately after learning. TTL, unique-boundary matching, and the per-lane session limit stay unchanged.
Verification
301e1a5459a77d5578206927c8062a58381af642(master, 0.1.215).npm run typecheck,npm run build, andgit diff --check: passed.Closes #6995