Browse Source
- Run profile inactivity timeout propagation on the single-threaded scheduled executor instead of the notifications consumer thread, so it stays off the consumer thread and serializes with the periodic state checker; a supersede guard drops stale tasks - Reject device profile inactivity timeout values that are not a whole number of seconds - Remove @Lazy on the device profile cache field - Set inactivityTimeoutMs directly in the device profile form instead of behind a redundant profileData guardpull/15527/head
5 changed files with 41 additions and 16 deletions
Loading…
Reference in new issue