mirror of
https://github.com/getpaseo/paseo.git
synced 2026-10-25 10:42:45 +00:00
A supervisor killed between creating paseo.pid and writing its contents leaves an empty file. Every later start, status, and stop then failed with "Cannot read daemon state", so the daemon stayed down until someone deleted the file by hand. An empty lock names no owner, so after the existing read retries it now reads as no lock, and acquiring the lock removes it before creating a new one. A lock with unparseable contents still refuses, since it may belong to a supervisor this version cannot read. Co-authored-by: paseo-bot[bot] <266920839+paseo-bot[bot]@users.noreply.github.com>