myxce/.wolf/hooks
lei.chen 5b47ee603f fix(apiserver): carry exec_user on job submit so jobs don't run as nobody (bug-1500)
modelJobToSubmit built the C job_startinfo_t without setting execuser, so the
controller forwarded a NULL execuser in the startjob request and the worker
ran every job as "nobody". Now the submit carries the resolved exec user: an
explicit exec_user wins, otherwise the job runs as the submitting user.

- add resolveExecUser() (plain-Go, unit-testable) + TestResolveExecUser
- set si.execuser in modelJobToSubmit, free it in freeJobSubmit

Note: deploying this exposed an ASAN heap-use-after-free in the apiserver's
submit/notification path (strncpy reading freed memory); the fix is committed
but needs the memory-lifecycle investigation before it can ship safely.

Co-Authored-By: Claude <noreply@anthropic.com>
2026-08-04 07:38:43 +00:00
..
_session.json fix(apiserver): carry exec_user on job submit so jobs don't run as nobody (bug-1500) 2026-08-04 07:38:43 +00:00
package.json chore: checkpoint all prior work for clean state 2026-06-04 13:04:16 +00:00
post-read.js chore: checkpoint all prior work for clean state 2026-06-04 13:04:16 +00:00
post-write.js chore: checkpoint all prior work for clean state 2026-06-04 13:04:16 +00:00
pre-read.js chore: checkpoint all prior work for clean state 2026-06-04 13:04:16 +00:00
pre-write.js chore: checkpoint all prior work for clean state 2026-06-04 13:04:16 +00:00
session-start.js chore: checkpoint all prior work for clean state 2026-06-04 13:04:16 +00:00
shared.js chore: checkpoint all prior work for clean state 2026-06-04 13:04:16 +00:00
stop.js chore: checkpoint all prior work for clean state 2026-06-04 13:04:16 +00:00