No description
No job could ever be scheduled in normal mode -- every round produced decision=(nil), forever. Three independent bugs were stacked on the same symptom, each masking the next (only reachable once the prior one was fixed): 1. scheduler.c's sched_init_queues() -- the scheduler's one-time synchronous initial-config-push handler -- only fired the legacy job_elect_fn-era plugin_queue_update() fan-out. builtin_fcfs (the default picker) has no .hooks, only picker_iface, so on_queue_update() was never called for any queue from the initial cluster config. Its own candidate registry stayed empty forever, so next_job() found zero candidates on every session. 2. Once #1 was fixed and a job first reached the allocator, core_events.c's core_build_job() never constructed job->schedobj -- a documented but incorrect assumption from the scheduler-core rewrite ("no picker hook reads job->schedobj... belongs to a separate allocation spec" -- no such spec exists in the live code). sched_allocator() dereferences it directly with no NULL check; reproduced live as a SIGSEGV in limit_job_election(). 3. Once #2 was fixed and a job reached genuine dispatch, resource.c's put_resvals() crashed during post-dispatch resource charging: `idxs[i] <= 0` treated resource index 0 ("slots", almost always the first registered resource) as an invalid sentinel, leaving its value slot NULL for an unconditional write two lines later. All three root-caused via gdb `bt full` on live SIGSEGVs, not guesswork, and live-verified end-to-end: a 3-element job array now runs PEND -> DISPATCH -> RUN -> DONE with the scheduler staying alive throughout. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> |
||
|---|---|---|
| .claude | ||
| .kiro | ||
| .wolf | ||
| docs/superpowers/plans | ||
| raft | ||
| reports | ||
| scripts | ||
| src | ||
| .clang-format | ||
| .gitignore | ||
| .mcp.json | ||
| .opencode.json | ||
| CLAUDE.md | ||
| README.md | ||
1. commit 规则
- 每个人 fork 自己的 branch, 从自己的 branch 做 PR,review 完再 commit
2. code format
2.1. C
推荐使用 clang-format,公共配置放在源码里面 xce/.clang-format
(理论上直接使用源码里面 xce/.clang-format 文件格式不会变)
2.1.1. vscode 可以在配置中加上如下内容
"C_Cpp.clang_format_style": "WebKit",
"C_Cpp.clang_format_fallbackStyle": "WebKit",
2.1.2. vim & emacs
clang-format -style="{BasedOnStyle: webkit}" -i XX.c
2.2. golang
使用默认 gofmt
3. build environment and build (example of ubuntu)
3.1 build environment
- Install nix package management tool
sh <(curl -L https://nixos.org/nix/install) --daemon
- Edit /etc/nix/nix.conf to make sure
experimental-features = nix-command flakes
sandbox = true
sandbox-fallback = false
substituters = https://mirrors.ustc.edu.cn/nix-channels/store https://cache.nixos.org https://cache.nixos.org/
trusted-users = root <your account>
make sure that you have restarted nix-daemon service after you have changed /etc/nix/nix.conf
- Install socat and config ssh (for clone by ssh protocol)
nix profile add nixpkgs#socat
.ssh/config
Host gitea.shenrs.eu
HostName gitea.shenrs.eu
IdentityFile ~/.ssh/id_ed25519
ProxyCommand socat - openssl-connect:gitea.shenrs.eu:2022,snihost=gitea.shenrs.eu,verify=0
3.2 checkout source code
3.3 build (for package and release)
cd xce/src
# for build debug version
nix build --option sandbox false .#xcecore_debug
# for normal build
nix build --option sandbox false .#xcecore
You can find the generated binaries at =result= directory
3.4 build (for daily develop)
cd xce/src
nix develop
# using meson to generated build configuration (debug and address sanitize)
meson setup build --buildtype=debug -Db_sanitize=address
# run meson to build
meson compile -C build
# The generated files will be in build/
3.5 build AppImage package
cd xce/src
nix bundle --bundler github:ralismark/nix-appimage --option sandbox false .#xce
This will create all in one AppImage file which contains everything for package delivery.
4. misc
4.1. Windows remap ctrl and alt key
create a reg file, e.g. remapkey.reg
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Keyboard Layout]
"Scancode Map"=hex:00,00,00,00,00,00,00,00,05,00,00,00,38,00,1d,00,1d,00,38,00,38,e0,1d,e0,1d,e0,38,e0,00,00,00,00
then double click remapkey.reg to import it. Restart OS.