* Show effective isolation level on workers page, not configured The workers page displayed the configured isolation level (nsjail/unshare) even when the binary wasn't actually available, which was misleading. Now shows "none (nsjail unavailable)" or "none (unshare unavailable)" when the setting is enabled but the binary failed its startup test, so admins can immediately see the mismatch from the UI. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * Simplify: use standard 'none' value when isolation binary unavailable Keep the string as one of the 3 known values (nsjail/unshare/none) since the frontend checks === 'none' for the warning badge. Now if nsjail/unshare is configured but the binary is unavailable, it correctly reports 'none' so the warning badge shows up. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Windmill Worker
The worker. Used to process and execute flows & jobs.
This crate exposes both a library as well as a binary target.