Repository navigation
SuperLocalMemory v4.2.33
·
11 commits
to main
since this release
Immutable
release. Only release title and notes can be modified.
Nothing changes in the store, and there is nothing to run. This release fixes the four known issues listed for 4.2.32.
Fixed
- Deleting a memory that a backup already holds now succeeds. Before, the delete removed the memory and recorded it outside the backups, then answered "busy, retry" for as long as the backup existed, so a client that followed the retry advice never saw success. The answer now names the backups that still hold the memory (
backup_obligations_pending); restoring one of them removes the memory again. A delete whose record could not be written still asks for a retry, because a restore would then bring the memory back (#342). - Auto-start no longer reloads the service while
slm serve uninstallis removing it. Auto-start now takes the same lock asslm serve installanduninstall, and never waits for it: while an installer holds it, the daemon starts directly with the service's settings (#337). - When one data folder has services installed for two ports, the hand-over and
slm doctornow count both. Before, a daemon run by the other port's service looked unowned and was asked to stop, and the two services could keep taking the folder from each other (#338). - On Fedora, RHEL, AlmaLinux and other distributions that ship a user-wide systemd drop-in, the service
slm serve installwrites is recognised again byslm serve status,slm doctor, auto-start and uninstall. A drop-in that only sets timeouts is accepted. One that changes the command, the settings, the user or the files the daemon can reach, or that sits in the unit's own folder, still is not (#339).
Changed
- Tests no longer inherit a logger level that an earlier test set, and the dashboard load test holds each request to its own idle time on the same machine, so two tests that failed at random on slow CI runners are steady (#343).