TW
stalebot is a rather annoying thing here. There is no reason for closing an issue just because no one cared for it.
It can also be found in `vorta.log`: ``` 2023-11-30 17:53:38,412 - root - CRITICAL - Uncaught exception, file a report at https://github.com/borgbase/vorta/issues/new/choose Traceback (most recent call last): File "views/exclude_dialog.py", line...
@rai-ankur Assigned - thanks for helping!
@rai-ankur You don't work on this any more, right?
@AdwaitSalankar Personally, I would rather have copy&paste than "send this report directly to Github" (and any complexity relating to the latter).
I think the link should go to `.../issues` and it should also tell "Please only open new issues after checking if this issue was not already reported."
Can be fixed manually by adding `--exclude-if-present .nobackup` in `Schedule -> Shell commands -> Extra arguments for borg create`.
@diivi is this related to / caused by your exclude gui changes?
@goebbe borg emits these hints at `borg init` time (on stderr or stdout), but maybe vorta does not show them on the GUI (or they disappear too quickly?).
The step to create a key backup is the same no matter whether keyfile or repokey is used and the backup should be made in both cases.