From ab220b89afcfda848cf84c18cc135a2e5c392b79 Mon Sep 17 00:00:00 2001 From: Gabriel Schneider Date: Tue, 29 Sep 2026 12:14:13 -0300 Subject: Recent goes on across a Restore, and is kept after it A Restore makes a new session, which never loaded the kept list, and saveRecent gives up until it has: Recent was empty after a Restore and nothing opened afterwards was kept. The new session now takes the old one's list (a boot from a dump reads the kept file). Co-Authored-By: Claude Opus 5.5 --- test/fs.py | 7 +++++++ 1 file changed, 7 insertions(+) (limited to 'test/fs.py') diff --git a/test/fs.py b/test/fs.py index 6edfeb0f..75d03d40 100644 --- a/test/fs.py +++ b/test/fs.py @@ -723,6 +723,13 @@ def workflow_canary(binary): wait(lambda: f'restore {saved}' in restored.read('/log').decode(), 'Restore not logged') names = restored.read('/index').decode() assert f'{root}/a.txt' in names and f'{root}/b.txt' in names, names + # Recent goes on across the Restore, and is kept after it. + assert f'{root}/a.txt\n' in restored.read('/recent').decode(), restored.read('/recent') + (root / 'after.txt').write_bytes(b'after\n') + look(restored, str(root / 'after.txt')) + assert f'open {root}/after.txt\n' in restored.read('/recent').decode() + state = root / '.local' / 'state' / 'pardes' / 'recent' + wait(lambda: f'{root}/after.txt'.encode() in state.read_bytes(), 'Recent not kept after Restore') assert time.monotonic() - started < 30, 'the canary took too long' -- cgit v1.3