Repository navigation
·
287 commits
to main
since this release
Immutable
release. Only release title and notes can be modified.
Features
- Add opt-in strict shell and task-prolog status for user job wrappers while retaining the default decision failure policy.
- Accept four-digit ASCII year frontends alongside validated versioned module names during a restore.
- A static Zig build of the guard,
zig build -Drelease=true, runs the same decision as the Python script and passes the same test suite (TOOL_BIN=zig-out/bin/eessi-arch-guard python -m unittest discover -s tests). It is not yet the default prolog; it replaces the Python guard only after the release gate in the port plan (shadow comparison, real Lmod, a second review of the validators).
Bugfixes
- The decision cache is kept per output mode. A batch script that runs
--shellafter the task prolog no longer gets the prolog's cached result, such as a failure for a value with a newline that--shellcan carry, and a prolog no longer reuses a--shellresult. - The cache and its lock are trusted only when the open file is a regular file owned by the caller, with one link and no group or other bits. A file planted at the cache name in a shared
/tmp, such as a FIFO or another user's file, no longer feeds the decision or blocks the prolog, and a cached entry that changesLD_*,SLURM_*,BASH_FUNC_*or another denylisted name is ignored. - Honor existing private job workspaces for restore temporaries and provide a strict-mode state-directory fallback without creating or widening configured bases.
- The Zig build exits 0 with the one skip line on every failure path it can reach: out of memory, a cache lock error other than would-block (reported instead of waited out), and a crash, whose handlers now run on an alternate stack; an emergency stops the chained prolog's child first. It builds on zig-common 0.8.1 and targets the baseline CPU by default.
Docs
- This release ships the Zig build without the shadow comparison beside the Python guard that the port plan's release gate names; the maintainer waived it on 2026-11-14. The Python guard stays the default prolog, and a site switching to the binary should run the comparison itself first (
RELEASING.md, item 5).