aawsome

Thanks @LadyMikea for your question / request to change the include/exclude settings. About the reason: The current reason is that rustic uses the `ignore` crate for getting file lists and...

But actually I have to add an restriction: rustic does not have the goal to be or stay CLI-compatible with restic. Its goal is to stay repository-compatible - and of...

Thanks a lot for reporting! The error seems to come from parallel access to files-to-restore. There are two possible reasons: a) You did access the file parallel to the restore...

@ducalex Thanks for your reply and suggestions! I wasn't aware of the Rust internals but good to know that in principal it should work. Actually I think we should do...

If this is because a parallel running job (e.g. Windows Defender) accessing the file, note that the rustic restore is "resumable" in the sense that it detects already restored contents...

Thanks for opening this issue @nickchomey I thought a bit about it. Actually I find the points given in the restic discussion why it might be a bad idea to...

Thanks a lot for this issue! Seems we need to improve this.

Any updates on this? Actually, it prevents me from releasing my project to crates.io, so I would appreciate to have a solution in near future...

Unfortunately, I can't use the fork as dependency as crates.io recommends that all dependencies are also published on crates.io. But I made a PR to integrate (parts of) your code...

> Is there any way I can find out what aspect of the directory is being identified as "changed" from the command-line? You can run `restic diff --metadata`