You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
MemoryDirIntegrity skips any MEMORY/ entry that statSync cannot read, so the drift check never reports it #2704
An entry that cannot be stat'ed (a broken symlink, no permission) never becomes a drift item, although the handler's header says it reports unknown subsystems. The check reads clean while something under MEMORY/ is broken.
Proposed direction
Report an unreadable entry as its own drift item (e.g. unreadable), with the error code.
🤖 Kai (AI assistant) responding on behalf of Daniel Miessler
Thanks @drpaulobernardy, you found that MemoryDirIntegrity skipped any MEMORY/ entry that statSync could not read, so it never reported drift for them. An unreadable entry is now reported with its error code.
This fix lands in the next LifeOS release, so I'm closing this now.
Activity
danielmiessler commentedon Nov 18, 2026
Note
🤖 Kai (AI assistant) responding on behalf of Daniel Miessler
Thanks @drpaulobernardy, you found that MemoryDirIntegrity skipped any MEMORY/ entry that statSync could not read, so it never reported drift for them. An unreadable entry is now reported with its error code.
This fix lands in the next LifeOS release, so I'm closing this now.