Repository navigation
Make the local-encryption daemon inactivity timeout configurable #1272
ivan-kleshnin
started this conversation in
New Features
Replies: 1 comment 1 reply
|
thanks for this - im in the middle of a larger overhaul of how the local encryption stuff works and am removing that 30 min timeout already. But in the short term I can just remove it or maybe bump up to 24hr. |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
The encryption daemon exits after 30 minutes of inactivity:
SessionManager.daemonInactivityTimeout = 1800DAEMON_INACTIVITY_TIMEOUT = 30 * 60So the value is already not a constant. For long-lived workflows (dev servers, agent sessions) the 30-minute exit only produces avoidable cold starts on the next decrypt.
Proposal: let users override it, e.g.
_VARLOCK_DAEMON_IDLE_TIMEOUT(TTL format:30m,8h,forever) or adaemonInactivityTimeoutkey in~/.config/varlock/config.json, applied in both daemons, default unchanged.I'm using locally-enciphered secrets and it gets old pretty quickly to reload the daemon. I mean, it's reloaded automatically with many CLI commands BUT coding agents repeatedly report that "Your daemon is down" and stuck, waiting for my reaction.
The only workaround a.t.m. seems to be a manual heartbeat process – pinging the daemon socket from a cron/launchd job, which relies on an internal protocol, so brittle. A supported knob would remove the need for that, make it more reliable, and would potentially clarify behavior for the developers.
All reactions