Michael Eischer

I don't get how your PR is supposed to solve the problem described here. Please add proper steps on how to reproduce the problem, before providing some solution. Without those,...

Closing as there's not enough information to reproduce and the associated PR is a hacky workaround.

The idea in #2128 was to eventually remove the hostname and username from the key metadata. That would make this impossible to implement once the metadata was removed.

Please follow the issue template and not just post whatever structure was generated by some AI. It took me a while to even notice that this isn't just random AI...

Restic never seems to get a reply to the request for `/data/b34d5ce8f035033aab0cc2aedb0ef38a91d71150be757aa5c71e5a23a36771d4 `. Does `rclone copy hetzner:/data/b3/b34d5ce8f035033aab0cc2aedb0ef38a91d71150be757aa5c71e5a23a36771d4 ./local-path` work? > I tried to restore on another Debian machine and restic...

The longer I look at that issue the weirder it gets. Apparently restic was trying to backup a file called `C:\Users\"Issac Kelly"\ --iexclude-file="C:\Users\Issac`. At the start of the backup, restic...

@brandtb Thanks for the clean reproduction steps. https://github.com/restic/restic/pull/5421 should fix the crash, although the overall error handling might be less than optimal still.

I just gave the current master branch a test run and the crash is fixed. Better handling the invalid filename is better suited for https://github.com/restic/restic/issues/2745 .

> I wanted to bench this, but: I'm pretty sure the code is AI generated to a larger extend and apparently not well tested. And based on a quick glance...

I don't appreciate talking to an AI agent. If I wanted to do that, I could just use one myself. So, I'll just close this before I get too snarky.