docs(buglog): record Gitea sync for bug-1958..bug-1966

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

2026-10-10 10:20:18 +00:00

2.1 KiB

Raw Blame History

status

status_updated

status_note

component

severity

timestamp

last_seen

occurrences

files

bug-1964: xce_scheduler --sim does not re-seed limits when a config push arrives mid-replay

Description

Observed: (source reading; follow-up of the 2026-10-10 P0 fixes (bug-1936..1957)) Reported by the bug-1943 fix: the simulator seeds the limit plugin only at bootstrap (sim_bootstrap_limit_plugin); a CONFIG_PUSH during replay updates groups (bug-1943) but a new or changed limit config never reaches the limit plugin, while the live scheduler applies it (plugin_config_update).

Expected: Live and simulated scheduling apply the same limits after a config change. Impact: Replays that span a limit config change decide differently than live. Found by: follow-up of the 2026-10-10 P0 fixes (bug-1936..1957)

Environment

OS: no /etc/os-release; Docker container; NixOS kernel; kernel Linux 6.18.33 x86_64
libc: glibc 2.42-47 (interpreter /nix/store/wb6rhpznjfczwlwx23zmdrrw74bayxw4-glibc-2.42-47/lib/ld-linux-x86-64.so.2)
Toolchain: gcc (GCC) 15.2.0, meson 1.9.1
Build: asan (xce.build)
Code: scheduler-framework @ 19be145d-dirty
Deployment: any (found by source reading; confirmed by the RED test of the fix)

Reproduction

Replay a recording with a CONFIG_PUSH that changes a limit; compare decisions with live.

Frequency: deterministic (by code reading; confirmed by the RED test of the fix)
Evidence: the code sites quoted in Description; no logs kept.

Root cause

TODO: required for fixed/partial

Fix