Kopia restore keeps running even when everything has been restored

[Tedpac]

When restoring a backup (which has 50 directories and 379 files), Kopia keeps running even when 100% of the directories and files have been restored. The repository of this backup is hosted on OneDrive through Rclone.

Every time I have tried to restore the backup through KopiaUI the same thing has happened:

Additionally, I tried to restore the backup using the following procedures and the same problem occurs in both:

1. $ kopia restore <snapshot> <some_path>

...
Processed 412 (35.4 GB) of 428 (35.4 GB) 15.5 MB/s (100.0%) remaining 0s.
Processed 413 (35.4 GB) of 428 (35.4 GB) 15.5 MB/s (100.0%) remaining 0s.
Processed 418 (35.4 GB) of 428 (35.4 GB) 15.5 MB/s (100.0%) remaining 0s.
Processed 421 (35.4 GB) of 428 (35.4 GB) 15.4 MB/s (100.0%) remaining 0s.
Processed 429 (35.4 GB) of 428 (35.4 GB) 15.4 MB/s (100.0%) remaining 0s.
Processed 429 (35.4 GB) of 428 (35.4 GB) 15.4 MB/s (100.0%) remaining 0s.
Processed 429 (35.4 GB) of 428 (35.4 GB) 15.4 MB/s (100.0%) remaining 0s.
Processed 429 (35.4 GB) of 428 (35.4 GB) 15.4 MB/s (100.0%) remaining 0s.
Processed 429 (35.4 GB) of 428 (35.4 GB) 15.4 MB/s (100.0%) remaining 0s.
Processed 429 (35.4 GB) of 428 (35.4 GB) 15.3 MB/s (100.0%) remaining 0s.
Processed 429 (35.4 GB) of 428 (35.4 GB) 15.3 MB/s (100.0%) remaining 0s.
Processed 429 (35.4 GB) of 428 (35.4 GB) 15.3 MB/s (100.0%) remaining 0s.
Processed 429 (35.4 GB) of 428 (35.4 GB) 15.2 MB/s (100.0%) remaining 0s.
Processed 429 (35.4 GB) of 428 (35.4 GB) 10.7 MB/s (100.0%) remaining 0s.
Processed 429 (35.4 GB) of 428 (35.4 GB) 5.4 MB/s (100.0%) remaining 0s.
...

2. I ran the following commands in different terminals:

• $ rclone mount --vfs-cache-mode full <repository_remote_path> <mount_path>
• $ kopia repo connect filesystem --path <mount_path>
• $ kopia restore <snapshot> <some_path>

And the result is the same:

...
Processed 419 (35.3 GB) of 428 (35.4 GB) 15.5 MB/s (99.5%) remaining 10s.
Processed 420 (35.3 GB) of 428 (35.4 GB) 15.5 MB/s (99.5%) remaining 9s.
Processed 423 (35.3 GB) of 428 (35.4 GB) 15.5 MB/s (99.5%) remaining 10s.
Processed 424 (35.3 GB) of 428 (35.4 GB) 15.3 MB/s (99.7%) remaining 6s.
Processed 425 (35.3 GB) of 428 (35.4 GB) 15.3 MB/s (99.7%) remaining 6s.
Processed 426 (35.3 GB) of 428 (35.4 GB) 15.3 MB/s (99.7%) remaining 5s.
Processed 427 (35.4 GB) of 428 (35.4 GB) 15.2 MB/s (99.8%) remaining 4s.
Processed 428 (35.4 GB) of 428 (35.4 GB) 15.1 MB/s (99.9%) remaining 2s.
Processed 429 (35.4 GB) of 428 (35.4 GB) 15 MB/s (100.0%) remaining 0s.
Processed 429 (35.4 GB) of 428 (35.4 GB) 9.6 MB/s (100.0%) remaining 0s.
Processed 429 (35.4 GB) of 428 (35.4 GB) 9.4 MB/s (100.0%) remaining 0s.
Processed 429 (35.4 GB) of 428 (35.4 GB) 9.3 MB/s (100.0%) remaining 0s.
Processed 429 (35.4 GB) of 428 (35.4 GB) 8.7 MB/s (100.0%) remaining 0s.
Processed 429 (35.4 GB) of 428 (35.4 GB) 8.2 MB/s (100.0%) remaining 0s.
Processed 429 (35.4 GB) of 428 (35.4 GB) 7.9 MB/s (100.0%) remaining 0s.
...

---

Notes:

1. Fortunately today I waited long enough and the restore done through KopiaUI managed to finish without any problems (but it took a very long time).
2. The above note leads me to the conclusion that this is a UX problem, because if Kopia is doing some post-processing having restored 100% of the directories and files, this should be recorded in the logs so that the user can find out.
3. "Processed 429 (35.4 GB) of 428..."? It seems to me that the last counter is incorrect.

Kopia version: 0.17.0 (the latest at the moment).