Please describe what you are doing to trigger the bug:
Accidentally removed a filter file referenced by “@”.
Please describe what you expect to happen (but doesn’t):
Expect CLI (version 3.2.3) to fail with error.
Please describe what actually happens (the wrong behaviour):
CLI continues, backing up files that should have been ignored:
Running backup command from /share/CACHEDEV1_DATA/.qpkg/Duplicacy/.duplicacy-web/repositories/localhost/4 to back up /share/homes/Greg
Options: [-log -comment ‘healthchecks=https://hc-ping.com/5f8d6138-0a58-453d-af7c-f543549bad92’ backup -storage NAS0 -stats]
2024-02-27 01:18:54.372 INFO REPOSITORY_SET Repository set to /share/homes/Greg
2024-02-27 01:18:54.374 INFO STORAGE_SET Storage set to /share/TR-004/Duplicacy/storage
2024-02-27 01:18:55.971 INFO BACKUP_START Last backup at revision 1231 found
2024-02-27 01:18:56.410 INFO BACKUP_INDEXING Indexing /share/homes/Greg
2024-02-27 01:18:56.410 INFO SNAPSHOT_FILTER Parsing filter file /share/CACHEDEV1_DATA/.qpkg/Duplicacy/.duplicacy-web/repositories/localhost/4/.duplicacy/filters
2024-02-27 01:18:56.410 INFO SNAPSHOT_FILTER Parsing filter file /share/Household/duplicacy/filters-global.txt
2024-02-27 01:18:56.410 INFO SNAPSHOT_FILTER Loaded 0 include/exclude pattern(s)
…