LibretroAdmin 267d4453b5 cloud sync: back up by copying when a rename cannot reach the backup ...

Backups go under the assets directory, wherever saves live. A rename
fails when those are on different volumes, or on Android when saves are
in a SAF folder, and the file then was not backed up: non-destructive
mode gave up on replacing it.

Fall back to copying the file and removing the original. If it cannot
be removed, drop the copy and report the failure, as the caller relies
on the local file being gone. cloudsync_commit_test covers both a
replaced and a removed file with such a rename refused.

2026-11-09 03:43:06 +01:00

..

cloudsync_async_test.c

cloud_sync: hand calls and results to the worker without a lock

2026-10-29 22:31:19 +01:00

cloudsync_commit_test.c

cloud sync: back up by copying when a rename cannot reach the backup

2026-11-09 03:43:06 +01:00

cloudsync_manifest_adds_test.c

cloudsync: a blocking driver's calls read settings copied as the sync is pushed

2026-10-05 12:51:48 +02:00

cloudsync_pacing_test.c

task_cloudsync: Sync Now and Resolve during a sync run after it

2026-11-02 16:22:17 +01:00

cloudsync_path_safety_test.c

security: validate replay, UPnP and cloud sync input (#19628)

2026-09-26 17:22:37 +02:00

cloudsync_savefile_owner_test.c

cloud sync: a directory that cannot be listed stops the sync

2026-09-14 13:56:31 +02:00

Makefile

cloud_sync: hand calls and results to the worker without a lock

2026-10-29 22:31:19 +01:00